agentsclimarketplace

Docs & writing

16,632 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

  • Whitepapers

    SkillMedev/skills/skills/whitepapers Skill

    5★ repo

    Structures and writes authoritative B2B whitepapers - a standalone executive summary, a data-sized problem statement, methodology, evidence-driven findings, recommendations, and a soft call to action - flagging every claim that needs a real citation. Use when a marketer asks "write a whitepaper on this topic", "turn our research into a lead-gen asset", "make this credible enough for executives", or a draft reads like a product pitch instead of analysis. Do NOT use for customer-story-driven proof - use case-study-builder instead; for policy audiences, use policy-brief.

    The same file is in 1 other repository

  • Wikipedia style

    SkillMedev/skills/skills/wikipedia-style Skill

    5★ repo

    Writes neutral, verifiable, encyclopedic prose following Wikipedia's core content policies and manual of style - NPOV, inline citations, notability-backed claims, and a strict ban on promotional language. Use when someone asks "write this like a Wikipedia article", "draft a Wikipedia page for this company or person", "make this neutral and encyclopedic", or "why does my article draft keep getting rejected". Do NOT use for persuasive or opinion writing - use op-ed-writer instead; for thesis-driven academic papers, use academic-essay; for verifying claims in existing text, use fact-checker.

  • Youtube script writer

    SkillMedev/skills/skills/youtube-script-writer Skill

    5★ repo

    Writes retention-engineered long-form YouTube scripts on a hook/body/payoff architecture - a first-30-seconds hook that survives the retention cliff, a beat-sheet body with mini-hooks and bridges, timed pattern interrupts, and a payoff that over-delivers - with B-roll and editing cues marked inline. Use when someone says "script my next video", "my retention graph dies at the start", "tighten this draft", or "outline a video on X". Do NOT use for the 3-second opener of TikTok, Reels, or Shorts - use video-hook-writer instead; do NOT use for spoken voiceover synced to on-screen tutorial actions - use narration-script instead; do NOT use for a sales demo built on a buyer's discovery notes - use demo-script instead; do NOT use to design the thumbnail and title - use thumbnail-concept instead.

    The same file is in 1 other repository

  • Content strategy

    Sudhakaran88/solopreneur-skills/skills/content-strategy Skill

    5★ repo

    When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also trigger on "content strategy", "what should I write about", "content ideas", "blog strategy", "topic clusters", "content planning", "content calendar", "editorial calendar", "what content works for SaaS/ecom". For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media specifically, see social-content.

  • Copywriting

    Sudhakaran88/solopreneur-skills/skills/copywriting Skill

    5★ repo

    When the user wants to write, rewrite, or improve marketing copy for any page — homepage, landing pages, pricing, feature pages, about pages, product pages. Also trigger on "write copy for", "improve this copy", "rewrite this page", "marketing copy", "headline help", "CTA copy". For email copy, see email-sequence. For popup copy, see popup-cro. For ad copy, see ad-creative. For editing/polishing existing copy, see copy-editing.

  • Plot

    zapgun-ai/clawback/.skills/plot Skill

    no license5★ repo

    Render the tokens-saved chart from an analyzer output directory. Dependency-free SVG generator — reads summary.json + report.csv produced by benchmark/bin/analyze.js and emits TWO SVGs of the same cumulative billable-input story (passthrough baseline vs clawback, honest green/red shaded gap): tokens_saved.svg (labeled, titled "Token Efficiency", for on-screen) and tokens_saved.bg.svg (BARE 1200×630, lines + wedge only, no text — the share-card PNG background; without it the posted card has no chart lines). No cost/$/CI tables. Use after .skills/bench to produce the visuals that document the win.

  • Report smoke

    zapgun-ai/clawback/.skills/report_smoke Skill

    no license5★ repo

    End-to-end smoke test for the /<admin-path>/report saved-run viewer. Boots the real clawback binary against the repo's runs/ dir and curls every report route, asserting status + content, prefix mutability, public-read exemption, and that sensitive run-dir siblings stay unreachable. Use after touching src/report.js, src/report_ui/*, or the admin/report wiring.

  • Write config

    zapgun-ai/clawback/.skills/write-config Skill

    no license5★ repo

    Generate or refresh the canonical CLAWBACK.md config. The front matter is built from the live DEFAULTS export in src/config.js (so it can never drift as options are added), with the only forced deviations being the two a LAN-reachable bind needs — host=0.0.0.0 and tls=true. adminToken is left as a null placeholder for you to set (it no longer mints one); a real existing token, or an explicit CLAWBACK_CANONICAL_TOKEN, is PRESERVED, and a token's value is NEVER printed (only presence and length). With no args it writes BOTH ./CLAWBACK.md and the global ~/.config/clawback/CLAWBACK.md. Use to (re)create a canonical config, or after adding an option or changing a default.

  • Unit test

    HsuanYuLee/polaris/.claude/skills/unit-test Skill

    5★ repo

    Project-aware unit testing guide with mock patterns, TDD discipline, and best practices. Auto-detects test framework (Jest/Vitest) and provides appropriate examples. Use when: (1) writing or fixing unit tests, (2) user says "寫測試", "write test", "補測試", "add test", (3) user encounters mock patterns or test failures, (4) user asks how to test a composable, component, or store, (5) user says "mock imports", "test store", "怎麼測", "測試怎麼寫", (6) reviewing test quality: "unit test review", "review tests", "check test quality", "測試審查", "review 測試", "測試品質", "檢查測試品質", (7) TDD workflow: "TDD", "test driven", "紅綠燈", "先寫測試", "test first", "red green refactor".

  • Scene inventory extractor v2

    leynos/visual-storytelling-skills/skills/scene-inventory-extractor-v2 Skill

    5★ repo

    End-to-end production-prep workflow: extracts comprehensive scene inventories from narrative writing, extracts continuity inventory and reset-critical state before prompt writing, generates all reference images (characters, locations under multiple angles/conditions, props), produces start/end/keyframe shot references with consistency verification, and then hands off to shot-specifier for per-shot direction, model routing, and prompt manifests. Use when analysing stories, scripts, or prose to create production-ready scene breakdowns with full visual asset pipelines. Also trigger when the user mentions "scene breakdown", "shot list", "character bible", "location bible", "continuity inventory", "reference images", "storyboarding", or any request to prepare narrative material for AI video generation. This skill expects access to an image-generation MCP and vision capabilities.

  • Lynqu pipeline report

    Gravisun/lynqu-ai-toolkit/skills/lynqu-pipeline-report Skill

    no license5★ repo

    Generate a pipeline and performance report from Lynqu — what moved, what's stalling, campaign and event ROI, card engagement, and who needs attention. Use for weekly pipeline review, sales reporting, "how's the pipeline looking", campaign performance, lead/card analytics, or a stand-up summary. Read-only. Requires the Lynqu MCP server connected (https://api.lynqu.com/mcp/v2).

  • Memory sync

    ramboz/jig/hosts/claude/skills/memory-sync Skill

    5★ repo

    Persist new context, terms, learnings, and settled lightweight decisions. Use when the user says remember this, save this for later, add to glossary, note this down, or at session end to consolidate what was learned — that goes to the memory layer (CLAUDE.md hot cache, docs/memory/, docs/inbox.md). Also use to record a decision or remember this decision when the call is a lightweight one shipped outside a spec slice: UI strings, visual and CSS choices, copy, or translation fixes. Those go to docs/decisions/lightweight-decisions.md via decisions.py. Also use when revising, updating, or re-pricing an already-recorded decision: judge whether it now warrants an ADR and promote it if so, rather than editing it in place. Also auto-fires at session end. Do not use for updating specs or code comments. For a NEW load-bearing decision, one with rejected alternatives, or any the user wants written up as an ADR, use `/jig:adr-workflow`; an already-recorded entry that outgrew this home is promoted from here.

  • Migrate

    ramboz/jig/hosts/claude/skills/migrate Skill

    5★ repo

    Inventory an existing spec-driven project and apply bounded migrations to jig defaults: `report`, `adopt-layout`, `rename-decisions`, `split-slices`, slice-to-spec, `seed-decisions`, and `copy-machinery`. Use when the user says migrate this project to jig, adopt jig here, this repo already has specs — set up jig, scaffold-init refused — what now; introduce jig to an existing codebase; apply ADR-0004 to my project; migrate flat slices into nested specs; seed the lightweight-decisions home; or copy jig's machinery into my project. Reports are read-only; mutations support dry runs where available, refuse conflicts before writing, and preserve originals in the agentic slice-to-spec workflow.

  • Tdd loop

    ramboz/jig/hosts/claude/skills/tdd-loop Skill

    5★ repo

    Drive the red-green-refactor loop for any non-trivial code change. Auto-detect the project's test runner (pytest / vitest / jest / node --test), invoke it via the `tdd.py` helper, and act on the normalized exit code. Use when you write a test, TDD this feature, let me test-drive a behaviour, are about to implement [feature], want to run my tests, ask is my coverage complete, or ask are tests green. Do not use for one-off exploratory scripts, throwaway spikes, or pure-documentation edits that touch no executable code.

  • Vision elicitation

    ramboz/jig/hosts/claude/skills/vision-elicitation Skill

    5★ repo

    Lightweight baseline elicitation pass that fills in `docs/product-vision.md` and the five `docs/architecture.md` elicitation slots after `scaffold-init`. Auto-triggers when you say set up project vision, elicit architecture, define what we're building, run the vision wizard, refresh the project pitch, or capture product scope. Defers to any other installed skill whose description identifies it as handling vision elicitation, product discovery, project framing, or product scope capture — if such a skill is present, prefer it over this one (jig's version is a slim baseline). Does not defer to the generic built-in `init` skill. Do not use for: ad-hoc brainstorming with no `docs/product-vision.md` slot to write into; silently overwriting vision content the user has already hand-edited (the re-run protocol's divergence detection handles that — see the Re-run protocol section below); spec authoring (use `/jig:spec-workflow`); seeding ADRs for already-named decisions (use `/jig:adr-workflow new`).

  • Adr workflow

    ramboz/jig/hosts/codex/plugins/jig/skills/adr-workflow Skill

    5★ repo

    Scaffold, accept, index, and link Architectural Decision Records (ADRs). Use when the user says "write an ADR", "record this decision", "resolve [deferred item] with an ADR", "supersede ADR-NNNN", or otherwise wants to capture a hard-to-reverse decision in `docs/decisions/`. Also use when a refinement-todo entry needs to be marked RESOLVED with a link back to the ADR. Do NOT use for ad-hoc design discussion that hasn't crystallized into a decision yet — wait until the choice is firm.

  • Memory sync

    ramboz/jig/hosts/codex/plugins/jig/skills/memory-sync Skill

    5★ repo

    Persist new context, terms, learnings, and settled lightweight decisions. Use when the user says remember this, save this for later, add to glossary, note this down, or at the end of a session to consolidate what was learned — that goes to the memory layer (AGENTS.md hot cache, docs/memory/, docs/inbox.md). Also use to record a decision, remember this decision, or write this decision down when the call is a lightweight one shipped outside a spec slice: UI strings, visual and CSS choices, sizes, copy, or translation fixes. Those go to docs/decisions/lightweight-decisions.md via decisions.py. Also auto-fires at session end to surface capture-worthy items. Do not use for updating specs or code comments — those have their own workflows. For a load-bearing or architectural decision, one with rejected alternatives worth recording, or any decision the user wants written up as an ADR, use `/jig:adr-workflow` instead.

  • Migrate

    ramboz/jig/hosts/codex/plugins/jig/skills/migrate Skill

    5★ repo

    Inventory an existing spec-driven project and apply bounded migrations to jig defaults: `report`, `adopt-layout`, `rename-decisions`, `split-slices`, slice-to-spec, `seed-decisions`, and `copy-machinery`. Use when the user says migrate this project to jig, adopt jig here, this repo already has specs — set up jig, scaffold-init refused — what now; introduce jig to an existing codebase; apply ADR-0004 to my project; migrate flat slices into nested specs; seed the lightweight-decisions home; or copy jig's machinery into my project. Reports are read-only; mutations support dry runs where available, refuse conflicts before writing, and preserve originals in the agentic slice-to-spec workflow.

  • Tdd loop

    ramboz/jig/hosts/codex/plugins/jig/skills/tdd-loop Skill

    5★ repo

    Drive the red-green-refactor loop for any non-trivial code change. Auto-detect the project's test runner (pytest / vitest / jest / node --test), invoke it via the `tdd.py` helper, and act on the normalized exit code. Use when you write a test, TDD this feature, let me test-drive a behaviour, are about to implement [feature], want to run my tests, ask is my coverage complete, or ask are tests green. Do not use for one-off exploratory scripts, throwaway spikes, or pure-documentation edits that touch no executable code.

  • Vision elicitation

    ramboz/jig/hosts/codex/plugins/jig/skills/vision-elicitation Skill

    5★ repo

    Lightweight baseline elicitation pass that fills in `docs/product-vision.md` and the five `docs/architecture.md` elicitation slots after `scaffold-init`. Auto-triggers when you say set up project vision, elicit architecture, define what we're building, run the vision wizard, refresh the project pitch, or capture product scope. Defers to any other installed skill whose description identifies it as handling vision elicitation, product discovery, project framing, or product scope capture — if such a skill is present, prefer it over this one (jig's version is a slim baseline). Does not defer to the generic built-in `init` skill. Do not use for: ad-hoc brainstorming with no `docs/product-vision.md` slot to write into; silently overwriting vision content the user has already hand-edited (the re-run protocol's divergence detection handles that — see the Re-run protocol section below); spec authoring (use `/jig:spec-workflow`); seeding ADRs for already-named decisions (use `/jig:adr-workflow new`).

  • Adr workflow

    ramboz/jig/skills/adr-workflow Skill

    5★ repo

    Scaffold, accept, index, and link Architectural Decision Records (ADRs). Use when the user says "write an ADR", "record this decision", "resolve [deferred item] with an ADR", "supersede ADR-NNNN", or otherwise wants to capture a hard-to-reverse decision in `docs/decisions/`. Also use when a refinement-todo entry needs to be marked RESOLVED with a link back to the ADR. Do NOT use for ad-hoc design discussion that hasn't crystallized into a decision yet — wait until the choice is firm.

  • Memory sync

    ramboz/jig/skills/memory-sync Skill

    5★ repo

    Persist new context, terms, learnings, and settled lightweight decisions. Use when the user says remember this, save this for later, add to glossary, note this down, or at session end to consolidate what was learned — that goes to the memory layer (CLAUDE.md hot cache, docs/memory/, docs/inbox.md). Also use to record a decision or remember this decision when the call is a lightweight one shipped outside a spec slice: UI strings, visual and CSS choices, copy, or translation fixes. Those go to docs/decisions/lightweight-decisions.md via decisions.py. Also use when revising, updating, or re-pricing an already-recorded decision: judge whether it now warrants an ADR and promote it if so, rather than editing it in place. Also auto-fires at session end. Do not use for updating specs or code comments. For a NEW load-bearing decision, one with rejected alternatives, or any the user wants written up as an ADR, use `/jig:adr-workflow`; an already-recorded entry that outgrew this home is promoted from here.

  • Migrate

    ramboz/jig/skills/migrate Skill

    5★ repo

    Inventory an existing spec-driven project and apply bounded migrations to jig defaults: `report`, `adopt-layout`, `rename-decisions`, `split-slices`, slice-to-spec, `seed-decisions`, and `copy-machinery`. Use when the user says migrate this project to jig, adopt jig here, this repo already has specs — set up jig, scaffold-init refused — what now; introduce jig to an existing codebase; apply ADR-0004 to my project; migrate flat slices into nested specs; seed the lightweight-decisions home; or copy jig's machinery into my project. Reports are read-only; mutations support dry runs where available, refuse conflicts before writing, and preserve originals in the agentic slice-to-spec workflow.

  • Tdd loop

    ramboz/jig/skills/tdd-loop Skill

    5★ repo

    Drive the red-green-refactor loop for any non-trivial code change. Auto-detect the project's test runner (pytest / vitest / jest / node --test), invoke it via the `tdd.py` helper, and act on the normalized exit code. Use when you write a test, TDD this feature, let me test-drive a behaviour, are about to implement [feature], want to run my tests, ask is my coverage complete, or ask are tests green. Do not use for one-off exploratory scripts, throwaway spikes, or pure-documentation edits that touch no executable code.

  • Vision elicitation

    ramboz/jig/skills/vision-elicitation Skill

    5★ repo

    Lightweight baseline elicitation pass that fills in `docs/product-vision.md` and the five `docs/architecture.md` elicitation slots after `scaffold-init`. Auto-triggers when you say set up project vision, elicit architecture, define what we're building, run the vision wizard, refresh the project pitch, or capture product scope. Defers to any other installed skill whose description identifies it as handling vision elicitation, product discovery, project framing, or product scope capture — if such a skill is present, prefer it over this one (jig's version is a slim baseline). Does not defer to the generic built-in `init` skill. Do not use for: ad-hoc brainstorming with no `docs/product-vision.md` slot to write into; silently overwriting vision content the user has already hand-edited (the re-run protocol's divergence detection handles that — see the Re-run protocol section below); spec authoring (use `/jig:spec-workflow`); seeding ADRs for already-named decisions (use `/jig:adr-workflow new`).

  • Pnl translation

    BrennanJCollins/UnabatedPM-coaching/unabatedpm-business-building/skills/pnl-translation Skill

    5★ repo

    Coaches PMs to translate product metrics into P&L (Profit & Loss) language — positioning their product as a profit center rather than a cost center, calculating contribution margin, building ROI-based budget defenses, and speaking the language of CFOs and finance teams.

  • Strategic storytelling pitch

    BrennanJCollins/UnabatedPM-coaching/unabatedpm-influence/skills/strategic-storytelling-pitch Skill

    5★ repo

    Transform competent-but-forgettable pitches into compelling stories that get to 'yes' — using Brennan Collins' 3-Act Structure (Human Stakes → Scale → Solution), stakeholder-specific adaptation via the 'What Would Get Them Fired?' test, and the Bridge Madlib. Catches when PMs lead with logic instead of stakes.

  • Mindstorming

    rohitgehe05/mindpowers/skills/mindstorming Skill

    5★ repo

    Use before drafting any non-code knowledge-work deliverable, including strategic memos, business reviews, OKR defences, PRDs, decision docs, briefing docs, exec talking points, Slack messages to leadership, frameworks, post-mortems, one-pagers, BRDs. Triggers on asks like "help me write up X", "draft this memo", "what should I say to Y", even casually phrased. NOT for software implementation; for creating features, components, or code changes use superpowers:brainstorming instead; for authoring the PRD document itself, use this skill. For non-code deliverables this skill supersedes generic brainstorming. Do not skip for simple asks; simple tasks hide the costliest assumptions.

  • Reviewing docs

    rohitgehe05/mindpowers/skills/reviewing-docs Skill

    5★ repo

    Use when the user has a finished or near-finished document (memo, business review, PRD, decision doc, briefing, comms, framework, talking points, post-mortem) and wants it pressure-tested before it ships, such as "review this doc", "poke holes in this", "is this ready to send". Works on any doc, not just mindpowers-drafted ones. Not for code review.

  • Iso27001

    Jandyoverseas977/Claude-Skills-Governance-Risk-and-Compliance/plugins/iso27001/skills/iso27001 Skill

    5★ repo

    Expert ISO 27001 compliance assistant for security and compliance teams. Use this skill whenever a user asks about ISO 27001 or ISO/IEC 27001, including any of the following: gap analysis, auditing, compliance assessments, control checklists, policy writing, document generation, Statement of Applicability (SoA), risk assessment, risk registers, risk treatment plans, Annex A controls, ISMS implementation, clause requirements, certification readiness, transitioning from 2013 to 2022, control implementation guidance, incident response policies, access control policies, supplier security, or any information security management system (ISMS) topic. Trigger even if the user doesn't say "skill" — any ISO 27001 or ISMS question should use this skill.

  • Soc2

    Jandyoverseas977/Claude-Skills-Governance-Risk-and-Compliance/plugins/soc2/skills/soc2 Skill

    5★ repo

    Expert SOC 2 compliance assistant covering all five Trust Services Criteria (Security/CC, Availability/A, Confidentiality/C, Processing Integrity/PI, Privacy/P). Use this skill whenever a user mentions SOC 2, Trust Services Criteria, SOC 2 Type 1 or Type 2, audit readiness, compliance gaps, control documentation, evidence collection, vendor risk questionnaires, or anything related to AICPA service organization controls. Trigger even for adjacent topics like "we need to get audited", "a customer asked for our security report", "writing an information security policy", or "preparing for an audit". Covers gap analysis, policy writing, control documentation, audit evidence preparation, and vendor risk reviews for organizations at any maturity level — from first-time startups to seasoned compliance teams.

  • Tsa compliance

    Jandyoverseas977/Claude-Skills-Governance-Risk-and-Compliance/plugins/tsa-compliance/skills/tsa-compliance Skill

    5★ repo

    Expert TSA cybersecurity compliance advisor for critical infrastructure owners and operators. Use this skill whenever a user asks about TSA Security Directives for pipelines, freight railroads, passenger rail, public transit, or bus operators; the TSA Cyber Risk Management Program (CRMP); Cybersecurity Implementation Plan (CIP); Cybersecurity Operational Implementation Plan (COIP); Cybersecurity Assessment Plan (CAP); incident reporting to CISA; designation of a Cybersecurity Coordinator; Critical Cyber Systems (CCS); OT/IT network segmentation; the TSA November 2024 NPRM; or any directive in the SD Pipeline-2021 series, SD 1580-21-01 (freight rail), or SD 1582-21-01 (public transit/passenger rail). Also trigger for questions like "are we covered by TSA directives?", "what does the TSA require for pipeline cybersecurity?", "how do I build a CIP?", "what must I report to CISA?", or any request involving transportation critical infrastructure cybersecurity compliance.

  • Hyper docs loop

    zeikar/hyperclaude/skills/hyper-docs-loop Skill

    5★ repo

    Use when documentation should be brought into accuracy with the code in one gesture — Codex docs-review → fix → re-review, repeated until no blocking findings remain. Also when the user invokes /hyperclaude:hyper-docs-loop. For manual round-by-round control use /hyperclaude:hyper-docs-review + manual edits instead.

  • Hyper docs review

    zeikar/hyperclaude/skills/hyper-docs-review Skill

    5★ repo

    Use after documentation edits — typically after the documenter agent runs, or when the user invokes /hyperclaude:hyper-docs-review. Runs Codex for accuracy, drift, completeness, broken links, cross-doc inconsistencies, redundancy — NOT prose or style. Distinct from /hyperclaude:hyper-code-review (code diffs) and /hyperclaude:hyper-plan-review (plans).

  • Hyper docs sync

    zeikar/hyperclaude/skills/hyper-docs-sync Skill

    5★ repo

    Use after implementation changes documented API, schemas, CLI flags, or architecture — before docs go stale. Also when the user invokes /hyperclaude:hyper-docs-sync. Syncs docs to the current code state.

  • Hyper tdd

    zeikar/hyperclaude/skills/hyper-tdd Skill

    5★ repo

    Use when about to write or modify behavior-bearing code — functions, business logic, bug fixes — before writing any production code. Also when the user invokes /hyperclaude:hyper-tdd. Forces a failing test first so you watch it fail for the right reason.

  • Helm

    air-gapped/skills/.claude/skills/helm Skill

    5★ repo

    This skill should be used when authoring or maintaining Helm charts — creating charts, writing templates and _helpers.tpl, values.yaml patterns, Chart.yaml, values.schema.json, helm-docs, and library charts. Covers Helm 4 (SSA, WASM, OCI digest), chart CI/CD, OpenShift compatibility, chart security, CRD management, and production templates. NOT for installing or consuming third-party charts.

  • Jira cli

    air-gapped/skills/.claude/skills/jira-cli Skill

    5★ repo

    Drive Atlassian Jira from the terminal with the `jira` CLI (jira-cli, v1.7.0) against ANY Jira — Cloud or on-premise/Data Center. Covers the full command surface (issue / epic / sprint / board / project / release), the non-interactive automation contract (`--no-input` + `--plain`/`--raw`/`--csv` for agent-safe, parseable output), JQL filtering, GitHub/Jira markdown → Atlassian Document Format (ADF) conversion, authentication for every backend (Cloud API token, on-prem basic, PAT/bearer, mTLS), and live-discovery of instance-specific values (project keys, issue types, statuses, priorities, link types, custom fields) instead of guessing them.

  • Kelly writer

    mr-kelly/skills/skills/kelly-writer Skill

    5★ repo

    Repurpose source content into channel-ready drafts with a local review UI and approval/export workflow. Use when the user asks to write content, make a content pack, turn a main blog/long article/transcript/notes into Xiaohongshu, WeChat, newsletter, LinkedIn, X/Twitter, short video scripts, SEO snippets, or a multi-platform publishing plan; also use when they ask for a content approval dashboard or App-in-Skill content workflow.

  • Executive storytelling

    fabioc-aloha/Alex_Skill_Mall/plugins/communication-people/executive-storytelling Skill

    5★ repo

    Data-driven narrative construction, stakeholder management, and influencing senior leadership decisions

  • Status reporting

    fabioc-aloha/Alex_Skill_Mall/plugins/communication-people/status-reporting Skill

    5★ repo

    Create stakeholder-friendly project status updates and progress reports

  • Docpilot

    fabioc-aloha/Alex_Skill_Mall/plugins/converters/docpilot Skill

    5★ repo

    Convert a Markdown file to a styled Word (.docx) document using docpilot — syntax-highlighted code blocks, blue-header tables, no Pandoc required.

  • Data storytelling

    fabioc-aloha/Alex_Skill_Mall/plugins/data-analytics/data-storytelling Skill

    5★ repo

    End-to-end data narrative construction -- three-act structure, Knaflic/Duarte methodology, audience-first framing, and orchestration across analysis, visualization, and dashboard skills

  • Chart big idea

    fabioc-aloha/Alex_Skill_Mall/plugins/data-analytics/flint-chart-plugin/skills/chart-big-idea Skill

    5★ repo

    Distill the one-sentence Big Idea, story arc, audience, and style stance for a chart BEFORE picking a chart type. Starts by questioning intent — whether the artifact should exist at all, and whether the stated purpose is the real one. Reads the surrounding docs / prose / ticket for an existing Big Idea first, then helps the user articulate one via a 3-question elicitation ladder if none is found. Asks whether the user wants a TRADITIONAL (safe) or INNOVATIVE (higher-impact, higher-risk) treatment. Use before invoking the flint-chart skill or the /render-chart prompt whenever the user's ask is 'chart this', 'visualize', 'make a chart', 'show the data', or when framing is unclear.

  • Storytelling requirements

    fabioc-aloha/Alex_Skill_Mall/plugins/data-analytics/storytelling-requirements Skill

    5★ repo

    Guided requirements template for data storytelling projects -- walks users through audience, Big Idea, questions, data sources, and delivery target before any chart is created

  • Visual storytelling

    fabioc-aloha/Alex_Skill_Mall/plugins/data-analytics/visual-storytelling Skill

    5★ repo

    Bundle plugin: installs the complete Visual Storytelling pipeline (brief, ingest, clean, select, deliver). See component SKILLs for detailed specs.

  • Creative writing

    fabioc-aloha/Alex_Skill_Mall/plugins/devops-process/creative-writing Skill

    5★ repo

    Patterns for fiction, narrative structure, character development, dialogue, and storytelling craft.

  • Github readme override

    fabioc-aloha/Alex_Skill_Mall/plugins/devops-process/github-readme-override Skill

    5★ repo

    GitHub README display rules — which README renders when multiple exist, profile READMEs, org READMEs

  • Release notes

    fabioc-aloha/Alex_Skill_Mall/plugins/devops-process/release-notes Skill

    5★ repo

    284 curated plugins for AI assistants across 16 categories: security, Azure, documentation, code quality, cloud infrastructure, and more. Works with GitHub Copilot. Drop into .github/skills/local/ and go.

  • Ai writing avoidance

    fabioc-aloha/Alex_Skill_Mall/plugins/documentation/ai-writing-avoidance Skill

    5★ repo

    Help writers produce content that sounds genuinely human by avoiding telltale AI-generated text patterns

  • Api documentation

    fabioc-aloha/Alex_Skill_Mall/plugins/documentation/api-documentation Skill

    5★ repo

    Technical documentation, API references, user guides, and docs-as-code workflows.

  • Doc coauthoring

    fabioc-aloha/Alex_Skill_Mall/plugins/documentation/doc-coauthoring Skill

    5★ repo

    Structured workflow for co-authoring technical documentation. Use when asked to "write documentation", "create a spec", "draft a proposal", "write a design doc", "create an RFC", "document this feature", or "write technical docs". Three stages: context gathering, iterative refinement, and reader testing.

  • Doc hygiene

    fabioc-aloha/Alex_Skill_Mall/plugins/documentation/doc-hygiene Skill

    5★ repo

    Documentation hygiene — anti-drift rules, count elimination, and living document maintenance

  • Docs decay velocity

    fabioc-aloha/Alex_Skill_Mall/plugins/documentation/docs-decay-velocity Skill

    5★ repo

    Documentation decay rates by content type — hardcoded numbers and version pins rot fastest

  • Documentation quality assurance

    fabioc-aloha/Alex_Skill_Mall/plugins/documentation/documentation-quality-assurance Skill

    5★ repo

    Systematic documentation audit, drift detection, preflight validation, and multi-pass quality pipelines

  • Dual surface docs drift

    fabioc-aloha/Alex_Skill_Mall/plugins/documentation/dual-surface-docs-drift Skill

    5★ repo

    Two READMEs covering overlapping scope will diverge:

  • Lint clean markdown

    fabioc-aloha/Alex_Skill_Mall/plugins/documentation/lint-clean-markdown Skill

    5★ repo

    Write markdown that passes linting on first attempt by internalizing common rules.

  • Markdown mermaid

    fabioc-aloha/Alex_Skill_Mall/plugins/documentation/markdown-mermaid Skill

    5★ repo

    Clear documentation through visual excellence

  • Wiki generation

    fabioc-aloha/Alex_Skill_Mall/plugins/documentation/wiki-generation Skill

    5★ repo

    Generate structured documentation from codebases — architecture mapping, page writing, and onboarding guides. Use when asked to create a wiki, document a repo, generate onboarding docs, map architecture for documentation, or produce a documentation plan from source code.

  • Comedy writing

    fabioc-aloha/Alex_Skill_Mall/plugins/domain-expertise/comedy-writing Skill

    5★ repo

    Joke structure, comedic timing, set construction, callback patterns, and audience engagement for comedy writers.