Template
Skill quivly/skills/template
Production-ready Agent Skills for Customer Engineering, Post-Sales, and Customer Success teams. Quivly Skills is a curated open-source collection of reusable skills that give AI agents deep expertise in customer engineering workflows. Every skill follows the official Agent Skills specification.
npx -y skills add quivly/skills --skill templateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
A minimal starting template for a new Quivly skill. Replace this description with a clear explanation of what the skill does and when an agent should activate it.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.3 KB, as published. Nobody here has run it
Template Skill
Replace this with the actual skill name.
When to Use This Skill
Describe the situations, keywords, or customer scenarios that should trigger this skill. Be specific — this text is used by agents for discovery.
Good descriptions mention:
- The core task (e.g., "run a customer health review")
- Trigger signals ("when the user mentions churn risk, health score, or QBR")
- The outcome the agent should deliver
Instructions
Provide clear, step-by-step guidance the agent should follow. Reference tools by their short capability name so any runtime can map them:
- Load the customer record (
get-customer) and capture ARR, tier, and owner. - Search recent calls (
search-calls) for commitments and open questions. - ...
Tool Bindings
Two layers keep skills portable:
- The body (above) references tools by capability — "load the customer record (
get-customer)". Any runtime with equivalent tools can execute it; agents without tools fall back to asking the user for the data. metadata.quivly-toolsis a space-separated list of exact Quivly tool-catalog IDs. Quivly's GitHub import reads this to attach tools automatically. Other platforms ignore it per the Agent Skills spec.
In Claude Code / claude.ai, connect the Quivly MCP connector — its tool names map 1:1 to the short names used in skill bodies.
Examples
Example 1
Input: ... Expected behavior: ...
Guidelines & Best Practices
- Key constraint or rule
- Common pitfalls to avoid
- Flag gaps where data is missing rather than guessing.
References
Prefer a single self-contained SKILL.md — Quivly's importer only ingests the SKILL.md file. Use references/ only for material that is genuinely optional.