Writing & Communication
2,906 results
- Archivist InithunainahmedjScaffold the archivist documentation system for a project — creates the docs tree from the template, configures .archivist.json, wires CLAUDE.md/AGENTS.md briefing loading and Codex hooks. Run once per project, from the workspace root (multi-repo project) or the repo root (monorepo).
- Autohotkey V2alivirgoWrite AutoHotkey v2 desktop scripts for window management and Win32 integration; troubleshoot permissions and compile scripts with Ahk2Exe.
- Baton Passrhawk117Hand the current session to the next one without losing what this session learned. Works from an active ticket (mid-sprint, or after stick-the-landing went green and review is next) or from a session with no ticket at all.
- Board Setupmonday.comCreates and configures monday.com boards with proper structure including groups, columns, and initial items. monday.com boards are flexible enough to manage any workflow - project trackers, CRM pipelines, bug trackers, content calendars, and more.
- Bounded Loopsgaurav8936Make any repeated or self-paced agent work safe — a written goal, a machine-checkable stop condition, a cap on attempts and time, a report after every round, and a clean way to interrupt.
- Capture Gotchasgaurav8936When something surprising breaks, write one short note — symptom, cause, fix, how to check — named after the symptom, in the shared gotchas folder, so the next session finds it before repeating the mistake.
- ChaffisamuCheck prose with chaff (npx chaffjs): pick the genre preset for the kind of document (contract, statute, manual, FAQ, paper, fiction, transcript…), run it on Markdown or text, read each finding, fix the text or record why not, and tune chaff.yaml with rules --json and relax --why.
- Chief Of Staffkl-autonomousSet up and run a "chief of staff" session that stands between the owner (the human) and several other Claude Code sessions in the Claude desktop app. It relays the owner's words word for word, gathers every session's questions into one numbered round with recommended answers, keeps hand-offs between sessions moving, resends work that stalled, keeps a short status page, and says when a session…
- ClarifygwpicardInterview the team before work is specified, one question at a time, each with a best guess attached. Used by setup-ai-build-kit for the founding interview and by shape when a request is too vague to size. Do not use for small clear changes or for repairs, and never write code during it.
- ClarifygwpicardInterview the team before work is specified, one question at a time, each with a best guess attached. Used by setup-ai-build-kit for the founding interview and by shape when a request is too vague to size. Do not use for small clear changes or for repairs, and never write code during it.
- Claude Team LeadkubilaygulacdiDomain-independent playbook for running a software project as a team lead (TL) agent that leads coding agents, one per task in its own git worktree (any harness: built-in sub-agents or a terminal multiplexer) — the lead talks to the TL in chat, the TL opens one agent per task in its own git worktree with a brief, reviews the PR and squash-merges it into the integration branch (`dev`); `dev` →…
- CommandseyelockScaffold a skill in the current harness, write it properly, and prove it lands
- CommithyperstructureCommit and open pull requests in hyperstructure/sandbox. Covers Conventional Commit titles, breaking changes, what goes in the description, branch names, waiting for the checks, answering reviews, and what happens after the merge. Use when committing, naming a branch, writing a pull request title or description, or getting a change merged.
- Commitskrrt-shCreate focused conventional commits with a mandatory gitmoji. Use when the user asks to commit, write a commit message, or split changes into commits.
- Compact Status UpdatesalivirgoWrite brief progress updates that state the current result, relevant blocker, and next meaningful action.
- Compact Yaml FrontmatteralivirgoWrite concise YAML metadata for skills and documents with clear names, descriptions, and supported routing fields.
- Composing Agent PromptsbostonaholicComposes a self-contained, source-cited task prompt for another coding agent to execute in a target repository, without running the task. Use when the user asks to write, draft, or hand off a prompt, brief, or task spec for another agent. Not for system prompts; use writing-system-prompts.
- Conducting Deep ResearchbostonaholicConducts source-backed, goal-directed research that combines a scholarly evidence review with an institution, company, or funding map. Use when a request needs both an evidence review and an organization or funding map. Not for quick lookups or general research write-ups.
- ConfluencealivirgoOrganize Confluence page trees, macros, labels, and permissions; perform scoped content updates through the REST API.
- Connector GooglecalendarcaffeinelabsMANDATORY recipe for every Caffeine build that lists upcoming events or creates events on the user's own Google Calendar. The ONLY supported path is the `googlecalendar-client` mops package (Calendar REST API v3) combined with the `google-oauth` mops package (token exchange + refresh + PKCE).
- Connector GoogledrivecaffeinelabsMANDATORY recipe for every Caffeine build that lists, reads, creates, shares, or organizes files and folders on the user's own Google Drive. The ONLY supported path is the `googledrive-client` mops package (Drive REST API v3) combined with the `google-oauth` mops package (OAuth 2.0 token exchange + refresh + PKCE).
- Connector GooglemailcaffeinelabsMANDATORY recipe for every Caffeine build that sends email through the user's own Gmail account. The ONLY supported path is the `googlemail-client` mops package (Gmail REST API) combined with the `google-oauth` mops package (token exchange + refresh + PKCE).
- Connector TwiliocaffeinelabsEXPERIMENTAL, NOT YET VERIFIED AGAINST LIVE TWILIO, and it spends real money — every message is billed, and a US-bound production number additionally needs A2P 10DLC registration (fees, weeks of lead time). Say both things to the user before building.
- Connector XcaffeinelabsMANDATORY recipe for every Caffeine build that posts to X (Twitter) from a canister. The supported path is the `x-client` mops package (X API v2) over outbound HTTPS, with per-user OAuth 2.0 (PKCE, no client secret).