skill template generator

Data Community

Skill notes

When to Use

After extracting a pattern from a reference codebase, you need to package it as a reusable skill You want to create a new skill that teaches an agent how to perform a specific kind of task You are converting informal documentation or code examples into the SKILL.md format

SKILL.md Format

Every skill is a directory containing at minimum a SKILL.md file:

Frontmatter (Required)

The file MUST start with YAML frontmatter containing exactly two fields: Rules: name must match the directory name (kebab-case, lowercase) description should be 15-40 words, include key terms an LLM would search for No other frontmatter fields — everything else goes in the markdown body

Body Structure

The markdown body follows this template:

Step 1: Determine Skill Category

Match the pattern to one of three OpenSpace categories: Category · Use When · Example tool_guide · The skill teaches how to use a specific tool or technique · "How to analyze a codebase", "How to use Finnhub API" workflow · The skill prescribes an end-to-end procedure with ordered steps · "Create a panel component", "Set up API proxy endpoint" reference · The skill provides knowledge that informs decisions · "WorldMonitor architecture index", "News API comparison"

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Data
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@HKUDS · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Required · Vendor-specific
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Determine Skill Category

Match the pattern to one of three OpenSpace categories: Category · Use When · Example `tool_guide` · The skill teaches how to use a specific tool or technique · "How to analyze a codebase", "How to use Finnhub API" `workflow` · The skill prescribes an end-to-end procedure with ordered steps · "Create a panel component", "Set up API proxy endpoint" `reference` · The skill provides knowledge that informs decisions · "WorldMonitor architecture index", "News API comparison"

02
Step 2: Write the Description

The `description` field is the most critical line — it determines whether OpenSpace selects this skill for a given task. Good descriptions (specific, searchable): "Create a dashboard panel component using vanilla TypeScript DOM API, following the worldmonitor Panel architecture." "Integrate with Finnhub Stock API for real-time and historical stock market data." "CSS grid layout system for a responsive panel dashboard with dark theme."

03
Step 3: Write Actionable Instructions

The body must be concrete enough that an AI agent can follow it without guessing.

04
Step 4: Add Dependency Hints

If the skill depends on patterns from other skills, mention them explicitly: This helps OpenSpace understand skill composition when DERIVING new skills.

05
Step 5: Validate the Skill

Before saving, verify: Frontmatter is valid YAML — no tabs, proper indentation, quotes around special chars Name matches directory — `name: foo-bar` lives in `foo-bar/SKILL.md` Code blocks are complete — every snippet can be copy-pasted and run No broken references — all file paths and URLs are valid

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.