external-resource-context — Claude Code skill
external-resource-context tracks access details for external API schemas, design files, IaC, and secret stores outside the repository. Prevents repeated discovery of environment assets.
MIT ★ 720 updated 2026-10-29
npx skills add shinpr/claude-code-workflows --skill external-resource-context -a claude-codeWhat external-resource-context does
The skill organizes external dependencies across two deterministic layers. At the project level, it maintains docs/project-context/external-resources.md with stable access methods like URLs, MCP server names, local file paths, and console commands. When environment locations change, updates happen only in this project file.
The feature tier sits inside individual UI Specs or Design Docs under the ## External Resources Used heading. It maps project entries to feature-specific identifiers, such as an endpoint path or a design node id. If an external system is unreachable, consumers proceed with repository evidence and record the gap in their output.
What it helps with
- record access routes for OpenAPI, Protobuf, and GraphQL schemas
- link design origins and token guidelines to feature specs
- document secret store locations and IaC sources in one place
- stop rediscovering external assets during implementation cycles
Example prompts for the agent
- Record the external API schema and mock environment for this project
- Add the design origin and node id to the feature context
- Check external resource context before drafting the implementation plan
How to install external-resource-context
1Skills CLI (Vercel)
npx skills add shinpr/claude-code-workflows --skill external-resource-context -a claude-code2Manually: put the files in place
~/.claude/skills/external-resource-context/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/external-resource-context/
1Skills CLI (Vercel)
npx skills add shinpr/claude-code-workflows --skill external-resource-context -a codex2Manually: put the files in place
.agents/skills/external-resource-context/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add shinpr/claude-code-workflows --skill external-resource-context -a cursor2Manually: put the files in place
.cursor/skills/external-resource-context/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install shinpr/claude-code-workflows dev-skills/skills/external-resource-context2Manually: put the files in place
.github/skills/external-resource-context/SKILL.md1Skills CLI (Vercel)
npx skills add shinpr/claude-code-workflows --skill external-resource-context -a gemini-cli2Platform CLI
gemini skills install https://github.com/shinpr/claude-code-workflows --path dev-skills/skills/external-resource-contextManually: put the files in place
.devin/skills/external-resource-context/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about external-resource-context
How to install external-resource-context in Claude Code?
Run npx skills add shinpr/claude-code-workflows --skill external-resource-context -a claude-code.
Where are external resources documented?
Project-wide facts are kept in docs/project-context/external-resources.md. Feature-specific identifiers belong under ## External Resources Used within the respective design doc or UI spec.
What happens if an external endpoint cannot be reached?
The agent proceeds using available repository evidence and logs the unreachable asset as a limitation in its output.
Source text
SKILL.md · MIT
--- name: external-resource-context description: Records where resources outside the repository live (design source, design system, API schema, IaC source, secret store) and how design, implementation, and verification reach them. Use when work depends on an external resource, or when the user mentions design source, design system, API schema, IaC source, secret store, or canonical source. --- # External Resource Context ## Purpose Repository evidence does not contain every external resource surrounding a system. 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 repeatedly rediscovering access details. 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. ## Storage Locations (Two-Tier) | Tier | Location | Holds | Update Frequency | |------|----------|-------|------------------| | Project | `docs/project-context/external-resources.md` | Environment-stable facts: which resources exist for this project and how to access them (URL, MCP name, file path, command) | Rare — only when the project's environment changes | | Feature | `## External Resources Used` section inside the relevant UI Spec or Design Doc | The subset of project-tier resources actually used by this feature, plus feature-specific identifiers (e.g., a specific node id within the design tool, a specific endpoint path) | Per feature | ### Single Source of Truth Rule The project tier owns environment facts. Feature-tier sections list only feature-specific identifiers (node id within the design source, specific endpoint path within the API, specific IaC module name) and reference project-tier entries by label; URLs, MCP names, and access commands remain in the project-tier file. When the environment changes, only the project-tier file is updated. Example feature-tier entry uses the table format defined in `references/template.md`: a row with the project-tier label in the first column and the feature-specific identifier in the second column. ## Reference Protocol (For Downstream Consumers) Before investigating the repository for an external fact, check whether it is already recorded: 1. Read `docs/project-context/external-resources.md` (if present) to learn what is available and how to access it. 2. Read the target UI Spec or Design Doc's `## External Resources Used` section for feature-specific identifiers. 3. Use the access method declared in the project tier (e.g., the named MCP, the URL, the file path) to fetch the actual resource content. When the file is absent or the resource is unreachable, continue from governing and repository evidence. Each consumer records the limitation in its applicable output. ## Capturing and Updating Records Capture only resources needed by the current decision. Reuse supplied access details and repository records, verify them within current authority, and ask only for missing information that prevents that decision. Follow [references/hearing.md](references/hearing.md) for evidence, questions and storage. ## Output Format Use [references/template.md](references/template.md) for a compact project record. Preserve existing labels referenced by consumers; include only relevant entries with their access details and source evidence. For feature-tier sections inside UI Spec or Design Doc, the heading text "External Resources Used" is fixed; the heading level matches the parent document's natural structure (h2 in UI Spec where it is a sibling of other top-level sections, h3 in Design Doc where it sits under Background and Context). ## References - [references/hearing.md](references/hearing.md) — Decision-specific capture and storage - [references/frontend.md](references/frontend.md) — Frontend domain axes - [references/backend.md](references/backend.md) — Backend domain axes - [references/api.md](references/api.md) — API contract domain axes - [references/infra.md](references/infra.md) — Infrastructure domain axes - [references/template.md](references/template.md) — Project-tier and feature-tier structure templates
© shinpr · MIT · shinpr/claude-code-workflows