C✳CODEZ.WIN
🌐 English

Localized reading guide

setupPurpose, usage and source

First-run setup - checks which tools are connected, shows what's connected and what each one unlocks, learns how you write from your sent email, and renders a starter dashboard right away with no upfront interview. When tools are missing it walks through connecting the CRM, then email, then calendar, showing something useful after each. Use on first open, or when the user says "set me up", "get started", "what's connected", "learn my voice", "match my writing style", or "onboard me".

Source retrieved:

Source repository
anthropics/knowledge-work-plugins
SKILL.md
sales/skills/setup/SKILL.md
Repository stars
34,049
Repository updated
2026-10-30
Categories
Documents
Last collected

License: License file needs review

Source SKILL.md

Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.

The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.

What this Skill does

First-run setup - checks which tools are connected, shows what's connected and what each one unlocks, learns how you write from your sent email, and renders a starter dashboard right away with no upfront interview. When tools are missing it walks through connecting the CRM, then email, then calendar, showing something useful after each. Use on first open, or when the user says "set me up", "get started", "what's connected", "learn my voice", "match my writing style", or "onboard me".

How the upstream workflow works

Connecting more tools (when tools are missing)

The only asks in setup are the connect clicks a user must make anyway. Each new connection shows something useful right away, and the wait for the next one is filled with something worth reading. Order is book, conversations, schedule: CRM (or the uploaded book when nothing is connected). The moment it is readable, say plainly what is running ("reading your open opps and accounts, read-only") and run a first read: book shape, where the pipeline value sits, what is closing, what is stale. Render the first dashboard and a short summary ("this is what you are focused on"). THEN point at email - the user reads the summary while they go connect it. Two first reads. Second, the sent folder: learn the user's writing voice (above) and show "this is how you write".

Upstream passage · L117 ↗

Flow

Check what is connected, quietly - one cheap read per connected tool (who-am-I, or a one-record list; never a write), with no questions: CRM, email, calendar, chat, docs, call recorder, enrichment and sales engagement tools. Take the internal email domain from the signed-in mailbox; if colleagues show up on a second domain, ask once. On Microsoft 365, a Teams meeting carries a transcript link only when it was transcribed; in-room and dial-in meetings have none, so say "no transcripts for non-Teams meetings", not "no transcripts".

Upstream passage · L34 ↗

Learn the user's writing voice

Clean - strip quoted reply text, forwarded headers, the signature block (repeated identical trailing lines, kept separately as the user's signature), and calendar-invite boilerplate.

Upstream passage · L78 ↗
Upstream passage · ↗
tiers:
  files-only:   starter dashboard from whatever is uploaded; action tiles
                name what to connect; voice from 5-10 pasted sent emails,
                or "not learned yet" below 5; zero questions
  read-only:    role/book inferred, dashboard live from crm + calendar
                + email + transcripts; voice from 30-60 sent emails
  gated-writes: adds write actions to dashboard tiles (each runs when the
                user clicks it, within connector permissions)

Requirements and setup

Setup

Rules (apply to every step of this skill): Work silently between tool calls and batch independent reads. When the user asks for an action (update a record, send an email, post to chat, book a meeting), take it through the connector. When the skill suggests a change the user did not ask for, show the change and its evidence and let the user decide. Permissions live in each connector's own settings (allow, ask or block per tool): never add a restriction the connector does not impose, and never refuse an action the user asked for on the plugin's own authority.

Upstream passage · L6 ↗

Limits and quality checks

No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.

Start with a safe trial

  1. Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
  2. Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
  3. Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
  4. Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.

Skill format and directory specification ↗

Read further in the source

Translation and scope

This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.

This introduction refers to the pinned version below; current repository activity and collection time are shown separately.

Source retrieved
Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d
Source SHA-256
243b20b050a2a1de8ed5cd96a58218da453a307c89533613d2e3274c54f4bcdf
Back to the full Skill catalog