skill-create
Scaffold a new skill in the monorepo with a valid manifest and catalog entry. Use when creating any new skill.
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 13
- Forks
- 6
01 前言 Front Matter
- name
- skill-create
- description
- Scaffold a new skill in the monorepo with a valid manifest and catalog entry. Use when creating any new skill.
- allowed-tools
- Read, Grep, Glob, ApplyPatch, Write
- argument-hint
- [skill-name] [--from <tool-ref>] [type: opencode|OpenClaw|n8n]
- disable-model-invocation
- true
02 资源文件 2
- 参考文档manifest.yaml541 B
- 脚本scripts/discover-tool15.2 KB
03 SKILL.md 正文
Skill Create — Monorepo Scaffold
Purpose
Create a new skill in the monorepo with a valid manifest.yaml and a catalog entry. Enforce secure defaults and prevent duplicates.
Inputs
-
Skill name (kebab-case)
-
Type:
opencode|OpenClaw|n8n -
Install scope:
local-repo|global -
Owner
-
Blast radius:
low|medium|high -
Description
-
Permissions (explicit list)
-
Data categories (e.g.,
pii,financial,credentials,none) -
Egress allowlist (domains or services)
-
Invoke command/trigger
-
Phase(s)
-
--fromflag (optional): A tool reference (CLI command name or URL) to discover capabilities from -
Template paths are resolved from
${AGENTS_SKILLS_ROOT}/skill-create/.
Steps
- Validate naming
- Ensure name is lowercase, kebab-case, and ≤ 64 chars.
1b. Discovery phase (only if
--fromis provided) - Run the discover-tool script:
python3 ${AGENTS_SKILLS_ROOT}/skill-create/scripts/discover-tool "<from-value>" - Parse the JSON output
- Use discovered data to pre-populate:
- Description (from
descriptionfield) - Dependencies (from
dependenciesfield) - Permissions (from
suggested_permissionsfield) - Egress (from
suggested_egressfield) - For CLI type: create command docs based on discovered command groups
- For API type: create command docs based on discovered endpoints
- Description (from
- Present the pre-populated scaffold to the user for review BEFORE writing files
- User can modify, remove, or add to any pre-populated field
- If user approves, proceed with normal scaffold using pre-populated values
- If user rejects or discovery fails, fall back to normal interactive scaffold
- Ensure name is lowercase, kebab-case, and ≤ 64 chars.
1b. Discovery phase (only if
- Choose install scope (required)
- Ask the user whether the skill should be installed as:
local-repo(Recommended for repo-specific automation) ->.agents/skills/<skill-name>/global(shared Harnessy skill) ->tools/flow-install/skills/<skill-name>/
- If the user is unsure, recommend
local-repounless the skill is intended for cross-repo reuse through Harnessy installation.
- Ask the user whether the skill should be installed as:
- Check for duplicates (required)
- Search both
.agents/skillsandtools/flow-install/skillsfor matching skill names. - Search
.agents/OpenClawand.agents/n8nwhen applicable. - Search
.jarvis/context/skills/_catalog.mdfor existing entries with the same name or invoke command. - If any match is found, STOP and report the conflict.
- Search both
- Create directory
- For
local-repo, create.agents/<type>/<skill-name>/. - For
global, createtools/flow-install/<type>/<skill-name>/.
- For
- Design the intelligence ↔ determinism split
- Put orchestration, intent parsing, and decision-making in
SKILL.md. - Put repeatable logic (parsing, transforms, formatting, API calls) into
scripts/inside the skill folder. - If the script should be terminal-callable, name the executable after the final command so installation can expose it through the user-local bin directory (
$XDG_BIN_HOMEor~/.local/bin). - The skill must describe when to call scripts and what input/output contracts they expect.
- Put orchestration, intent parsing, and decision-making in
- Write
manifest.yamlusingtemplates/manifest.yaml.- Autoresearch is mandatory: all Harnessy skills include
autoresearch: enabled: trueby default. Settime_budget_secondsbased on blast_radius: high=1800, medium=1200, low=600.
- Autoresearch is mandatory: all Harnessy skills include
- Write
SKILL.mdusingtemplates/SKILL.md(fill in purpose, inputs, steps, output).- If the skill delegates to command docs, reference them as
${AGENTS_SKILLS_ROOT}/<skill-name>/commands/<file-name>.md. - Do not use fragile references like
./commands/<file-name>.md. - Include this mandatory line in every skill doc:
Template paths are resolved from ${AGENTS_SKILLS_ROOT}/<skill-name>/. - When
templates/...is used, resolve it from${AGENTS_SKILLS_ROOT}/<skill-name>/. - For
local-repo, keep skill runtime scripts under.agents/skills/<skill-name>/scripts/. - For
global, keep skill runtime scripts undertools/flow-install/skills/<skill-name>/scripts/.
- If the skill delegates to command docs, reference them as
- Add catalog entry in
.jarvis/context/skills/_catalog.mdusingtemplates/catalog-entry.md. - Register skills when required
- For
local-repo, runpnpm skills:registerto install the skill to${AGENTS_SKILLS_ROOT}. - For
global, update the shared source of truth and note any install/sync step the user should run afterward.
- For
- Return a checklist for validation and publishing.
Templates
templates/manifest.yamltemplates/SKILL.mdtemplates/catalog-entry.md
Checklist (Return to User)
- [ ] Verify
autoresearchsection is present inmanifest.yaml - [ ] Run
/skill-validate <skill-name> - [ ] If local-repo: run
pnpm skills:register(installs to${AGENTS_SKILLS_ROOT}) - [ ] If global: sync the shared skill install path after review
- [ ] Add test evidence for blast radius
- [ ] If high blast radius: get explicit approval before publish
Deterministic Logic (Scripts)
scripts/discover-tool— Takes a tool reference string (CLI command or URL), outputs JSON describing the tool's capabilities. Used by the--fromflag discovery phase.- Input: positional arg (tool reference), optional
--depth N - Output: JSON to stdout with tool_name, source_type, commands/endpoints, flags, dependencies
- Input: positional arg (tool reference), optional
Feedback Capture
After completion, ask the user: "Any feedback on this run? (skip to finish)" If provided, capture it:
python3 "${AGENTS_SKILLS_ROOT}/_shared/trace_capture.py" capture \
--skill "skill-create" --gate "run_retrospective" --gate-type "retrospective" \
--outcome "approved" --feedback "<user's feedback>"
04 同仓库更多 Skills
personal-knowledge
Save sources to the private Harnessy learning library, sync delivered readings, answer questions from saved evidence, browse its wiki, and generate weekly learning reviews.
valid-skill
A valid skill for testing purposes.
unknown-field
A skill with an unknown frontmatter field.
nested-child
Nested skill should be ignored.
root-skill-preferred
Root skill should win.
no-frontmatter
暂无简介