Run any Skill in Manus with one click

template-skill

Stars4

Forks0

UpdatedJuly 17, 2026 at 05:33

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

quivly

quivly/skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

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"}

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-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.

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.

More from this repository

same repository

account-360

quivly/skills

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.

2026-07-174

advocacy-finder

quivly/skills

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.

2026-07-174

at-risk-report

quivly/skills

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".

2026-07-174

champion-change

quivly/skills

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.

2026-07-174

churn-save-plan

quivly/skills

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".

2026-07-174

customer-health-review

quivly/skills

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.

2026-07-174

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"}

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-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.

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.