Docs & writing
16,641 rows, by stacks then stars
3,030 of these skill files have been read, by 1,951 distinct authors, and what they tell an agent counted. What Docs & writing authors agree on, and what they forbid
itallstartedwithaidea/google-ads-skills/skills/google-ads-write Skill
46★ repoSafe Google Ads write operations using the Confirm-Execute-Postcheck (CEP) protocol. Activate when the user wants to pause campaigns, change bids, update budgets, add keywords, create ads, or make any modification to their Google Ads account. Every mutation requires explicit user confirmation before execution.
The same file is in 1 other repository
kesslernity/awesome-copilot-cowork-skills/skills/project-management/project-status-tracker Skill
46★ repoMaintains living project files (project.md, decisions.md, risks.md, links.md) in a per-project OneDrive folder from emails, Teams channels and meeting transcripts, and generates a weekly DRAFT status document in Word. Use when the user asks to set up tracking for a project, update a project's status files, log a decision or risk, or produce a weekly status report for a named project.
The same file is in 1 other repository
kesslernity/awesome-copilot-cowork-skills/skills/reporting-analysis/report-attachment-analyzer Skill
46★ repoTracks a recurring emailed report end to end. It finds new report emails in the inbox, extracts data from their attachments, appends each reporting period to a trends spreadsheet, and rewrites a summary document with period-on-period deltas and flagged anomalies. Use when the user asks to update or analyse trends for a report that arrives by email on a schedule, or asks what changed in the latest weekly or monthly report.
The same file is in 1 other repository
kesslernity/awesome-copilot-cowork-skills/skills/sales-bd/estimate-to-sow Skill
46★ repoConverts a priced estimate spreadsheet into a populated statement of work document using the user's own SOW template. Validates that line items, hours, rates and totals add up before drafting, flags every discrepancy, and produces a DRAFT-labelled Word document plus a validation report. Use when the user asks to turn an estimate, quote or pricing spreadsheet into an SOW, statement of work, or scope document.
The same file is in 1 other repository
kesslernity/awesome-copilot-cowork-skills/skills/writing-communication/write-like-me Skill
46★ repoBuilds a personal voice profile from roughly 90 days of the user's sent email and meeting transcripts, then drafts emails and documents that match how the user actually writes. Use when the user asks to write like me, match my voice or tone, build or refresh my voice profile, or wants an email or document drafted in their own style.
The same file is in 1 other repository
BagelHole/DevOps-Security-Agent-Skills/compliance/continuity/runbook-creation Skill
46★ repoCreate operational runbooks and standard operating procedures. Document troubleshooting guides and recovery procedures. Use when documenting operational knowledge.
Kanevry/session-orchestrator/skills/vault-mirror Skill
45★ repoUse when you need to populate the Meta-Vault with machine-generated notes derived from session-orchestrator JSONL records. Converts entries from `.orchestrator/metrics/sessions.jsonl` and `.orchestrator/metrics/learnings.jsonl` into vault-conformant Markdown under `50-sessions/` and `40-learnings/`. Called automatically at session-end Phase 3.7 and after evolve Phase 3.5 — only when `vault-integration.enabled=true` and `vault-integration.mode != "off"`. Idempotent: re-runs safely; skips hand-authored notes. Triggers: "mirror to vault", "sync session notes to vault", "write learning notes to vault", "vault-mirror failed at session close". <example>Context: session-end is finalizing, vault-integration.mode is "warn". user: "/close" assistant: "Running vault-mirror to write 50-sessions/session-2026-05-17.md from the closing session record — 1 created, 0 skipped."</example>
Kanevry/session-orchestrator/skills/write-executable-plan Skill
45★ repoUse when you have a PRD or design spec and need a bite-sized, executable implementation plan that any agent can follow without re-deriving structure. Produces `docs/plans/YYYY-MM-DD-<feature>.md` with per-task Files block, complete code per step (no placeholders), and exact verification commands. Rejects "TBD", "TODO", "add error handling", "similar to Task N".
t3chnaztea/unifi-skills/skills/unifi-context-map Skill
45★ repoUse when an agent keeps guessing wrong about a UniFi network, when starting recurring agent work against a gateway, or when asked to "map my network", "document my UniFi setup", "build a network inventory", "what's on my network", "why does the agent keep using the wrong AP", or "audit my reservations against reality". Covers writing and maintaining the site map file: networks, devices, SSIDs, reservations, zones, an append-only Gotchas list, provenance checks that keep it honest, and the security rules for a file that is a burglary aid if it leaks. Assumes unifi-connect. Not for making changes to any of it (unifi-firewall, unifi-wifi, unifi-clients).
tale-project/tale/.agents/skills/create-issue Skill
45★ repoUse this skill whenever you file a GitHub issue — a bug report, an improvement, a feature request, or an epic — and whenever you hit a defect or missing capability that is out of scope for the change at hand. It owns the filing discipline: search open and closed issues for duplicates first (comment and link instead of re-filing), ground the report in observed behaviour with a repro and code pointers, write to the house format (typed title, Problem / Current behaviour / Proposed change / Acceptance criteria), label from the existing label set, cross-link related issues, then file with gh issue create. Load it the moment a task says "file an issue", "create a ticket", "report a bug", "open an issue", or "track this". Never file an ungrounded or duplicate issue — it wastes the triage it was meant to start. To investigate and fix the defect use fix-bug; to land a finished change use create-pr.
tale-project/tale/.agents/skills/deep-research Skill
45★ repoUse this skill whenever a decision depends on facts you don't have — an unfamiliar domain or technology, choosing a dependency, an external API or standard you've never used, conflicting evidence, or any claim your design will load-bear on. It is the discipline of researching before acting: write the questions first, work the sources in order (this codebase, the project's own docs, official docs at the version the project uses, then the web), cross-check every load-bearing claim against a second independent source or a local experiment, record findings with confidence and evidence in your note, stop at diminishing returns, and hand off to the skill that owns the work. Load it when a task says "research", "investigate", "evaluate", "compare", "which library", or "how does X work", and whenever you catch yourself deciding on a guess. Never adopt a dependency or API contract from a single unverified source. To locate code or concepts inside the repo, use search-codebase instead.
tale-project/tale/.agents/skills/produce-video Skill
45★ repoUse this skill whenever you produce, re-record, or localize a docs tutorial video — a new episode, a new locale of an existing one, a narration or choreography change, a voice/TTS change, or a red `videos` gate in services/docs/tests. It owns the production discipline end to end — storyboard-first authoring under services/platform/tests/docs-videos/episodes/, the billed ElevenLabs TTS stage and its cache, the planned-timeline recorder and its ±100 ms drift gate, the shared demo-org contract, the docs embed set (mp4+vtt+poster ×3 locales), and the watch-it QA gate. Load it before touching services/platform/tests/docs-videos/ or anything under services/docs/public/videos/. Never hand-record, hand-edit, or hand-place a video — every committed asset comes out of `bun run docs:videos`. For still screenshots use write-docs (its SCREENSHOTS.md); for the docs pages around the video use write-docs; for de/fr narration follow write-translations.
tale-project/tale/.agents/skills/test-code Skill
45★ repoUse this skill whenever you test a change or prove it works — write tests that exercise real behaviour (happy path + one edge + one error), run them and watch red→green, drive the real app for anything user-visible, and codify the check so it can't silently break. Load it before writing or changing any test, adding an end-to-end spec, deciding what to cover, or whenever asked to "verify", "test", or "confirm it works". Never claim a change is done on a green typecheck alone — observe the real outcome.
tale-project/tale/.agents/skills/write-agent Skill
45★ repoUse this skill whenever you create or update an agent in a Tale organization — a chat assistant, an image generator, or an external coding agent (Claude Code / Cursor). Triggers include: "create an agent", "change an agent's instructions, model, or tools", "give an agent a skill or integration", or an automation that needs its own agent. Never author an agent definition without it — and never create one before listing the existing agents and ruling out reuse. For the trigger→steps definitions an agent participates in, use write-workflow; for the installable bundle that groups agents, use write-automation.
tale-project/tale/.agents/skills/write-automation Skill
45★ repoUse this skill whenever you create or update an automation in a Tale organization — the installable bundle that groups workflows, agents, views, integrations, and configuration behind one manifest. Triggers include: "build an automation", "package these workflows and agents", "add a view or config field to an automation", or "make X installable". Never author a bundle without it — and never create one before listing the existing automations and ruling out extending one. For the pieces inside the bundle, use write-workflow, write-agent, write-skill, and write-integration.
tale-project/tale/.agents/skills/write-docs Skill
45★ repoUse this skill whenever you write or edit end-user documentation — a page under a docs content tree, a docs navigation or sidebar file, a docs landing or overview page, a screenshot or code example embedded in docs, or a failing docs structural check. It owns the journey-first method — organize every page around what the reader is trying to do, show the UI before describing it, prove behaviour with runnable examples, and use the docs component vocabulary (steps, tabs, code groups, callouts, frames, cards) with discipline instead of walls of prose. Before writing anything, discover the repo's own docs contract — its docs guide, its component registry, its structural test suite — and let that contract override this skill's defaults. Never write a docs page from imagination, never describe a UI you have not driven, and never ship a hand-captured screenshot. Page-type playbooks, component rules, screenshot doctrine, worked examples, and mechanics live in companion files here.
tale-project/tale/.agents/skills/write-integration Skill
45★ repoUse this skill whenever you create or update an integration in a Tale organization — a connector definition for a REST API, SQL database, or IMAP/SMTP mailbox. Triggers include: "connect X", "add an operation to an integration", "set up OAuth / an API key for …", or a workflow or automation that needs an external system. Never author a connector without it — and never create one before listing the existing integrations; if one already reaches the system, add the missing operation to it instead. Workflows call integrations from action steps (write-workflow); automations declare them in requires.integrations (write-automation).
tale-project/tale/.agents/skills/write-notes Skill
45★ repoUse this skill whenever you start real work under any other skill — before you implement, fix, refactor, review, test, research, delegate, or author. It makes you write a short note FIRST: answer the active skill's note form (its questions) in a few lines, so your intent, reuse decision, and plan are explicit and reviewable before you act. Load it the moment you pick up implement-feature, make-improvement, fix-bug, review-code, review-pr, create-pr, test-code, deep-research, delegate-work, or an authoring skill. Never start the work before the note exists — thinking on paper is cheaper than a wrong change.
tale-project/tale/.agents/skills/write-skill Skill
45★ repoUse this skill whenever you create or update a skill in a Tale organization — a SKILL.md bundle that teaches agents a capability or procedure. Triggers include: "write/add a skill", "teach the agent to …", "package this procedure so agents can reuse it", or an agent that keeps needing the same instructions. Never author a SKILL.md without it — and never create one before listing the existing skills and ruling out reuse. To make an agent load a skill, bind it via skillBindings (write-agent); to ship skills inside an installable bundle, use write-automation.
tale-project/tale/.agents/skills/write-translations Skill
45★ repoUse this skill whenever you edit any non-English file under services/*/messages/ (e.g. de.json, fr.json), packages/ui/src/i18n/messages/, or any page under docs/<locale>/, add a locale, or touch a glossary term — Tale ships as one narrator written natively per language, never a word-for-word render of the English. Load it before touching any non-English string; never translate by rendering the source words. Per-locale voice doctrine lives in locales/<locale>/AGENTS.md; the loanword buckets in BUCKETS.md, the conventions template in CONVENTIONS.md, the glossary workflow in GLOSSARY_GUIDE.md.
tale-project/tale/.agents/skills/write-workflow Skill
45★ repoThe Orchestrator for AI Agents — Connect OpenClaw, Hermes Agent, Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Pi, and Qwen Code. Pool their knowledge, delegate tasks, and build your swarm of agents.
tale-project/tale/builtin-configs/skills/create-issue Skill
45★ repoUse this skill whenever you file a GitHub issue — a bug report, an improvement, a feature request, or an epic — and whenever you hit a defect or missing capability that is out of scope for the change at hand. It owns the filing discipline: search open and closed issues for duplicates first (comment and link instead of re-filing), ground the report in observed behaviour with a repro and code pointers, write to the house format (typed title, Problem / Current behaviour / Proposed change / Acceptance criteria), label from the existing label set, cross-link related issues, then file with gh issue create. Load it the moment a task says "file an issue", "create a ticket", "report a bug", "open an issue", or "track this". Never file an ungrounded or duplicate issue — it wastes the triage it was meant to start. To investigate and fix the defect use fix-bug; to land a finished change use create-pr.
tale-project/tale/builtin-configs/skills/deep-research Skill
45★ repoUse this skill whenever a decision depends on facts you don't have — an unfamiliar domain or technology, choosing a dependency, an external API or standard you've never used, conflicting evidence, or any claim your design will load-bear on. It is the discipline of researching before acting: write the questions first, work the sources in order (this codebase, the project's own docs, official docs at the version the project uses, then the web), cross-check every load-bearing claim against a second independent source or a local experiment, record findings with confidence and evidence in your note, stop at diminishing returns, and hand off to the skill that owns the work. Load it when a task says "research", "investigate", "evaluate", "compare", "which library", or "how does X work", and whenever you catch yourself deciding on a guess. Never adopt a dependency or API contract from a single unverified source. To locate code or concepts inside the repo, use search-codebase instead.
tale-project/tale/builtin-configs/skills/docx Skill
45★ repoUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
tale-project/tale/builtin-configs/skills/test-code Skill
45★ repoUse this skill whenever you test a change or prove it works — write tests that exercise real behaviour (happy path + one edge + one error), run them and watch red→green, drive the real app for anything user-visible, and codify the check so it can't silently break. Load it before writing or changing any test, adding an end-to-end spec, deciding what to cover, or whenever asked to "verify", "test", or "confirm it works". Never claim a change is done on a green typecheck alone — observe the real outcome.
tale-project/tale/builtin-configs/skills/write-agent Skill
45★ repoUse this skill whenever you create or update an agent in a Tale organization — a chat assistant, an image generator, or an external coding agent (Claude Code / Cursor). Triggers include: "create an agent", "change an agent's instructions, model, or tools", "give an agent a skill or integration", or an automation that needs its own agent. Never author an agent definition without it — and never create one before listing the existing agents and ruling out reuse. For the trigger→steps definitions an agent participates in, use write-workflow; for the installable bundle that groups agents, use write-automation.
tale-project/tale/builtin-configs/skills/write-automation Skill
45★ repoUse this skill whenever you create or update an automation in a Tale organization — the installable bundle that groups workflows, agents, views, integrations, and configuration behind one manifest. Triggers include: "build an automation", "package these workflows and agents", "add a view or config field to an automation", or "make X installable". Never author a bundle without it — and never create one before listing the existing automations and ruling out extending one. For the pieces inside the bundle, use write-workflow, write-agent, write-skill, and write-integration.
tale-project/tale/builtin-configs/skills/write-docs Skill
45★ repoUse this skill whenever you write or edit end-user documentation — a page under a docs content tree, a docs navigation or sidebar file, a docs landing or overview page, a screenshot or code example embedded in docs, or a failing docs structural check. It owns the journey-first method — organize every page around what the reader is trying to do, show the UI before describing it, prove behaviour with runnable examples, and use the docs component vocabulary (steps, tabs, code groups, callouts, frames, cards) with discipline instead of walls of prose. Before writing anything, discover the repo's own docs contract — its docs guide, its component registry, its structural test suite — and let that contract override this skill's defaults. Never write a docs page from imagination, never describe a UI you have not driven, and never ship a hand-captured screenshot. Page-type playbooks, component rules, screenshot doctrine, worked examples, and mechanics live in companion files here.
tale-project/tale/builtin-configs/skills/write-integration Skill
45★ repoUse this skill whenever you create or update an integration in a Tale organization — a connector definition for a REST API, SQL database, or IMAP/SMTP mailbox. Triggers include: "connect X", "add an operation to an integration", "set up OAuth / an API key for …", or a workflow or automation that needs an external system. Never author a connector without it — and never create one before listing the existing integrations; if one already reaches the system, add the missing operation to it instead. Workflows call integrations from action steps (write-workflow); automations declare them in requires.integrations (write-automation).
tale-project/tale/builtin-configs/skills/write-notes Skill
45★ repoUse this skill whenever you start real work under any other skill — before you implement, fix, refactor, review, test, research, delegate, or author. It makes you write a short note FIRST: answer the active skill's note form (its questions) in a few lines, so your intent, reuse decision, and plan are explicit and reviewable before you act. Load it the moment you pick up implement-feature, make-improvement, fix-bug, review-code, review-pr, create-pr, test-code, deep-research, delegate-work, or an authoring skill. Never start the work before the note exists — thinking on paper is cheaper than a wrong change.
tale-project/tale/builtin-configs/skills/write-skill Skill
45★ repoUse this skill whenever you create or update a skill in a Tale organization — a SKILL.md bundle that teaches agents a capability or procedure. Triggers include: "write/add a skill", "teach the agent to …", "package this procedure so agents can reuse it", or an agent that keeps needing the same instructions. Never author a SKILL.md without it — and never create one before listing the existing skills and ruling out reuse. To make an agent load a skill, bind it via skillBindings (write-agent); to ship skills inside an installable bundle, use write-automation.
tale-project/tale/builtin-configs/skills/write-workflow Skill
45★ repoThe Orchestrator for AI Agents — Connect OpenClaw, Hermes Agent, Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Pi, and Qwen Code. Pool their knowledge, delegate tasks, and build your swarm of agents.
tale-project/tale/builtin-configs/skills/xlsx Skill
45★ repoUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
AndrewNgGirl/SkillLens/skills/skill-scorer/examples/mega-pipeline/agents/docs Skill
45★ repoUse when the parent pipeline routes a docs-related PR review request. Reads the diff and emits structured docsFindings using the docs specialist heuristics.
AndrewNgGirl/SkillLens/skills/skill-scorer/examples/mega-pipeline/agents/i18n Skill
45★ repoUse when the parent pipeline routes a i18n-related PR review request. Reads the diff and emits structured i18nFindings using the i18n specialist heuristics.
P0g diversity rewrite checklist
gmaxxxie/ai-native-product-agent-skills/skills/p0g-diversity-rewrite-checklist Skill
no license45★ repo多元推荐改写清单。当团队想重写推荐系统时,最容易只在原目标函数上加一点随机。 这个 Skill 帮你避免"看起来更多元,底层仍然单一"。 基于《AI rebuild product needs》工具卡。
KevinKE93/Dev_Agent_OPC/dev-agent/skills/documentation-and-adrs Skill
no license45★ repoRecords decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
The same file is in 11 other repositories
Xopoko/build-swift-apps/skills/appstore-metadata-localizer Skill
45★ repoUse when App Store listing text must be translated or market-adapted across locales, including descriptions, keywords, What's New, subtitles, names, privacy text, and App Store Connect languages. Not for non-translation metadata edits, release-note drafting, or subscription/IAP display-name localization.
Xopoko/build-swift-apps/skills/appstore-metadata-sync Skill
45★ repoUse when App Store listing metadata in canonical `./metadata` JSON needs field edits, validation, push, keyword sync, or legacy fastlane migration. Not for translation-first localization, release-note drafting, or subscription/IAP display-name localizations.
Xopoko/build-swift-apps/skills/appstore-release-notes-writer Skill
45★ repoUse when the requested App Store artifact is What's New release notes or promotional text, drafted from git history, bullets, or free text and optionally localized. Not for full listing translation, canonical metadata field sync, or subscription/IAP display names.
AlemTuzlak/skills/skills/changelog Skill
no license45★ repoUse when the user wants to generate a changelog, release notes, or document what changed between versions, tags, or PRs
AlemTuzlak/skills/skills/docs Skill
no license45★ repoPersonal AI agent skills for Claude Code, Copilot, Codex, Gemini & Cursor — turn a PR or idea into marketing content, technical Slidev presentations, courses, changelogs, and rendered videos.
AlemTuzlak/skills/skills/marketing-pipeline Skill
no license45★ repoUse when the user wants to run multiple marketing skills together (brief, blog post, social copy, changelog, newsletter, video script) from a single input, or when they mention "marketing pipeline", "full marketing", or "launch content"
AlemTuzlak/skills/skills/newsletter Skill
no license45★ repoUse when the user wants to write a product update email, feature announcement newsletter, or digest email for users or subscribers
AlemTuzlak/skills/skills/teach-me Skill
no license45★ repoUse when the user wants to deeply learn a new topic from scratch. Runs a pre-interview (current knowledge, end-goal proficiency, depth, practice load, background, scope), researches online (articles, niche-influencer blogs, canonical docs, subtopic landscape), then produces a structured markdown course with mandatory visual diagrams, evidence-based learning-science features (retrieval practice, spaced callbacks, worked-example fading, concept ledger, jargon gate, analogy hygiene), and a self-contained interactive HTML mini-course. Triggers on /teach-me, "teach me about X", "I want to learn X", "deep dive on X", "create a course on X", "study X with me".
owainlewis/agent-skills/skills/humanizer Skill
44★ repoMy personal agent skills
Documentation quality improvement starter
ma-compbio-lab/SkillFoundry/skills/meta-maintenance/documentation-quality-improvement-starter Skill
44★ repoA framework for discovering, compiling, and validating reusable skills for scientific agents.
Workflow interoperability and translation starter
ma-compbio-lab/SkillFoundry/skills/reproducible-workflows/workflow-interoperability-and-translation-starter Skill
44★ repoA framework for discovering, compiling, and validating reusable skills for scientific agents.
Mkdocs summary catalog starter
ma-compbio-lab/SkillFoundry/skills/visualization-and-reporting/mkdocs-summary-catalog-starter Skill
44★ repoA framework for discovering, compiling, and validating reusable skills for scientific agents.
Plotly interactive report starter
ma-compbio-lab/SkillFoundry/skills/visualization-and-reporting/plotly-interactive-report-starter Skill
44★ repoA framework for discovering, compiling, and validating reusable skills for scientific agents.
Quarto notebook report starter
ma-compbio-lab/SkillFoundry/skills/visualization-and-reporting/quarto-notebook-report-starter Skill
44★ repoA framework for discovering, compiling, and validating reusable skills for scientific agents.
itallstartedwithaidea/agent-skills/skills/scientific-research/scientific-writing Skill
44★ repoScientific Writing guides the production of research papers, abstracts, grant proposals, and supplementary materials with proper citation management, LaTeX formatting, and journal-specific template compliance.
itallstartedwithaidea/agent-skills/skills/software-dev/writing-plans Skill
44★ repoWriting Plans decomposes any implementation task into a sequence of atomic steps, each completable in 2-5 minutes, with exact file paths, complete code blocks, and verification commands.
AsiaOstrich/universal-dev-skills/skills/documentation-guide Skill
no license43★ repoGuide documentation structure, README content, and project documentation best practices. Use when: creating README, documentation, docs folder, project setup. Keywords: README, docs, documentation, CONTRIBUTING, CHANGELOG, 文件, 說明文件.
sequenzia/agent-alchemy/claude/core-tools/skills/interview-me Skill
43★ repoConduct an adaptive interactive interview on any topic and produce a structured markdown report, summary, or implementation plan. Use when the user says "interview me", "interview me about", "run an interview on", "help me think through", or wants guided discovery on any subject. Also triggers on "talk me through", "explore X with me", "help me plan Y", or "walk me through my thinking on Z" when the user wants a guided conversation rather than a direct answer. Applies broadly — career decisions, project ideas, product direction, personal goals, research questions, team problems — not just technical topics.
The same file is in 2 other repositories
sequenzia/agent-alchemy/claude/core-tools/skills/technical-diagrams Skill
43★ repoProvides Mermaid diagram syntax, best practices, and styling rules for technical visualizations. Use when creating diagrams, flowcharts, sequence diagrams, class diagrams, state diagrams, ER diagrams, architecture diagrams, C4 diagrams, visualizations, or any visual documentation in markdown. Always use this skill when generating or updating Mermaid code blocks.
sequenzia/agent-alchemy/claude/dev-tools/skills/changelog-format Skill
43★ repoKeep a Changelog format guidelines and entry writing best practices. Use when writing changelog entries, updating CHANGELOG.md, or following Keep a Changelog specification.
The same file is in 2 other repositories
sequenzia/agent-alchemy/claude/dev-tools/skills/docs-manager Skill
43★ repoDocumentation management workflow for MkDocs sites and standalone markdown files — initialize, generate, update docs, and create change summaries. Use when asked to "create docs", "write README", "update documentation", "generate docs site", "write CONTRIBUTING", "manage documentation", or "docs changelog".
sequenzia/agent-alchemy/claude/dev-tools/skills/document-changes Skill
43★ repoGenerate a markdown report documenting codebase changes from the current session — files added, modified, deleted, and a summary of what was done. Use when asked to "document changes", "generate change report", "save changes report", "what did I change", "session report", "summarize my changes", or "write a changes report".
The same file is in 2 other repositories
cgallic/kai-cmo-harness/harness/skills/kai-newsletter Skill
no license43★ repoPlan and produce newsletter editions — content selection, subject lines, scheduling, and production with quality gates. Use when "newsletter", "plan newsletter", "newsletter content", "email newsletter", "weekly digest", or any request to create or manage a newsletter.