_template_reference_first

Create reusable skills with a reference-first architecture template.

497|38|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/WILLOSCAR/research-units-pipeline-skills --skill template-reference-first
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: _template_reference_first
Source: https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/_template_reference_first
Command: npx skills add https://github.com/WILLOSCAR/research-units-pipeline-skills --skill template-reference-first

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a standardized template for creating new, reusable skills within the repository, ensuring a consistent structure and separation of concerns.

Core Features & Use Cases

  • Structured Skill Design: Enforces a clear division between routing logic (SKILL.md), domain knowledge (references/), machine-readable contracts (assets/), and deterministic execution (scripts/).
  • Reusable Components: Facilitates the creation of skills that are easy to understand, maintain, and reuse across different workflows.
  • Use Case: When developing a new research assistant capability, use this template to quickly scaffold a well-organized skill that separates the core logic from explanatory text and examples.

Quick Start

Copy this template directory to start building a new skill.

Frequently Asked Questions about _template_reference_first

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

FAQPage Schema
How do I structure a reusable code skill to separate routing logic from domain knowledge?

To structure a reusable code skill with a reference-first architecture, use a standardized template that isolates routing logic, domain knowledge, machine-readable contracts, and deterministic execution scripts into distinct components. This separation of concerns ensures consistent skill development and easier maintenance.

What is a reference-first skill blueprint and when should I use it?

A reference-first skill blueprint is a standardized template for creating reusable skills that enforces separation of concerns between routing, domain knowledge, contracts, and execution scripts. You should use it when developing new research assistant capabilities to scaffold a well-organized skill quickly.

How do I scaffold a new skill that separates explanatory text from core execution logic?

Scaffold a new skill by copying a reference-first template directory. This approach separates core deterministic execution scripts from explanatory text and domain references, facilitating the creation of skills that are easy to understand, maintain, and reuse across different workflows.

Can I use this skill template for capabilities that require deterministic execution scripts?

Yes, this template enforces a clear division for deterministic execution scripts alongside routing logic and machine-readable contracts. It provides a standardized structure ensuring consistent skill design and separation of concerns for deterministic workflows.

What is the best way to maintain consistent skill development across different workflows?

The best way to maintain consistent skill development is to use a standardized template enforcing a reference-first architecture. It provides reusable components and a clear division between routing, domain knowledge, contracts, and scripts, ensuring skills remain easy to understand and maintain.

Why does my skill structure mix domain knowledge with routing logic?

Your skill structure mixes concerns because it lacks a reference-first template enforcing separation. Using a standardized blueprint isolates routing logic in SKILL.md, domain knowledge in references, contracts in assets, and execution in scripts to prevent this issue.