reference-pack

Explain the gbrain skillpack contract and required artifacts for validation.

1|Updated May 9, 2026
One-click install
npx skills add https://github.com/weiping/gbrain-cn --skill reference-pack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reference-pack
Source: https://github.com/weiping/gbrain-cn/tree/main/examples/skillpack-reference/skills/reference-pack
Command: npx skills add https://github.com/weiping/gbrain-cn --skill reference-pack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Users need a clear, canonical reference for how third-party gbrain skillpacks are structured and what artifacts must exist for the skillpack contract to be valid and publishable.

Core Features & Use Cases

  • Explains the 10/10 skillpack contract by pointing to the four pack artifacts every third-party pack must ship.
  • Covers routing and authoring expectations so agents can route user requests to the correct skill via skill triggers.
  • Describes what the “doctor” scores and how to pass checks so publishers can correct missing metadata, tests, and required files.

Quick Start

Ask your agent to explain the skillpack contract, and it will direct you to the required artifacts inside the pack.

Frequently Asked Questions about reference-pack

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

FAQPage Schema
What is the 10/10 skillpack contract for third-party publishing?

The 10/10 skillpack contract specifies the four required artifacts every third-party pack must ship: skillpack.json metadata, SKILL.md frontmatter and body, bootstrap runbooks, and CHANGELOG version entries.

How do I validate third-party skillpack artifacts before publishing?

You validate skillpack artifacts by applying the doctor rubric, which scores required metadata, routing files, and CHANGELOG version entries to ensure your pack passes publish-time validation checks.

How does skill routing work for third-party skillpacks?

Skill routing relies on SKILL.md frontmatter and routing-eval intent coverage to map user requests to the correct skill triggers, ensuring agents direct queries to the appropriate skillpack behaviors.

What files are required in a third-party skillpack directory structure?

Required files include skillpack.json metadata, skills/<name>/SKILL.md with YAML frontmatter and body, runbooks/bootstrap.md steps, and CHANGELOG version entries to satisfy the skillpack contract.

Why does the skillpack doctor rubric fail validation checks?

The doctor rubric fails validation when skillpacks are missing required metadata, YAML frontmatter, bootstrap runbook steps, or CHANGELOG version entries needed to satisfy the skillpack contract.

Do I need YAML frontmatter in SKILL.md for skillpack discovery?

Yes, YAML frontmatter in skills/<name>/SKILL.md is required for skillpack discovery and routing, as it provides the metadata agents use to map user requests to the correct skill triggers.