Skill Authoring

Define SKILL.md frontmatter and directory conventions for onscreen agent skills.

5|Updated May 6, 2026
One-click install
npx skills add https://github.com/binary16labs/prime-silo --skill skill-authoring-binary16labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Skill Authoring
Source: https://github.com/binary16labs/prime-silo/tree/main/app/L0/_all/mod/_core/skillset/ext/skills/development/skills
Command: npx skills add https://github.com/binary16labs/prime-silo --skill skill-authoring-binary16labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you correctly create or update onscreen agent skills so they can be discovered, loaded, and routed reliably in the Prime-Silo UI.

Core Features & Use Cases

  • Correct skill placement and layout guidance: Defines where first-party shared skills vs module-specific skills vs admin-scoped skills should live, using the ext/skills directory structure.
  • Catalog and loading rules: Explains how top-level ext/skills/* skills are discovered, how nested skills remain explicit-load-only, and how metadata.when tags gate eligibility.
  • Operational metadata controls: Documents metadata.when, metadata.loaded, and metadata.placement behaviors (system, transient, history) to ensure the right lifespan and injection model for skill content.

Quick Start

Add a SKILL.md at the correct ext/skills/<skill-id>/ path with name and description frontmatter, then use space.skills.load("<path>") to validate loading behavior in the current context.

Frequently Asked Questions about Skill Authoring

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

FAQPage Schema
How do I create onscreen agent skills that load reliably in the catalog?

Top-level ext/skills/* directories are auto-discovered by the catalog, while nested skills remain explicit-load-only, requiring manual space.skills.load("<path>") calls to inject their content into the runtime context.

How do I control context-gated eligibility for skill routing using metadata?

Define metadata.placement in SKILL.md frontmatter to control skill content lifespan and injection model, specifying system, transient, or history placement semantics for deterministic routing behavior.

How do I structure the ext/skills directory for first-party and module-specific skills?

Validate skill loading behavior by calling space.skills.load("<path>") in your current context after adding the SKILL.md file, checking whether the catalog discovers it or if it requires explicit loading.

What is the difference between auto-loaded and explicit-loaded skill routing?

Skills without external side effects ensure deterministic routing by relying on metadata.when tags and directory conventions, preventing unpredictable state changes during catalog discovery and runtime loading.