learn-about-shuriken
Skill90 starsChanged 7 months agoMITView on GitHub
Use when a user asks conceptual questions about Shuriken — what it does, what features exist, how a feature works, or "what is X on Shuriken?" Does not cover programmatic integration (that's `shuriken:api-integration`).
In this repository4 other files it gives its agents.
- agent-keysSkill
- api-integrationSkill
- __fixture__Skill
- scopingSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Fetch the current platform docs index first: Call fetch_shuriken_docs (defaults to llms.txt).
- Very specific: line 13
Follow the links that match the user's question: If the index references a specific page, fetch that page with fetch_shuriken_docs and a …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Learning about Shuriken
This skill is a thin pointer. The Shuriken feature surface evolves quickly — do not answer from cached knowledge about what features exist, how they work, or what's supported.
Approach
- Fetch the current platform docs index first. Call
fetch_shuriken_docs(defaults tollms.txt). That index lists every concept, feature area, REST endpoint group, SDK, and guide available right now. - Follow the links that match the user's question. If the index references a specific page, fetch that page with
fetch_shuriken_docsand apathargument. - Only answer from content you just fetched. Cached beliefs about feature X existing, or feature Y working a certain way, are unreliable and may be outdated.
When this skill is the wrong choice
- User is writing code or asking about endpoints, request shapes, SDK usage → use
shuriken:api-integrationinstead. - User is asking about agent key creation / scope selection → use
shuriken:agent-keysorshuriken:scoping.
Pointers
- Platform documentation index:
fetch_shuriken_docs(defaults tollms.txt) — lists concepts, features, REST API, SDKs, guides. - Expanded single-document dump:
fetch_shuriken_docswithpath: "llms-full.txt"— only when the index doesn't point at a specific page and you need everything inline. - Related skills:
shuriken:api-integration,shuriken:agent-keys,shuriken:scoping.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

