Skills

Skills in the catalog

The catalog contains these skill ids. Start with skill-authoring when you need to create or edit a workspace skill.

Read a skill before editing it

Search the catalog before you create a new skill. Read the matching skill, its Markdown, frontmatter, supporting pages, and current revision. A supporting page is only needed when the task needs that detail.

Write a useful skill

A useful skill has one thesis line, an invariant, a short numbered practice, guardrails, and a clear return. Keep SKILL.md near 5 KB and place detail, examples, and edge cases in supporting pages when needed.

Before saving an edit, read the current revision. Change only what was requested, preserve the required frontmatter, then read the saved result. If another editor saved first, re-read and merge rather than sending the older text over their revision.

When it goes wrong

If a search finds an existing skill, add the needed section there instead of duplicating the practice. If an edit descriptor is unavailable for a starter skill, wait for its workspace copy to appear and read the catalog again. If a revision conflicts, re-read the current text and merge the requested change.

Architect should use skills_list or skills_get to inspect guidance, then use tools_search and tools_get to find exact schemas. Search can return runnable contracts, and a run is refused as capability_not_fetched if the contract was not delivered in the current turn.

If a skill changed after it was read, re-read the current Markdown and merge the requested update. Do not overwrite a collaborator’s revision with an older local copy or create a duplicate practice.

A good skill update is visible in the skill catalog or workspace copy, retains required frontmatter, names a concrete practice and guardrails, and points the user to actual evidence for verification.

If a skill names an old pack or stale workflow, use the current product pack and canonical capability contract. The catalog is the authority for executable work, while the skill remains a source of practice guidance.

Read the current source before correcting guidance. Preserve the task-specific practice and link it to the current capability authority.

Choose guidance, not permission

The declared catalog has eighteen skill ids. A skill is a Markdown practice with its SKILL.md and, where needed, supporting Markdown pages served through skills_list and skills_get.

Skills describe how to work, not what an account may do. A skill neither grants permission nor binds a tool, and capability authority remains in the active customer-facing catalog.

The knowledge skill covers the practice of durable workspace knowledge. It should direct an agent toward visible Context documents rather than an undocumented private memory.

list-building is named Workbook building in the skill catalog. Lists happen only inside a workbook, with worksheets, one row source per worksheet, enrichment and judging columns, and an optional score.

The outreach skill teaches sequence building. Sequence steps are separate from sending: a sequence can be drafted, validated, published, enrolled, started, delivered, and replied in distinct stages.

The social, linkedin-posts, x-posts, and reddit-posts skills support social practice. They do not turn a draft into a publish action or bypass the relevant social capability contract.

The visibility skill teaches measurement discipline. It keeps citation and rank evidence, provider coverage, windows, and completeness separate rather than treating a bounded result as a universal score.

The workflows skill concerns deterministic automation graphs, triggers, conditional actions, runs, failures, replay, and metrics. It is distinct from sequence cadence and authoring.

The writing skill helps an agent shape content. It does not promise a system spending confirmation or publish authority, because credit limits and explicit capability choices govern paid work and effects.

inbox-replies guides a reply in an existing conversation. It is distinct from net-new outreach, and a draft reply does not send an external message.

Use a skill with the contract

The plays skill points users to the blueprint catalog play list. Choose by stage and needs against real workspace state, then inspect every ordered capability rather than treating the skill as a second catalog.

first-win focuses on setting up Context, sourcing, a workbook, a worksheet, a sampled row-source run, evidence, and a score. It is a practice for early work, not an automatic campaign.

diagnostics helps investigate a failure from actual receipts, state, and capability results. It should not invent a cure when the evidence only shows a missing credential, connection, or prerequisite.

worksheet-tidy focuses on repairing worksheet quality. The workbook remains the home of list work, while canonical CRM truth belongs to the CRM surface.

The crm skill concerns canonical CRM records. It must not describe a system confirmation for spend, because credit ceilings and runtime quotes are the product mechanism for consent to paid work.

linkedin-warm-signals supports a warm-network practice. It should not call a non-existent pack; the corresponding product pack ids have defined boundaries.

skill-authoring is the featured practice for creating or editing a workspace skill. It directs the author to inspect current content, frontmatter, supporting files, and revisions before saving focused changes.

Before work changes shared state, check the current app object, exact capability schema, mode, credit policy, and result. The skill gives the method; the discovered contract determines the call.