add-resource

Integrate external JSON, YAML, and markdown files into plain specifications.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/Codeplain-ai/onboarding-flow --skill add-resource-codeplain-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-resource
Source: https://github.com/Codeplain-ai/onboarding-flow/tree/main/.claude/skills/add-resource
Command: npx skills add https://github.com/Codeplain-ai/onboarding-flow --skill add-resource-codeplain-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill allows users to link external files such as JSON schemas, API specifications, and data files directly into plain specifications, providing additional context and reducing the need for repetitive content.

Core Features & Use Cases

  • Link External Files: Add external files as references in plain specifications.
  • File Path Management: Ensures relative paths are used and resolves to valid text-based files.
  • Use Case: When writing a functional spec for a system, link to an external OpenAPI spec to provide API endpoint details.

Quick Start

Use the add-resource skill to link to an external JSON schema file at 'resources/auth_schema.json'.

Frequently Asked Questions about add-resource

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

FAQPage Schema
How do I link external files into a plain specification for code generation?

To link external files into a plain specification, you can reference text-based files directly to provide additional context for code generation. This approach reduces repetitive content by integrating external schemas and data files.

Can I use a JSON schema as an external reference in my specification?

Yes, you can use a JSON schema as an external reference in your specification. The functionality supports adding JSON, YAML, and markdown file formats to ensure your text-based files resolve correctly within the project structure.

How do I manage file paths when adding external resources to a specification?

When adding external resources to a specification, you must use relative file paths. The system ensures these paths resolve correctly within the project structure so that your text-based files are linked accurately.

What is the best way to include an OpenAPI spec in a functional spec?

The best way to include an OpenAPI spec in a functional spec is to link it as an external file. This provides API endpoint details directly within your plain specification without duplicating content.

Does this approach support markdown and YAML files for code generation?

Yes, this approach supports markdown and YAML files for code generation. You can integrate these text-based file formats as references to add necessary context to your plain specifications.

Why should I use external references instead of inline content in specifications?

You should use external references instead of inline content to reduce the need for repetitive content. Linking external files like data files and schemas directly provides additional context while keeping your plain specifications concise.