sakura-research

Verify external documentation, APIs, and standards for software decisions.

3|1|Updated Sep 9, 2026
One-click install
npx skills add https://github.com/v20227/using-sakura-dev --skill sakura-research-v20227
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sakura-research
Source: https://github.com/v20227/using-sakura-dev/tree/main/skills/sakura-research
Command: npx skills add https://github.com/v20227/using-sakura-dev --skill sakura-research-v20227

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Software decisions often depend on external facts like framework compatibility, API behavior, standards, and licensing, and guessing or relying on stale knowledge leads to broken implementations. This Skill verifies those facts against current first-party documentation and source code before they affect your plan or code. ## Core Features & Use Cases - Evidence-Based Verification: Searches, opens, and reads the actual documentation passage supporting a decision instead of trusting search snippets. - Source Prioritization: Prefers first-party platform, framework, and API documentation, with open-source repositories used for implementation patterns when official material is insufficient. - License Boundary Enforcement: Supports a no-inherited-license mode that blocks copying, porting, or adapting third-party code when the result must carry no external license obligations. - Use Case: Before integrating a new payment API, use this Skill to confirm the current endpoint behavior, authentication requirements, and version compatibility, then receive a decision-ready summary with source links. ## Quick Start Verify the current authentication requirements and version compatibility of the Stripe API before we implement the checkout flow.

Frequently Asked Questions about sakura-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify API documentation before implementing an integration?▼

Identify the specific decision the API fact affects, then search for and open the official first-party documentation page. Confirm the exact passage covering authentication, endpoints, and version behavior rather than relying on search result snippets.

What sources should I trust for framework compatibility questions?▼

Prefer current first-party documentation for platform, framework, API, and compatibility behavior. When official material does not cover implementation patterns, inspect relevant open-source repositories for tested approaches.

Can I copy code from open-source repositories into my project?▼

Only after checking the repository license. If your project must carry no inherited license or attribution obligations, do not copy, port, or adapt third-party source; instead write an independent implementation based only on observed behavior.

Why is a search result snippet not enough for a technical decision?▼

Snippets can be outdated, truncated, or taken out of context. Verification requires opening the source page and reading the passage that supports the decision, so the fact is confirmed against current documentation.

What happens when evidence for a technical question is unavailable?▼

The item is left explicitly unverified rather than filled with an invented conclusion. The unresolved blocker is stated precisely so the development decision can account for the remaining uncertainty.