메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Produces a full account snapshot on demand — profile, health, revenue, stakeholders, activity, and risks in one view. Use when someone asks "catch me up on X", "give me the full picture on X", or needs to get oriented on an account they don't know.
Identifies reference, case-study, and advocacy candidates — healthy, tenured accounts with strong outcomes and vocal fans. Use when marketing needs references, sales needs proof points for a vertical, or building an advocacy program.
Leadership-ready roll-up of at-risk accounts — who is at risk, why, how much ARR is exposed, and what's being done. Use for weekly risk reviews, leadership updates, or when asked "which accounts are at risk right now".
Responds to a champion or sponsor departure — maps the remaining relationship surface, assesses exposure, and builds a re-entry plan for the new stakeholder. Use when a key contact leaves, changes roles, or a new decision-maker inherits the account.
Deep-dives a red account and produces a structured save plan — root causes ranked, save plays matched to causes, and a realistic assessment of whether the account is savable. Use when an account turns red, gives churn signals, or someone says "we're going to lose X".
Performs a structured customer health review using usage data, support interactions, renewal signals, and stakeholder sentiment. Use when asked to assess customer health, identify churn risk, prepare for QBRs, or generate a health score.
| name | template-skill |
| description | 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. |
| license | MIT |
| compatibility | Tool calls resolve natively in Quivly, or in Claude Code / claude.ai / any MCP-enabled agent via the Quivly MCP connector. Without tools, the skill degrades to a guided manual workflow. |
| metadata | {"author":"quivly","version":"1.0","category":"customer-engineering","quivly-tools":"customer-data.get-customer communication.search-calls"} |
Replace this with the actual skill name.
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:
Provide clear, step-by-step guidance the agent should follow. Reference tools by their short capability name so any runtime can map them:
get-customer) and capture ARR, tier, and owner.search-calls) for commitments and open questions.Two layers keep skills portable:
get-customer)". Any runtime with equivalent tools can execute it; agents without tools fall back to asking the user for the data.metadata.quivly-tools is 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.
Input: ... Expected behavior: ...
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.