Help us improve
Share bugs, ideas, or general feedback.
From shuriken
Use when a user wants to integrate with or develop against the Shuriken API or SDK — covers proficiency assessment, path routing (quickstart / raw API / SDK), and tells you which deepening reference tool to reach for (OpenAPI for HTTP endpoints, the stream catalog for WebSockets, platform docs as fallback).
npx claudepluginhub shurikentrade/shuriken-skills --plugin shurikenHow this skill is triggered — by the user, by Claude, or both
Slash command
/shuriken:api-integrationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill covers the full "I want to call Shuriken programmatically" surface. It is intentionally thin up front — use the deepening tools below rather than pasting long code into the session.
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`).
Scaffolds third-party service integrations: detects project language (TypeScript/Python/Go/Rust/Ruby), pulls SDK docs via Context7, chooses tier, generates client/auth/webhooks with error handling/tests.
Share bugs, ideas, or general feedback.
This skill covers the full "I want to call Shuriken programmatically" surface. It is intentionally thin up front — use the deepening tools below rather than pasting long code into the session.
Before pointing the user at code, establish two things:
Calibrate vocabulary and level of detail to this. If ambiguous, ask one clarifying question before firing off a long answer.
Three ways to call Shuriken. Help the user pick.
Rough default: quickstart for beginners/intermediates, SDK for software engineers, raw HTTP only when they've said why.
Every integration needs an agent key. See shuriken:agent-keys for lifecycle and shuriken:scoping for least-privilege scope selection. Point the user at app.shuriken.trade/agents to create one.
Do not preload the entire API reference into the conversation. Pull deeper references only when the user's next question needs them:
fetch_shuriken_openapi. This returns the live OpenAPI spec — the source of truth for HTTP endpoints.fetch_shuriken_streams. This returns the live v1 stream catalog with channel names, required filters, and payload formats.fetch_shuriken_docs and read the relevant page under llms.txt.Never guess an endpoint or stream name from memory — the API evolves.
shuriken:agent-keys.shuriken:scoping.Before writing code, confirm:
shuriken:agent-keys, shuriken:scoping, shuriken:learn-about-shuriken