Skills for “writing”

Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.

Writing, exploit: shape raw material into an article, paragraph by paragraph.

Writing, explore: mine raw fragments, no structure yet.

Use when you have a spec or requirements for a multi-step task, before touching code

Use when creating new skills, editing existing skills, or verifying skills work before deployment

…or `update_list_property` call that sets a formula; never write a formula without loading it first. Use when writing, editing, or debugging Pigment metric or list property formulas — quoting, references, data types,…

Draft and revise source-backed GovCon responses, proposal narratives, RFI replies, and official correspondence. Exclude generic writing and unsupported claims about company capabilities.

--- name: Writing Plans description: Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context when_to_use: when design is complete and you need detailed implementation tasks…

Writing documents for agents. Use when creating or editing a skill (its SKILL.md, description or reference files), when modifying AGENTS.md or CLAUDE.md, or when reviewing an agent-facing document that behaves…

This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.

Execution skill. Use when reviewing or finalizing Pigment formulas before delivery. Provides the mandatory pre-delivery checklist, sparsity preservation rules, scope-first patterns, and anti-patterns to avoid.

Use when authoring an AG-IR — the typed intermediate representation Sigil lowers into a runnable agent — from a SKILL.md and its frozen rule set, verifying each draft with the compile oracle until every gate passes.

…own name, in plain language that does not read as machine-written. Use when drafting or editing a chat message, an email, a pull request description, a comment, a wiki page, an announcement or a post on the user's…

Writes the words of an ad — the headline, primary text, description and call to action that go into the ad platform's own fields, shaped to the channel it runs on. Handles one channel or several, returning copy sized to…

Draft and revise complete Clay Sequencer email sequences using supplied campaign strategy and context.

Write English that a reader cannot misread: one meaning per word, active voice, simple tenses, one idea per sentence, short sentences. Based on ASD-STE100 (Simplified Technical English), the controlled-language standard…

按事实与功能顺序直接撰写、改写或检查产品、工具、功能、项目和更新说明，内置 ASD-STE100 清晰表达原则，核对主体、动作、指代、术语、条件与承诺强度，保留原意和用户锁定的文字，不加营销钩子、痛点渲染和抽象包装。用户要求平铺直叙地写、不要营销腔、去掉说明文里的 AI 套路、把能力逐条写清、检查措辞歧义或只改指定一处时使用；中文为原则适配，不等于官方符合性认证。

…when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what…

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.