From Directives Toolkit
Use BEFORE discussing, offering, or promising work on any repository other than the one this session is scoped to. Verifies the session's TRUE repo scope (GitHub MCP scope, add_repo/list_repos availability) so cross-repo access is never overclaimed.
How this skill is triggered — by the user, by Claude, or both
Slash command
/directives-toolkit:scope-chkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Establish and report the **real** repository scope of this session, so you never
Establish and report the real repository scope of this session, so you never
offer cross-repo capability you can't deliver (the Repository Scope rule in
global.md). Quick, read-only. Run it, then report — do not guess.
Execute in order:
In-scope repo(s). Identify the repo(s) this session can actually act on:
git remote -v — the cloned repo this session is working in.Can other repos be added? Check via ToolSearch whether the
add_repo / list_repos tools (claude-code-remote server) actually exist in
THIS session:
list_repos exists → run it and list the repos that add_repo could pull
in.Report a compact verdict:
<owner/repo …><addable repos> | NOT availableadd_repo was confirmed available.Use it at session start to set the boundary up front, and any time you — or the user — suspect drift toward promising cross-repo work. When in doubt about another repo, run this before saying anything about it.
npx claudepluginhub akyachtsman/claude.directives --plugin directives-toolkitProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Searches MemPalace before answering questions about past work, people, projects, or prior decisions. Returns verbatim stored content instead of guessing from model memory.