external-resource-context
Captures and persists access methods for resources outside the repository (design source, design system, API schema, IaC source, secret store) so downstream work can reach them deterministically. Use when work depends on external resources, or when the user mentions design source, design system, API schema, IaC source, secret store, or canonical source.
npx skills add shinpr/claude-code-workflows --skill external-resource-context --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# External Resource Context ## Purpose AI agents understand the codebase but not the external resources surrounding it. This skill captures, in a deterministic location, the **access methods** to resources outside the repository so downstream work (design, planning, implementation, review) can reach them without re-asking the user. Resources covered: design origin (where the canonical visual specification lives), design system (component library and tokens), guidelines (usage docs, accessibility rules), visual verification environment (how to confirm rendering), database schema source, migration history, secret store location, API schema source (OpenAPI / proto / GraphQL SDL), mock environment, IaC source, environment configuration. ## Scope Boundaries **In scope**: hearing protocol, storage location, single-source-of-truth ownership rule, reference protocol for downstream consumers. **Out of scope**: enforcing that captured resources are correct or current — verification belongs to the agent that consumes the resource. Generating the resources themselves (e.g., creating a DESIGN.md from scratch). ## Storage Locations (Two-Tier) | Tier | Location | Holds | Update Frequency | |-----
- Purpose
- Scope Boundaries
- Storage Locations (Two-Tier)
- Single Source of Truth Rule
- Hearing Protocol
- When to Hear
- Domain Routing
- Two-Phase Hearing
- Storage Protocol
- Reference Protocol (For Downstream Consumers)
- Output Format
- Quality Checklist
- References
What does the external-resource-context skill do?
Captures and persists access methods for resources outside the repository (design source, design system, API schema, IaC source, secret store) so downstream work can reach them deterministically. Use when work depends on external resources, or when the user mentions design source, design system, API schema, IaC source, secret store, or canonical source.
How do I install it?
Run `npx skills add shinpr/claude-code-workflows --skill external-resource-context --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From shinpr/claude-code-workflows, a repository with 664 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.