external-resource-context

Record external resource access methods in docs/project-context/external-resources.md.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/darsoohoo/intake-bot --skill external-resource-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: external-resource-context
Source: https://github.com/darsoohoo/intake-bot/tree/main/.agents/skills/external-resource-context
Command: npx skills add https://github.com/darsoohoo/intake-bot --skill external-resource-context

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Discovers, confirms, and records external resource access methods for project design and implementation work, including design sources, design systems, API schemas, database schemas, IaC sources, secret stores, environment config, and verification environments. Use when external resource context needs to be discovered or refreshed, recorded in docs/project-context/external-resources.md, or referenced from a Design Doc/UI Spec.

Core Features & Use Cases

  • This skill helps Codex identify external resources such as design origins, design systems, API schemas, database schemas, IaC sources, secret stores, and environment configurations.
  • It records stable access methods and reuses recorded context during design, planning, implementation, and review.
  • It supports updating docs/project-context/external-resources.md and referencing from UI Specs or Design Docs.

Quick Start

Identify external resources and capture their access methods in docs/project-context/external-resources.md.

Frequently Asked Questions about external-resource-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document external resources like API schemas and database schemas for project design?

To document external resources like API schemas and database schemas, you record their stable access methods in docs/project-context/external-resources.md. This standardizes reference material and ensures traceability across frontend, backend, and infrastructure work.

What external resource context should I capture for infrastructure and design docs?

External resource context to capture includes design origins, design systems, API schemas, database schemas, IaC sources, secret stores, environment config, and verification environments. Recording these in external-resources.md ensures consistent references for design and implementation.

Can I reference external resource context directly from a UI Spec or Design Doc?

Yes, you can reference external resource context directly from a UI Spec or Design Doc. The skill supports updating docs/project-context/external-resources.md and linking these recorded contexts to ensure consistent reference material across project planning.

How do I standardize access methods for environment config and secret stores across a project?

You standardize access methods for environment config and secret stores by capturing their stable access details in docs/project-context/external-resources.md. Applying reference templates ensures this data remains consistent and traceable across all design and implementation phases.