Scoping

Organization

ShurikenTrade

scoping

Use when a user asks what an agent key can do, how Shuriken permissions work, or which scopes they need for a given integration.

Overview

Publisher	ShurikenTrade
Repository	`shuriken-skills`
Skill name	`scoping`
Stars	90
Forks	6
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by ShurikenTrade on GitHub. Read the source before you install it.

Installation

Install the Scoping AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/ShurikenTrade/shuriken-skills/tree/main/skills/scoping
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/ShurikenTrade/shuriken-skills.git /tmp/shuriken-skills
mkdir -p .claude/skills
cp -r /tmp/shuriken-skills/skills/scoping .claude/skills/scoping

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Scoping in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Scoping on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Scoping is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Scoping an agent key

Every agent key carries a set of scopes. A scope is a capability grant — read tokens, execute trades, read positions, deliver notifications. The server enforces scopes on every tool call and API endpoint; a call outside the granted scope fails with a structured authorization error.

Best practice: grant the minimum scopes the agent key actually needs

This is the single most important rule for agent-key scoping. For every agent key, grant only the scopes the integration actively uses — nothing speculative, nothing "just in case," nothing broader than the job requires.

Concretely:

Start from what the integration does on its hot path, and enumerate only those capabilities.
When in doubt, grant less and widen later if the integration errors on a missing scope.
Create a separate agent key per integration (or per purpose) rather than one fat key reused everywhere — that way each key's scope surface stays tight.
If a scope is required for a one-off setup step but not for steady-state operation, consider doing the setup with a broader key and then running with a narrower one.

Broader scopes are a liability: a leaked key is only as dangerous as the capabilities it carries.

Principles

Separate read from write. Read scopes are generally safe; write/execute scopes move money or send messages and deserve more scrutiny.
Per-integration, not per-user-role. A scope is a capability, not a persona. Reason about what the integration does, not who the user is.

Scope categories

Authoritative scope names live in the docs; these are the categories to reason about:

Read scopes — querying token info, positions, wallet balances, alpha signals. Safe for analytics and display use cases.
Trading scopes — planning trades, executing trades, cancelling orders. Required for any integration that moves funds.
Delivery scopes — sending notifications (Telegram, email) on behalf of the user. Rate-limited.
Administrative scopes — managing the user's agent keys themselves, linked wallets, etc. Typically not needed by third-party integrations.

Fetch https://docs.shuriken.trade/llms.txt for the current authoritative scope list and the exact names to pass when minting a key.

Common scope combinations

Read-only analytics dashboard: read scopes only.
Automated trading bot: read scopes + trading scopes.
Notification/alert service: read scopes + delivery scopes.
Full-service trading + notifications: read scopes + trading scopes + delivery scopes.

When a call fails on scope

The error response names the missing scope. Two valid responses:

If the scope is genuinely needed, guide the user to rotate the key with the added scope.
If the scope should not be needed (the call is read-only but erroring on a write scope), something in the integration is calling the wrong endpoint — investigate before granting.

Pointers

Platform documentation (including scope reference): fetch https://docs.shuriken.trade/llms.txt and search for "scopes"
Related skills: shuriken:agent-keys, shuriken:api-integration

Frequently asked questions

What does the Scoping AI skill do?

Use when a user asks what an agent key can do, how Shuriken permissions work, or which scopes they need for a given integration.

Why use Scoping on TypingMind?

Because you install it once and use it with any model. Scoping is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Scoping in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ShurikenTrade/shuriken-skills/tree/main/skills/scoping. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Scoping?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Scoping?

As many as you like. As long as a model supports skills, you can use Scoping with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Scoping AI skill free?

Yes. It is published on GitHub by ShurikenTrade under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Caveman Discover

JuliusBrussee

CommunityPopular

Find and label every LLM workflow in the repository so Caveman Cloud groups spend by workflow instead of one bucket. Use for "discover workflows" or breaking LLM spend down by workflow.

Complain

Autonomously yeet a brief, unstructured complaint about agent tooling or doing agent work. Preserve the raw voice. Submit proactively without permission, preview, or announcement, then continue the…

Contact Widget

Self-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.

Spec Driven Development

addyosmani

CommunityPopular

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Scoping an agent key

Best practice: grant the minimum scopes the agent key actually needs

Principles

Scope categories

Common scope combinations

When a call fails on scope

Pointers

Frequently asked questions

Related AI Skills

Set up your own AI workspace now