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

  • Doc generator

    spideynolove/claude-code-in-action/00-materials/claude-howto/03-skills/doc-generator Skill

    2★ repo

    Generate comprehensive, accurate API documentation from source code. Use when creating or updating API documentation, generating OpenAPI specs, or when users mention API docs, endpoints, or documentation.

  • Selection report

    jperrello/C0BALT_CUT/.claude/skills/selection-report Skill

    no license2★ repo

    Write output/<slug>/_selection.json for a source — the shipped shorts (scores + rationale from segments.raw.json, linked to their delivered filename) ALONGSIDE the considered-not-shipped RLM candidate menu (candidates.hint.json, each marked picked/unused) and the topic list (topics.json). Deterministic, no Claude, idempotent, non-fatal. Runs once at end of run AND standalone over the whole output/ backlog. Answers "show me the other arguments alongside the shorts".

  • Article writing

    multiplex-ai/muggle-ai-teams/skills/article-writing Skill

    2★ repo

    Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.

    The same file is in 7 other repositories

  • Content strategy

    multiplex-ai/muggle-ai-teams/skills/content-strategy Skill

    2★ repo

    When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use 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 content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social-content.

    The same file is in 2 other repositories

  • Copywriting

    multiplex-ai/muggle-ai-teams/skills/copywriting Skill

    2★ repo

    When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see email-sequence. For popup copy, see popup-cro. For editing existing copy, see copy-editing.

    The same file is in 5 other repositories

  • Documentation lookup

    multiplex-ai/muggle-ai-teams/skills/documentation-lookup Skill

    2★ repo

    Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma).

    The same file is in 4 other repositories

  • Geo compare

    multiplex-ai/muggle-ai-teams/skills/geo-compare Skill

    2★ repo

    Monthly delta tracking and progress reporting for GEO clients. Compares two GEO audits (baseline vs. current), calculates score improvements across all categories, tracks action item completion, and generates a "here's your progress" client report. Use when user says "compare", "delta", "monthly report", "progress", "confronta", "progressi", "report mensile", or when running a monthly client check-in.

    The same file is in 15 other repositories

  • Geo report pdf

    multiplex-ai/muggle-ai-teams/skills/geo-report-pdf Skill

    2★ repo

    Generate a professional PDF report from GEO audit data using ReportLab. Creates a polished, client-ready PDF with score gauges, bar charts, platform readiness visualizations, color-coded tables, and prioritized action plans.

    The same file is in 9 other repositories

  • Geo report

    multiplex-ai/muggle-ai-teams/skills/geo-report Skill

    2★ repo

    Generate a professional, client-facing GEO report combining all audit results into a single deliverable with scores, findings, and prioritized actions

    The same file is in 9 other repositories

  • Nutrient document processing

    multiplex-ai/muggle-ai-teams/skills/nutrient-document-processing Skill

    2★ repo

    Process, convert, OCR, extract, redact, sign, and fill documents using the Nutrient DWS API. Works with PDFs, DOCX, XLSX, PPTX, HTML, and images.

  • Sales enablement

    multiplex-ai/muggle-ai-teams/skills/sales-enablement Skill

    2★ repo

    When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitor-alternatives. For marketing website copy, see copywriting. For cold outreach emails, see cold-email.

    The same file is in 3 other repositories

  • Visa doc translate

    multiplex-ai/muggle-ai-teams/skills/visa-doc-translate Skill

    2★ repo

    Translate visa application documents (images) to English and create a bilingual PDF with original and translation

    The same file is in 8 other repositories

  • Ss proposal

    lbk-open/super-spec/skills/ss-proposal Skill

    2★ repo

    Use when you have a PRD or requirement description and need a complete technical proposal before writing any code. Filters the requirement down to this repository's boundary, analyzes the existing architecture and conventions, and produces a Markdown proposal covering architecture, data flow, key interfaces, alternatives, risks, and milestones — gated by a self-review and, when available, an independent reviewer pass.

  • Ss write spec

    lbk-open/super-spec/skills/ss-write-spec Skill

    2★ repo

    Generates or updates OpenSpec delta specs under openspec/changes/<change-id>/ from a proposal, PRD, or plain-language requirement, bootstrapping the openspec/ skeleton first if the project doesn't have one yet. Use this to align capability specs with reviewers before writing a full execution plan, or to adjust deltas without regenerating the plan.

  • Devrites prose craft

    ViktorsBaikers/DevRites/pack/.claude/skills/devrites-prose-craft Skill

    no license2★ repo

    Humanize prose without losing technical content. Use when asked to remove AI-writing tells, match a writing sample or project voice, edit artifacts/replies/commit or PR prose, or run `/rite-polish`'s prose pass. Not for code comments or UI craft.

  • Rite handoff

    ViktorsBaikers/DevRites/pack/.claude/skills/rite-handoff Skill

    no license2★ repo

    User-invoked handoff writer: sync chat-only context into `.devrites/` and write a fresh-agent handoff.

  • Devrites prose craft

    ViktorsBaikers/DevRites/pack/generated/claude/skills/devrites-prose-craft Skill

    no license2★ repo

    Humanize prose without losing technical content. Use when asked to remove AI-writing tells, match a writing sample or project voice, edit artifacts/replies/commit or PR prose, or run `/rite-polish`'s prose pass. Not for code comments or UI craft.

  • Rite handoff

    ViktorsBaikers/DevRites/pack/generated/claude/skills/rite-handoff Skill

    no license2★ repo

    User-invoked handoff writer: sync chat-only context into `.devrites/` and write a fresh-agent handoff.

  • Devrites prose craft

    ViktorsBaikers/DevRites/pack/generated/codex/skills/devrites-prose-craft Skill

    no license2★ repo

    Internal DevRites skill; DevRites agents invoke it explicitly, not by prompt match.

  • Rite handoff

    ViktorsBaikers/DevRites/pack/generated/codex/skills/rite-handoff Skill

    no license2★ repo

    User-invoked handoff writer: sync chat-only context into `.devrites/` and write a fresh-agent handoff.

  • Xiaohongshu to markdown

    kohoj/skills/xiaohongshu-to-markdown Skill

    2★ repo

    Xiaohongshu Article to Markdown — Extracts text from Xiaohongshu image-based posts via OCR. Use when the user needs to convert a Xiaohongshu/Little Red Book post into readable Markdown text. The tool downloads all carousel images from a post and uses macOS Vision OCR to extract the text content. Requires a Chromium browser logged into xiaohongshu.com with CDP enabled. macOS only (uses Vision Framework for OCR).

  • Instance generation and benchmarks

    hajibabaie/combinatorial-optimization-skills/skills/instance-generation-and-benchmarks Skill

    2★ repo

    When the user wants to assemble instances for optimization experiments by parsing standard benchmarks (TSPLIB, CVRPLIB/Solomon, OR-Library, MIPLIB, QAPLIB, Taillard), writing seeded generators with controlled hardness, reporting instance features, or building train/test splits for tuning. Also use when the user mentions "benchmark instances," "TSPLIB," "Solomon instances," "OR-Library," "instance generator," "test instances," or when a study needs a defensible test bed. For statistical comparison, see algorithm-benchmarking-statistics; for feasibility checking, see solution-validation-testing.

  • Fixing doc drift

    aj604/toolshed/plugins/doc-lifecycle/skills/fixing-doc-drift Skill

    2★ repo

    Use when applying a drift report (detecting-doc-drift output) to the docs — syncing documentation to code after drift is found, landing fixes from a structured STALE/VERIFIED/UNVERIFIABLE record set, or whenever tempted to "clean up", reword, or delete doc passages the report did not flag.

  • Growing docs

    aj604/toolshed/plugins/doc-lifecycle/skills/growing-docs Skill

    2★ repo

    Use when a repo already has baseline docs but a demand signal says they are no longer enough — the same question answered twice, a fact re-derived the hard way across sessions, an incident with no runbook, onboarding pain, a recurring "why is it like this?", someone asking "should we document X?", or a docs/doc-scope.md item whose promotion signal has fired — and for any direct ask to write a narrative doc: an ADR, tutorial, walkthrough, or architecture overview (writing-docs scopes those out by design; their REQUIRED template lives here). The demand-driven counterpart to bootstrapping-docs, which creates the minimum for a repo with no docs.

  • Scheduling doc sync

    aj604/toolshed/plugins/doc-lifecycle/skills/scheduling-doc-sync Skill

    2★ repo

    Use when wiring a repo for automated/unattended documentation audit — "set up doc sync", "automate drift detection", "schedule nightly doc checks", "keep docs in sync automatically" — installs the doc-lifecycle GitHub Actions (scheduled read-only drift and bloat audits, an optional policy apply lane, a manual apply dispatch, and a weekly upgrade check) instead of hand-rolling workflow YAML. Also the door for upgrading an existing install.

  • Writing docs

    aj604/toolshed/plugins/doc-lifecycle/skills/writing-docs Skill

    2★ repo

    Use when writing or editing a documentation file whose job is to track the repo — README, runbook, CLAUDE.md/AGENTS.md, reference (including the claim-style docs/reference/architecture.md that bootstrapping-docs prescribes), or agent-facing context pack — including converting human or marketing docs into dense agent-facing form, or when tempted to add example output, install steps, or "why" prose. The one door for these repo-tracking docs, across human and agent readers (token bloat, context rot). Out of scope: tutorials, narrative architecture/conceptual overviews and design rationale, and decision records (ADRs) — narrative by design, not line-by-line claims about the repo (growing-docs creates those when demand justifies it). To create a baseline doc set from scratch for an undocumented repo, start with bootstrapping-docs; it routes here for each doc.

  • Spec writer

    jaydenluckertjes-ai/Carmack-Council/skills/spec-writer Skill

    2★ repo

    Generate structured software specifications for features, bug fixes, and products. Use when the user wants to create a spec, PRD, feature brief, requirements document, or when starting any new implementation that needs a specification first. Invoke via /spec-writer or when the user says "write a spec", "spec this out", "create a spec", "I need a spec for...", or describes a feature they want to build. Produces adaptive-complexity specs with Job Stories, Gherkin acceptance criteria, and three-tier boundaries. Output is a markdown file ready for agent execution or human review.

    The same file is in 1 other repository

  • Pathology compliance checker

    patolojiAI/pathology-skills-collection/pathology-skills/pathology-compliance-checker Skill

    no license2★ repo

    Validates surgical pathology cancer reports against CAP (College of American Pathologists) and ICCR (International Collaboration on Cancer Reporting) guidelines with severity-based compliance scoring (0-100) and automatic pT/pN/margin cross-validation. Use whenever the user pastes or uploads a pathology report (.pdf, .docx, .txt) and asks to "check compliance", "validate against CAP", "score this report", "audit this synoptic", "find missing elements", or "verify pT/pN consistency". Supports breast, colorectal, pancreas, and gastric carcinoma in English and Turkish.

  • Pathology report checker

    patolojiAI/pathology-skills-collection/pathology-skills/pathology-report-checker Skill

    no license2★ repo

    Analyzes surgical pathology cancer reports for compliance with CAP (College of American Pathologists) and ICCR (International Collaboration on Cancer Reporting) guidelines. Validates pTNM staging (AJCC 8th edition), checks required element completeness with severity-based scoring, generates blank or pre-filled CAP synoptic templates, creates 3-5 line tumor board summaries, suggests SNOMED CT and ICD-O-3 codes, converts free-text narratives to structured synoptic format, and drafts amendments/addenda. Use when the user pastes or uploads a pathology report (txt, pdf, docx, image, xlsx) and asks to "check CAP compliance", "verify staging", "generate synoptic template", "tumor board summary", "convert to synoptic", "calculate TNM stage", or "code with SNOMED" for breast invasive carcinoma, colorectal resection, exocrine pancreas carcinoma, or gastric carcinoma. Supports English and Turkish. Do NOT use for non-cancer pathology (inflammatory, infectious), cytology, or unsupported tumor types.

  • Reference verifier

    patolojiAI/pathology-skills-collection/pathology-skills/reference-verifier Skill

    no license2★ repo

    Comprehensive academic reference auditor that performs four levels of verification on citations in uploaded manuscripts (.pdf, .docx). Level 1 checks if references actually exist. Level 2 verifies metadata accuracy (authors, year, journal, volume, pages). Level 3 checks whether the cited paper actually covers the topic it is cited for. Level 4 analyzes whether each citation is used correctly in context — confirming if the cited source truly supports, contradicts, or is neutral toward the claim being made. Saves a BibTeX file (.bib) and a markdown audit report (HTML optional) in the current working directory. Use whenever the user uploads a manuscript and asks to check, verify, validate, or audit references, citations, or bibliography, generate a .bib file, detect fake or hallucinated references, check citation accuracy, verify citation context, or audit a reference list. Especially tuned for biomedical/PubMed-indexed literature but works for any discipline.

  • Report converter

    patolojiAI/pathology-skills-collection/pathology-skills/report-converter Skill

    no license2★ repo

    Converts free-text narrative pathology reports into structured CAP synoptic format and generates amendments/addenda/corrections for previously-issued reports. Use when the user uploads or pastes a narrative pathology report (.pdf, .docx, .txt) and asks to "convert to synoptic", "convert to CAP format", "structure this report", "make this synoptic", "generate an amendment", "add an addendum", or "issue a corrected report". Extracts diagnostic elements (tumor type, grade, size, stage, margins, nodes, biomarkers) and maps them to CAP data elements.

  • Scientific similarity checker

    patolojiAI/pathology-skills-collection/pathology-skills/scientific-similarity-checker Skill

    no license2★ repo

    Analyze a scientific article (.pdf, .docx, image, or text) to find similar work across PubMed, OpenAlex, Semantic Scholar, IEEE, arXiv, Crossref, and the web. Detects similarity by abstract content, topic, authors, and journal. Issues tiered warnings (red/amber/green) when similarity levels suggest self-plagiarism, duplicate publication, salami slicing, or research misconduct. Saves a structured report as markdown (and optionally HTML) in the current working directory. Use whenever a user uploads or pastes a scientific article, manuscript, preprint, or abstract and asks to "check this paper", "find similar studies", "is this published elsewhere", "duplicate publication check", "misconduct screening", "novelty check", "plagiarism screen", or "find the authors' other work" — including when academic integrity checking is implied.

  • Statistical methods reviewer

    patolojiAI/pathology-skills-collection/pathology-skills/statistical-methods-reviewer Skill

    no license2★ repo

    Critically review the statistical methods used in a research article (.pdf, .docx, .pptx, .html, .txt). Extract every test and model the authors used, judge whether each is appropriate for the study design and data, and evaluate assumption checks, multiplicity control, sample-size justification, effect-size reporting, model specification, missing-data handling, validation/calibration, and reproducibility. Produces a scored rubric (0-2 across 9 aspects, total 0-18), a red-flag list, and concrete recommendations for better statistical tests where appropriate. Saves the review as a markdown file (and optionally HTML) in the current working directory. Use when the user supplies a research article and asks to "review the stats", "check the statistical methods", "audit the analysis", "are these tests correct", "score this paper's statistics", or any variant of statistical critique.

  • Locking

    matejformanek/postgres-claude/.claude/skills/locking Skill

    2★ repo

    Pick a PostgreSQL backend lock primitive (atomic / spinlock / LWLock / heavyweight / predicate / buffer-pin-content) or debug a lock-ordering bug, silent LWLock hang, deadlock-detector report, or a multixact / tuple-lock interaction — the six-layer PG lock taxonomy in operational form. Covers `pg_atomic_u32 / u64` ordering + memory barriers, `SpinLockAcquire / SpinLockRelease` (with the "no calls / no ereport / no CHECK_FOR_INTERRUPTS" rules), `LWLockAcquire LW_SHARED / LW_EXCLUSIVE` and tranches (lwlocklist.h + wait_event_names.txt), heavyweight `LockAcquire` / `LockRelationOid` / `LOCKTAG_*`, predicate (SSI) locks, buffer pin / content locks, the `BufferMapping / LockManager / PredicateLockManager` partition rank rules, multi-XID `HEAP_XMAX_IS_MULTI` interaction with `FOR UPDATE / FOR KEY SHARE`, parallel-worker lock-group semantics, and the lldb-attach recipe for silent-LWLock-deadlock diagnosis. **Use this skill proactively whenever the user is writing or reviewing C in `src/backend` or `dev/src/backend` that touches shared memory (MainLWLockArray, PGPROC, ProcArray, BufferDesc, SLRU, any `*Shmem*` allocation), adds a new LWLock tranche (RequestNamedLWLockTranche / LWLockNewTrancheId / PG_LWLOCK / PG_LWLOCKTRANCHE), picks between spinlock / LWLock / atomic / heavyweight for new shmem state, asks about LWLock partition rank order, debugs an LWLock hang where `pg_stat_activity` shows `wait_event_type='LWLock'` but no `deadlock detected` ever fires, hits an assertion like `IsRelationExtensionLockHeld`, gets bitten by `HEAP_XMAX_IS_MULTI` and GetMultiXactIdMembers, asks about parallel-worker lock-group conflicts, or reviews a patch that adds shmem state / new wait events — even when the user doesn't use the literal word "lock".** Skip for pthread_mutex_t / std::mutex / Java synchronized / ReentrantLock / Go sync.Mutex / Rust std::sync::Mutex / parking_lot / tokio::sync::Mutex / C# lock(obj) / Monitor.Enter, Redis pessimistic / Redlock / ZooKeeper / etcd / Chubby distributed locks, ORM optimistic locking (version int column), user-level / application-side `SELECT FOR UPDATE` design questions (how to model inventory claim), application-level lock-manager design (key→holder hash with TTLs), and general "what's the right lock primitive" non-PG advice.

  • Patch submission

    matejformanek/postgres-claude/.claude/skills/patch-submission Skill

    2★ repo

    Prepare a PostgreSQL change for upstream submission to pgsql-hackers — covers git format-patch of the series, writing the cover letter, registering a CommitFest (CF) entry, running pgindent / check-world / docs build, and staging the v1 patchset for mailing. Thin wrapper: review machinery lives in pg-patch-review (--self mode) and the commit-message format in commit-message-style. Use whenever a PG patch is being prepared to go upstream — running pgindent before format-patch, writing the cover letter, registering or updating a CF entry, staging v(N+1) re-submission after a review cycle, or running the pre-submission gate (check-world + docs build + pgindent). Skip for GitHub PR creation / `gh pr create` on app repos, NPM publish / crate publish / PyPI / RubyGems release flows, LKML / Linux-kernel patch submission, Apache committer paperwork, generic "how do I contribute to open source" questions, and Gerrit / Phabricator workflows.

  • Review checklist

    matejformanek/postgres-claude/.claude/skills/review-checklist Skill

    2★ repo

    Review a PostgreSQL patch using the wiki's seven-phase checklist — covers Phase 0 reviewer-reflex gates + REJECT-A/B/C grade rubric for design rejections, plus the wiki's Phases 1-7 (apply/build, regress + check-world, pgindent, design fit, docs, comments, committer-readiness). Applies to reviewing someone else's pgsql-hackers / CommitFest submission OR self-reviewing your own patch before mailing it. Use whenever the user says "review this patch", "is it ready to send to hackers", "CF entry NNNN review", "pre-submission review", "REJECT this patch", or pastes a pgsql-hackers thread asking for a structured review. Skip for generic GitHub PR code review (app code), Terraform / Helm chart review, Python / Ruby / Rust / Go application code review, security audit (use security-review), API design review on REST / GraphQL endpoints, and documentation-only review for non-PG projects.

  • Wal and xlog

    matejformanek/postgres-claude/.claude/skills/wal-and-xlog Skill

    2★ repo

    Add or modify a PostgreSQL WAL / XLOG record — covers choosing built-in rmgr vs Generic WAL (generic_xlog.c) vs custom rmgr (RegisterCustomRmgr), the XLogInsert + XLogRegisterBuffer idiom, writing a correct redo function, FPI / hint-bit (MarkBufferDirtyHint) rules, full-page-write handling, updating rmgrdesc + pg_waldump output, and bumping XLOG_PAGE_MAGIC when format changes. Use whenever a PG patch emits XLogInsert, adds an access method that needs durability, writes or modifies a redo function, registers a custom rmgr via RegisterCustomRmgr, or reviews a patch that changes WAL-record formats. Skip for MySQL binlog / GTID / row-based logging, SQLite WAL journal mode, Kafka log compaction / segment retention, pgbackrest / barman / wal-g operational config, recovery.conf / standby.signal DBA-side configuration, and generic write-ahead-logging theory or ARIES algorithm questions.

  • Jerusalem municipality report

    danielrosehill/Claude-Israel-Agent-Skills-Plugin/skills/jerusalem-municipality-report Skill

    2★ repo

    Use when the user wants to file a "106" public-contact report with the Jerusalem Municipality (עיריית ירושלים, pniya la-106). Opens the official form at https://www.jerusalem.muni.il/he/contactus/106/ via Playwright, fills the applicant, contact, address, and description fields from user-supplied data, pauses for the user to solve the reCAPTCHA, then submits. Trigger phrases: "open a Jerusalem municipality report", "file a 106", "report something to iriya", "pniya la-iriya", "report a pothole / graffiti / broken streetlight to Jerusalem".

  • Update plugin readme

    danielrosehill/Claude-Israel-Agent-Skills-Plugin/skills/update-plugin-readme Skill

    2★ repo

    Use when the user wants to refresh the README of this plugin (or any Claude Code skills plugin) so that its "Skills" section reflects the current set of skills under `skills/*/SKILL.md`. Reads each skill's frontmatter (`name`, `description`, optional `category`), groups by category, sorts alphabetically within each group, and rewrites the README's Skills section between the `<!-- SKILLS:START -->` and `<!-- SKILLS:END -->` markers. Preserves everything else in the README (header, installation, license). A helper script at `scripts/generate-skills-section.py` does the extraction and emits the block on stdout; the skill is responsible for splicing it into the README. Trigger phrases - "update the plugin README", "regenerate the skills table", "refresh skills list on the plugin README", "the plugin README is out of date", "add the new skill to the README".

  • Logo brief writer

    SkillMedev/brand-visual-identity/skills/logo-brief-writer Skill

    2★ repo

    Writes a complete creative brief for a logo or identity project - business context, a three-adjective personality axis, deliverables and constraints, competitive territory, rounds and timeline, and concrete success criteria. Use when someone asks "write a logo brief", "brief a designer for our rebrand", "what do I send the identity studio", or is kicking off a brand identity engagement. Do NOT use for generating the brand name itself - use brand-naming instead; for documenting the finished identity system's usage rules, use brand-guidelines; for briefing broader creative direction, use moodboard-builder.

    The same file is in 1 other repository

  • Resume content writer

    ebarti/skills/resume-content-writer Skill

    2★ repo

    Generates tailored, schema-conformant resume content — headline, branding summary, JD-matched skills section, and quantified achievement bullets — tuned to a target role, seniority, and focus, while honoring user-pinned "must-include" achievements. Distilled from "Resumes For Dummies" (AI-era ed.). Built for automated pipelines (e.g. JobHunter): consumes a TargetProfile and emits structured resume data. Use this skill when: - Tailoring a resume's content to a specific job description - Rewriting experience into quantified, action-verb-led achievement bullets - Writing a targeted headline / branding summary (replacing weak objectives) - Selecting and ordering a skills section to match a JD - Framing content by seniority (new-grad/thin experience vs senior/experienced) - Revising resume content from a scorer's prioritized fixes - Producing resume content that must conform to a caller-supplied JSON schema

  • Data extract

    moonlight-lupin/data-toolkit/skills/data-extract Skill

    2★ repo

    Data prep toolkit for finance & ops: extract, tidy, reconcile, analyse, visualise — powered by deterministic engines for consistent and accurate outputs. From Phronesis Applied.

  • Data tidy

    moonlight-lupin/data-toolkit/skills/data-tidy Skill

    2★ repo

    Data prep toolkit for finance & ops: extract, tidy, reconcile, analyse, visualise — powered by deterministic engines for consistent and accurate outputs. From Phronesis Applied.

  • My ios app store changelog

    qteqpid/ios-app-development/skills/my-ios-app-store-changelog Skill

    no license2★ repo

    Create user-facing iOS App Store release notes by collecting and summarizing user-impacting changes since the last git tag or a specified ref. Use when asked to generate App Store "What's New" text, release notes, TestFlight notes, or a user-facing changelog for an iOS app based on git history.

  • Domainkit

    mimukit/skills/skills/domainkit Skill

    2★ repo

    My personal collection of AI agent skills; the *kit family. Portable, one install away.

  • Handoffkit

    mimukit/skills/skills/handoffkit Skill

    2★ repo

    My personal collection of AI agent skills; the *kit family. Portable, one install away.

  • Humankit

    mimukit/skills/skills/humankit Skill

    2★ repo

    My personal collection of AI agent skills; the *kit family. Portable, one install away.

    The same file is in 1 other repository

  • Plankit

    mimukit/skills/skills/plankit Skill

    2★ repo

    My personal collection of AI agent skills; the *kit family. Portable, one install away.

  • Qakit

    mimukit/skills/skills/qakit Skill

    2★ repo

    My personal collection of AI agent skills; the *kit family. Portable, one install away.

  • Humanizer

    7ucg/baron-forge/plugins/baron-forge/skills/humanizer Skill

    2★ repo

    Remove AI-writing tells from text. Use when editing/reviewing prose to sound human — fixes em-dash overuse, rule-of-three, inflated/promotional vocab, vague attributions, negative parallelisms, conjunctive filler. Based on Wikipedia's "Signs of AI writing". Credits: @blader - github.com/blader/humanizer

  • Gt google ads

    Growth-Today/claude-skills/gt-google-ads Skill

    2★ repo

    GT Google Ads — expert Google Ads strategist for B2B companies, built by Growth Today (growthtoday.co). Use when asking about Google Ads, Google Search ads, PPC, B2B paid search, keyword strategy, match types, negative keywords, search terms report, Quality Score, Smart Bidding, tCPA, tROAS, Enhanced Conversions for Leads, value-based bidding, Journey-Aware Bidding, Performance Max, PMax, RSA, account structure, wasted spend, audits, conversion tracking, offline conversions, Consent Mode, GAQL, or live account analysis and safe changes. Triggers on: Google Ads, paid search, negative keywords, search terms, Quality Score, Smart Bidding, Journey-Aware Bidding, Performance Max, RSA, wasted spend audit, conversion tracking, offline conversions, Consent Mode, GAQL, MCP, live data, forecast, safe write. Do NOT use for LinkedIn Ads (use gt-linkedin-ads), Meta/Facebook Ads (use gt-meta-ads), SEO, or organic content. More GT skills: growthtoday.co.

  • Gt gtm strategy advisor

    Growth-Today/claude-skills/gt-gtm-strategy-advisor Skill

    2★ repo

    GTM Strategy Advisor by Growth Today (growthtoday.co) — turns your own CRM data, sales deck, website, and call recordings into a signal-based GTM playbook. Use when a VP of Sales, Head of Growth, RevOps lead, CRO, or founder wants to build, audit, or sharpen their go-to-market motion: define a data-backed ICP, map the buyer journey, document pain per persona, build a buying-signal library, write a competitor battlecard, and generate a messaging matrix. Connect your HubSpot or Salesforce or upload your materials; it outputs a ready-to-use Excel workbook. Also triggers on: GTM playbook, GTM strategy, go-to-market plan, build my ICP, ideal customer profile, buyer journey, buying signals, signal library, signal-based selling, sales battlecard, objection handling, messaging matrix, positioning, sharpen our outbound. Do NOT use for ads (gt-google-ads / gt-linkedin-ads / gt-meta-ads), CRM cleanup (gt-hubspot-admin / gt-salesforce-admin), list building (gt-list-building), or cold emails (gt-cold-email).

  • Hubspot reporting

    Growth-Today/claude-skills/gt-hubspot-admin/.claude/skills/hubspot-reporting Skill

    2★ repo

    HubSpot reporting and dashboards. Use for building RevOps dashboards, the custom report builder (single/cross-object/funnel/attribution/cohort), attribution reporting, funnel and cohort analysis, SLA/KPI dashboards, and cleaning up stale dashboards. Triggers on "hubspot reporting", "dashboards", "custom report", "report builder", "attribution", "funnel report", "cohort report", "SLA dashboard", "KPI dashboard", "pipeline report", "cleanup dashboards". Do NOT use for building the underlying pipeline (use hubspot-pipelines-deals) or lead scoring models (use hubspot-segmentation).

  • Storytelling

    Growth-Today/claude-skills/gt-linkedin-content/.claude/skills/storytelling Skill

    2★ repo

    Structure LinkedIn post bodies using proven storytelling frameworks. Use when the user asks about post structure, AIDA, PAS, BAB, storytelling, narrative posts, system reveals, contrarian takes, or LinkedIn copywriting. Do NOT use for hooks/first lines (use hooks) or call-to-action endings (use cta).

  • Gt linkedin content

    Growth-Today/claude-skills/gt-linkedin-content Skill

    2★ repo

    A specialist for organic LinkedIn content aimed at B2B founders and GTM teams. Reach for it on anything across the LinkedIn writing workflow, opening lines and hooks, post structure and storytelling, format choice, posting cadence and timing, comments and engagement, CTAs and comment-gates, profile optimization, repurposing, monthly content planning, and turning a post into its parts (team copy, engagement comments, alt text) or a design brief. Fires on phrases like write a LinkedIn post, LinkedIn hook, the algorithm, carousel, newsletter, best time to post, posting cadence, grow my LinkedIn, content plan, content pillar plan, plan my month, fix this hook, make it less AI, P.S. line, comment gate, alt text, design brief. Do NOT use for LinkedIn Ads (use the linkedin-ads skill) or cold outreach to strangers (LinkedIn cold DMs use gt-linkedin-outbound, cold email uses the cold-email skill). Warm social selling to the audience your content builds IS in scope (see social-selling-campaigns.md).

  • Sf reporting

    Growth-Today/claude-skills/gt-salesforce-admin/.claude/skills/sf-reporting Skill

    2★ repo

    Salesforce reporting and dashboards — custom report types, RevOps reports & dashboards (pipeline, funnel, forecast, data quality), and dashboard cleanup. Use for building reports/dashboards and unlocking cross-object reporting. Triggers on "salesforce report", "custom report type", "dashboard", "cross-object report", "revops dashboard", "cleanup dashboards", "joined report". Do NOT use for building the pipeline (use sf-opportunities-sales) or lead scoring (use sf-segmentation).

  • Eng career goals writer

    tkolleh/skills/eng-career-goals-writer Skill

    2★ repo

    Seasoned engineering manager and career coach. Helps engineers translate tasks into SMART performance goals aligned with team and org strategy.

  • Qmd search

    tkolleh/skills/qmd-search Skill

    2★ repo

    Answers user questions by searching a local Markdown repository using the `qmd` (Quick Markdown Search) CLI toolkit. Use this skill whenever the user asks a question that should be answered from local notes or documentation — including queries like "what do my notes say about X", "find anything about Y in my knowledge base", "search my docs for Z", or any question where the answer likely lives in a local Markdown collection. Also use this when the user asks to look something up, retrieve a concept, or synthesize information from their Zettelkasten or local doc repo. Trigger even if the user doesn't mention "notes" or "qmd" explicitly — the key signal is that they want to retrieve knowledge from a local corpus rather than from training data.

  • Smart init

    tkolleh/skills/smart-init Skill

    2★ repo

    Trigger on: init, CLAUDE.md, AGENTS.md, setup repo, onboard, generate docs, project documentation for agents, bootstrap, new project setup. Evidence-guided AGENTS.md/CLAUDE.md generator that makes AI coding agent runs ~28% faster and ~16% cheaper by eliminating exploratory navigation.

  • Pwp docs

    shandar/pwp-plugin/skills/pwp-docs Skill

    2★ repo

    Documentation lifecycle protocol — living docs that stay current and traceable. Use this skill whenever the user needs to create, update, or organize project documentation. Also use when they say 'update the docs', 'write documentation', 'update the changelog', 'document this', 'add to the README', 'architecture docs', 'create a plan document', or ask about documentation structure, feature traceability, or post-completion walkthroughs. Covers living documents, feature traceability IDs, changelog management, architecture docs, and walkthrough artifacts.