create-library-template
Skill59 starsChanged 3 months agoApache-2.0View on GitHub
Author or modify a Workflow Template Library template. Use when creating a template, migrating an example to a template, editing template-metadata or install.form, or preparing a template PR.
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
Read the CONTRIBUTING.md sections above.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Create a Workflow Template Library template
Where the rules are
Read CONTRIBUTING.md § "Authoring a template" before writing anything — do not work from memory. It is the single source of truth for the file layout, the template-metadata block, the categories vocabulary (library/categories.yaml), install.form and how __install__.* references render (the most common source of broken templates), step-type rules, and style. Local validation and the PR checklist are in § "Validating locally" and § "Pull request flow" of the same file.
Templates live at library/workflows/<slug>/<slug>.yaml — one directory per slug; directory, file name, and template-metadata.slug must match.
Migration references
Some templates were migrated from a plain workflow in examples/. Study a pair or two before authoring — the diff shows exactly what "templatizing" means (add the template-metadata block, promote operator-specific values and connector ids to install.form, drop banner comments, tidy step comments):
Template (library/workflows/) | Original example (examples/) |
create-slack-channel/create-slack-channel.yaml | integrations/slack/create-slack-channel.yaml |
hash-threat-check/hash-threat-check.yaml | security/detection/hash-threat-check.yaml |
ip-reputation-check/ip-reputation-check.yaml | security/enrichment/ip-reputation-check.yaml |
mark-alert-as-acknowledged/mark-alert-as-acknowledged.yaml | security/detection/mark-alert-as-acknowledged.yaml |
root-cause-analysis/root-cause-analysis.yaml | observability/root-cause-analysis-rca-workflow.yaml |
semantic-knowledge-search/semantic-knowledge-search.yaml | search/semantic-knowledge-search.yaml |
web-search/web-search.yaml | search/web-search.yaml |
ip-reputation-check is the golden example referenced throughout CONTRIBUTING.md.
Workflow
- Read the CONTRIBUTING.md sections above.
- Pick the closest migration pair from the table and mirror its structure.
- Author the template; follow every rule in § "Authoring a template" (especially the
__install__.*rendering rules). - Validate per § "Validating locally" and open the PR per § "Pull request flow", including the validation output and a test plan.
In this repositoryOne other file it gives its agents.
- AGENTS.mdAGENTS.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.