External Resource Context

Community

shinpr

external-resource-context

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.

Overview

Publisher	shinpr
Repository	`claude-code-workflows`
Skill name	`external-resource-context`
Stars	682
Forks	103
Bundled files	6
License	MIT
Links	Skill source Repository

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.
6 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by shinpr on GitHub. Read the source before you install it.

Installation

Install the External Resource Context 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.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/shinpr/claude-code-workflows/tree/main/dev-skills/skills/external-resource-context

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

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/shinpr/claude-code-workflows.git /tmp/claude-code-workflows
mkdir -p .claude/skills
cp -r /tmp/claude-code-workflows/dev-skills/skills/external-resource-context .claude/skills/external-resource-context

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

Use it in TypingMind

Enable External Resource Context 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 External Resource Context 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 External Resource Context 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.

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:

Read docs/project-context/external-resources.md (if present) to learn what is available and how to access it.
Read the target UI Spec or Design Doc's ## External Resources Used section for feature-specific identifiers.
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

Capturing a record requires an interactive hearing. The workflow using this skill owns the interaction mechanism and routing. Follow references/hearing.md for the hearing conditions, domain routing, two-phase hearing, storage protocol, and quality checklist.

Output Format

The project-tier file follows the structure in references/template.md. The project-tier file's heading levels and section names are fixed so downstream agents can locate sections deterministically.

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 — Hearing conditions, domain routing, storage protocol, quality checklist
references/frontend.md — Frontend domain axes
references/backend.md — Backend domain axes
references/api.md — API contract domain axes
references/infra.md — Infrastructure domain axes
references/template.md — Project-tier and feature-tier structure templates

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the External Resource Context AI skill do?

Why use External Resource Context on TypingMind?

Because you install it once and use it with any model. External Resource Context 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 External Resource Context in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/shinpr/claude-code-workflows/tree/main/dev-skills/skills/external-resource-context. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use External Resource Context?

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 External Resource Context?

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

Is the External Resource Context AI skill free?

Yes. It is published on GitHub by shinpr 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

Brainstorming

obra

CommunityPopular

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Executing Plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Using Superpowers

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Loop Me

Grill me about specs for the workflows I want to build, within this workspace.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

External Resource Context

Purpose

Storage Locations (Two-Tier)

Single Source of Truth Rule

Reference Protocol (For Downstream Consumers)

Capturing and Updating Records

Output Format

References

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now