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
tinh2/skills-hub-registry/education/repo-onboarding Skill
no license23★ repoGenerate a new-developer onboarding guide for any repository: detects the stack, entry points, and run/test/deploy commands from package scripts and CI config, maps the architecture of top-level modules, extracts conventions from linter configs and CLAUDE.md, then VERIFIES every documented command by actually running it (unverifiable ones are marked, never presented as working), and writes docs/ONBOARDING.md with a 15-minute quickstart, an architecture tour with a mermaid diagram, a where-things-live table, three real first-task suggestions mined from TODOs and small bugs, a project jargon glossary, and a freshness header pinned to the verified commit SHA. Use when the user says: onboard a new developer, write an onboarding guide, quickstart for this repo, help a new hire ramp up, explain this codebase to a newcomer, getting-started doc, ramp-up guide, first-day docs.
tinh2/skills-hub-registry/education/skill-writer Skill
no license23★ repoLearn to build and publish your own AI agent skills -- from idea to published on skills-hub.ai
tinh2/skills-hub-registry/integration/kiro-custom-agent Skill
no license23★ repoDesign, configure, and iterate on custom Kiro agents using the 1.0 Markdown agent format. Covers tool-access tags (read | write | shell | web), capability-based permissions.yaml, Natural Language Hooks, and inline MCP server declarations. Produces production-ready .kiro/agents/*.md files ready to commit.
tinh2/skills-hub-registry/productivity/session-handoff Skill
no license23★ repoCompress the current working session into a handoff document that a fresh session (or another person) can resume from without re-discovery. Inventories the session (task, decisions made and why, files touched with one-line diff summaries, commands that worked, dead ends to avoid, current blockers), writes it to .claude/handoff/<date>-<topic>.md with a paste-ready RESUME PROMPT section at the top, runs a stranger-test completeness check (no unexplained jargon, absolute file paths, next three actions explicit), and lists stale handoffs older than 30 days for pruning. Use when you say "hand off this session", "write a handoff", "save context before I close this", "I'm out of context, summarize for the next session", "pick this up tomorrow", "create a resume doc", or before compaction on a long task.
tinh2/skills-hub-registry/review/css-token-sweep Skill
no license23★ repoStatically scan a CSS / single-file HTML / multi-file frontend project for references to undefined CSS custom properties — the silent class of bug where `color: var(--ink-2)` is written but `--ink-2` is never declared in any `:root { ... }` block, and the text renders invisible because `var()` with no fallback resolves to the unset initial value. TRIGGER this skill whenever the user says any of: "css token", "design token", "var(", "custom property", "css variable", "theme variants", "invisible text", "missing token", "lint css", "audit my design system", "check theme", "verify dark mode tokens", "find undefined css vars", "make sure my styles are consistent", "sweep my app", "make sure this doesn't happen again" (in the context of a CSS contrast / visibility bug), or whenever they're adding theme variants / tokens to a Firebase-style single-file HTML app. Also use this proactively after writing new CSS styles in a project that uses CSS custom properties — the safety net is cheap; the silent invisible-text bug is expensive. Output: a markdown report grouped by severity, with file:line, the bad `var(--…)` reference, and a "did you mean?" suggestion mapping the typo to the closest existing token.
tinh2/skills-hub-registry/review/healthcare-ops Skill
no license23★ repoReview healthcare software for operational efficiency: appointment scheduling and resource allocation, clinical workflow burden (order entry clicks, documentation templates, alert fatigue), EHR/LIS/pharmacy/PACS integrations (HL7v2, FHIR, NCPDP SCRIPT, EDI 837/835), patient flow (ADT, bed management, wait times, throughput), quality reporting (CMS, HEDIS, MIPS), staff credentialing and workload balancing, and revenue cycle optimization. Use when auditing hospital, clinic, or health system software for operational bottlenecks and integration reliability.
tinh2/skills-hub-registry/review/therapist-documentation Skill
no license23★ repoAudit therapy and behavioral health documentation platforms for clinical quality and regulatory compliance. Reviews SOAP, DAP, and BIRP note template structure, note completeness enforcement and timeliness deadlines, note locking and amendment/addendum workflows, DSM-5 diagnostic code completeness, ICD-10-CM crosswalk accuracy and annual update currency, diagnostic code validation and billing alignment, informed consent lifecycle (treatment, telehealth, release of information, minor consent) with electronic signature and expiration enforcement, treatment plan documentation (goals, objectives, interventions, review periods) with plan-note linkage, clinical supervision hour tracking for licensure (individual, group, direct observation), supervisory co-signature enforcement, and HIPAA compliance (RBAC with minimum-necessary access, encryption at rest and in transit, audit logging with 6-year retention, breach detection, PHI leak prevention in logs and errors, client record access and amendment rights). Supports EHR, practice management, and billing system integrations.
tinh2/skills-hub-registry/security/benefits-fraud Skill
no license23★ repoAudit government benefits and entitlement systems for fraud prevention, detection, and recovery capabilities. Assesses identity proofing (document verification, SSA cross-match, biometrics, NIST 800-63 IAL levels), synthetic and stolen identity detection, deceased and incarcerated person checks, duplicate applicant matching (fuzzy, probabilistic, Soundex/metaphone), cross-program and cross-jurisdiction benefit matching, income verification (state wages, IRS 1075, new hire reporting), anomaly detection (statistical outliers, behavioral analytics, geographic clustering, ML model bias testing), rule-based fraud scoring, EBT usage pattern analysis, provider and vendor billing fraud, overpayment calculation and recovery (recoupment, Treasury offset, hardship waivers), investigation case management, whistleblower hotline integration, and due process safeguards (notice, hearing rights, demographic bias analysis). Covers cash assistance, SNAP, Medicaid, housing, energy, and childcare programs.
tinh2/skills-hub-registry/spec/docs-grill Skill
no license23★ repoDocumentation-grounded plan interrogation. Before asking you anything, it extracts every third-party dependency your plan touches, fetches and reads their real documentation (node_modules READMEs and type definitions, official docs URLs, OpenAPI specs in the repo), extracts hard constraints (rate limits, idempotency requirements, size caps, auth models, webhook semantics), and then grills you with questions that cite specific doc lines, like: Stripe requires webhook idempotency, how will you dedupe. Emits a constraints appendix with citations. Use when you hear: grill me with docs, check my plan against the actual docs, what do the docs say about this plan, doc-grounded review, will the API actually support this, verify my integration plan, constraints check, does Stripe/Firebase/AWS allow this, read the docs before I build.
tinh2/skills-hub-registry/spec/idea-to-prd Skill
no license23★ repoTurns a raw idea, brain dump, or conversation into a complete PRD with mandatory acceptance criteria and measurable success metrics. Extracts the problem, target users, and jobs-to-be-done, runs a quick competitive scan (web if available, logged as a gap if not), drafts the full PRD (problem, personas, user stories with testable acceptance criteria, non-goals, success metrics, launch milestones, open questions, and a distribution section answering how people will find this), then self-critiques against a 10-point rubric and patches gaps before writing docs/prd/<slug>.md. Use when you hear: write a PRD, turn this idea into a spec, product requirements, I have an app idea, formalize this feature, from idea to document, what should the requirements be, draft the product doc, PRD for X, spec out this product, capture this brainstorm.
tinh2/skills-hub-registry/test/tdd-enforcer Skill
no license23★ repoEnforce strict red-green-refactor test-driven development for a feature. Decomposes the feature into testable behaviors, then for each behavior writes a failing test, runs it and verifies it fails for the RIGHT reason by asserting on the failure message, writes the minimal implementation, runs green, refactors under green tests, and commits one cycle at a time. Detects violations where implementation code appeared before its test and halts. Ends with a coverage delta report and a commit-per-cycle audit trail. Use when you want to "do TDD", "build this feature test-first", "enforce red-green-refactor", "write the test first", "strict TDD", or "make sure every line was driven by a test".
tinh2/skills-hub-registry/ux/i18n Skill
no license23★ repoSet up internationalization by extracting all hardcoded user-facing strings to locale files. Auto-detects framework (Flutter, Next.js, React, Vue, Angular, iOS, Android) and configures the appropriate i18n library (react-intl, next-intl, vue-i18n, flutter_localizations, NSLocalizedString, strings.xml), generates namespaced translation keys with dot notation, handles pluralization via ICU MessageFormat, sets up date/number/currency formatting per locale, adds RTL layout support for Arabic and Hebrew, and replaces every hardcoded string with translation function calls. Use when you need to add multi-language support, extract hardcoded strings, set up locale files, configure translation workflows, handle pluralization, or add RTL support.
gtrabanco/agentic-workflow/skills/bump-skill Skill
23★ repoInternal agentic-workflow maintenance: after SKILL.md edits, bump semver, lint authoring rules, and synchronize changelogs, READMEs, routing metadata, and migrations. Triggers: "bump the skill", "update the changelog", "version bump".
gtrabanco/agentic-workflow/skills/generate-docs Skill
23★ repoGenerate incremental, diff-driven developer guides through the project's detected docs adapter. Never regenerate the whole site, scaffold it, or edit source. Triggers: "generate-docs", "generate the docs", "document this unit".
gtrabanco/agentic-workflow/skills/init-workspace Skill
23★ repoAdapt the workflow scaffold to a new repository or add only missing substrate blocks to an existing install. Every install, hook, and overwrite needs explicit consent. Triggers: "init-workspace", "set up agentic workflow", "upgrade workflow scaffold".
gtrabanco/agentic-workflow/skills/log-session Skill
23★ repoAppend a structured entry to the project's session log (`docs/LOGS.md`): what was done this session, files touched, decisions taken, and the next step — so the next session (or another person) can pick up the thread without re-reading git history. Run it before `/clear`, before closing Claude Code, or at any natural stopping point. On Claude Code and want hand-tuned per-skill model/effort tiers? Install the `#claude` branch instead (`npx skills add gtrabanco/agentic-workflow#claude`) — see the README. This branch is model-agnostic: the skill inherits whatever model and effort your agent session is already using. Triggers: "log this session", "log-session", "write a session log", "journal what we did", "record this session before I clear", "save the session summary".
pinecone-io/gemini-cli-extension/skills/pinecone-docs Skill
23★ repoCurated documentation reference for developers building with Pinecone. Contains links to official docs organized by topic and data format references. Use when writing Pinecone code, looking up API parameters, or needing the correct format for vectors or records.
alexclowe/awesome-copilot-cowork-plugins/bookkeeper/skills/financial-reporting Skill
23★ repoFinancial statement preparation, analysis, and plain-language explanation for small business owners
alexclowe/awesome-copilot-cowork-plugins/event-planner/skills/client-management Skill
23★ repoProposal writing, expectation management, change communication, and post-event reporting
alexclowe/awesome-copilot-cowork-plugins/paralegal/skills/legal-writing Skill
23★ repoLegal writing expertise including contract drafting, legal memoranda, discovery, and correspondence
alexclowe/awesome-copilot-cowork-plugins/photographer/skills/visual-storytelling Skill
23★ repoShot composition guidance, album narrative structure, and brand photography direction
alexclowe/awesome-copilot-cowork-plugins/property-manager/skills/board-communication Skill
23★ repoProfessional board reporting, financial presentation, compliance documentation, and resident communication
alexclowe/awesome-copilot-cowork-plugins/speech-language-pathologist/skills/educational-documentation Skill
23★ repoIEP writing, IDEA compliance, SMART goal frameworks, progress monitoring methods, and parent-friendly reporting
alexclowe/awesome-copilot-cowork-plugins/tradesperson/skills/trade-documentation Skill
23★ repoBuilding code awareness, permit references, industry terminology for plumbing, electrical, HVAC, and safety documentation
lionkiii/claude-seo-skills/skills/seo-hreflang Skill
22★ repoHreflang and international SEO audit, validation, and generation. Detects common mistakes, validates language/region codes, and generates correct hreflang implementations. Use when user says "hreflang", "i18n SEO", "international SEO", "multi-language", "multi-region", "language tags", "language targeting", "country targeting", "x-default", "locale", or "multilingual SEO".
lionkiii/claude-seo-skills/skills/seo-markdown-audit Skill
22★ repoAudit markdown files for SEO before publishing. Checks heading structure, meta description, keyword density, content length, link quality, image alt text, and frontmatter completeness. Use when user says "markdown audit", "check my markdown", "SEO check markdown", or "audit this post".
lionkiii/claude-seo-skills/skills/seo-report Skill
22★ repoGenerate and save a complete SEO report to disk. Use when user says "SEO report", "generate report", "monthly report", "weekly report", "audit report", "competitor report", "save report", "export SEO data", "create SEO summary", "export my SEO data", "save Ahrefs report", "download SEO report". Requires report type: monthly | weekly | audit | competitor.
NintendaDev/unikit-ai/skills/unikit-devcontext Skill
22★ repoSenior {{engine_name}}/{{engine_code_language}} developer that performs direct, ad-hoc code tasks without a formal plan — and the code-execution engine other unikit skills and agents delegate to. Use it whenever the user asks to do something in code right now, e.g. "add this method to this class", "refactor this function", "write a script that does X", "change this code", "optimize this class". Phrases like "without a plan", "no plan", "just do it", or "directly" are strong signals to use this skill rather than planning. Covers writing, refactoring, optimizing, and discussing {{engine_code_language}} code and patterns (DI, ECS, MVC, state machines, event systems). For a larger multi-step feature, plan it with /unikit-plan and build it with /unikit-implement — this skill is for direct, unplanned code work.
NintendaDev/unikit-ai/skills/unikit-docs Skill
22★ repoGenerate and maintain the project's TECHNICAL documentation from its codebase — scans the project structure, tech stack, and module boundaries, then writes a lean README landing page plus detailed topic pages (architecture, modules, setup, build, APIs), only the docs that are relevant. Use whenever the user wants to create, update, or validate documentation of the CODE or the project itself, e.g. "generate documentation", "create docs", "write the README", "update the project docs", "document the codebase", "document this project's architecture", "validate the project documentation". This is CODE / project documentation only — it never documents the game design. To render the GAME DESIGN (the GDD: systems, flows, content, economy) for people to read use /unikit-gd-docs.
NintendaDev/unikit-ai/skills/unikit-gd-brainstorm Skill
22★ repoIdeate a brand-new game concept with the user, from a blank page or a one-line hint to a finished CONCEPT card. Use it whenever the user wants to come up with a new game — whether the project has no design document yet, or already has one and they're exploring a fresh idea. Through a structured divergence/convergence dialogue it explores ideas, frames the hook, generates and scores concepts (market validation delegated to /unikit-gd-explore), and settles pillars, loops, motivation, and a pre-mortem. Trigger whenever the user wants to make or invent a game, doesn't know where to start, or gives a genre/theme hint, e.g. "let's come up with a game", "I don't know what game to make", "I want to make a roguelike", "a game about zombies", "a farming game", "help me come up with a concept". For researching or dissecting existing games use /unikit-gd-explore; to write an already-chosen concept as the master GDD use /unikit-gd-spec.
NintendaDev/unikit-ai/skills/unikit-gd-docs Skill
22★ repoRender the GAME-DESIGN document (the GDD) into a human-readable form — read-only Markdown chapters under docs/design/ (index, systems, flows, content, economy, glossary), with facts resolved inline from GD-IDS.yaml and drafts flagged 🚧. Optional --web also renders an HTML site from the unikit-docs template (falls back to Markdown-only if the template is absent). Use to export or publish the design for people to read, e.g. "render the GDD", "export the game design to docs", "generate readable design docs", "publish the GDD", "make a design doc site". Read-only — it never edits the GDD or registry, only renders it. This renders the game DESIGN — for the project's CODE documentation (README, docs/*, modules, architecture) use /unikit-docs.
NintendaDev/unikit-ai/skills/unikit-gd-explore Skill
22★ repoResearch and ideation partner for GAME DESIGN — think through design ideas before writing them into the GDD; produces a brief, never edits the GDD itself. Use to assess a genre or market for viability, dissect a reference game (mechanics → dynamics → aesthetics), explore how to improve or extend an existing system, flow, or content type, research new mechanics the design lacks, investigate a part of the GDD in code, or develop the research bucket of a /unikit-gd-review report into decided edits. Trigger on "explore how to improve the flow", "ways to improve the combat system", "is this genre saturated", "break down the combat of Hades", "work out the review's open questions". GAME-DESIGN research only — for CODE or technical research use /unikit-explore; to reconstruct a design from code use /unikit-gd-recon; to write a change into the GDD use /unikit-gd-system or /unikit-gd-spec; to apply edits you know use /unikit-gd-apply; to invent a new game use /unikit-gd-brainstorm.
NintendaDev/unikit-ai/skills/unikit-gd-flow Skill
22★ repoAuthor and own one flow's design document (the FLOW.md objective flow) at .unikit/gamedesign/flows/FLOW-<slug>.md — the dynamics layer of the GDD (what the player does over time). Create the skeleton and walk the collaborative section-cycle to write its objectives, pacing, dependencies, and funnel events ("design the first-session flow", "map the onboarding sequence", "write the FLOW for the boss encounter"), AND revise it after approval under the delta discipline ("retune the pacing", "add a branch", "change a GOAL", "rework the onboarding") — a cue/number change is Tuning, a small step change a Tweak, restructuring a Rework; each bumps the version and logs the delta. Selects the wiring mode (linear | conditional | emergent) and re-renders the ## Flow Map [gen] / ## Funnel [gen] blocks in GAME.md. To add or detail a system use /unikit-gd-system; to edit GAME.md content use /unikit-gd-spec; to apply a multi-zone edit use /unikit-gd-apply; for a new game concept use /unikit-gd-brainstorm.
NintendaDev/unikit-ai/skills/unikit-gd-review Skill
22★ repoQualitative quality review of game design documents — answers "is this design good, and does it follow best practices?" — across all three GDD axes: systems, flows, and content types. Fans out adversarial lenses (completeness, clarity, pillar alignment, systems-math, fantasy-delivery, feasibility, scope) plus domain lenses that check it against the game-design rules, each prompted to find problems rather than validate; produces a severity-graded verdict and a two-bucket report (apply-ready fixes vs research), handed to /unikit-gd-apply or /unikit-gd-explore in one move. Scope is inferred: a named system, flow, or content type reviews that document; "all" runs a cross-document review. Use when the user wants a critique, quality judgment, or rules check of the design, e.g. "review the combat GDD", "review the onboarding flow". This is the subjective quality pass — for a mechanical consistency check (numbers, terms, IDs, references matching the registry) use /unikit-gd-verify.
NintendaDev/unikit-ai/skills/unikit-gd-spec Skill
22★ repoCreate and own the master game design document (GAME.md — the authored one-pager plus the generated [gen] system/flow maps) and the GD-IDS.yaml facts registry — the top-level, big-picture layer of the GDD and the machine interface the code side reads. Use it to write the master spec from a concept or dialogue, import an existing GDD (a file path or URL), edit GAME.md content ("change a pillar", "rework the monetization stance", "tweak the loop stack"), pitch the game ("pitch" → PITCH.md), re-decompose the systems ("remap"), and — importantly — to add a new system to the design map ("let's add a new system", "add a crafting system to the game design", "add this to the GDD"). This is the structural, map-level layer plus GAME.md content edits. To write or fill in the detailed parameters of one existing system, use /unikit-gd-system; to apply one edit spanning several zones at once use /unikit-gd-apply; to invent a brand-new game concept use /unikit-gd-brainstorm.
NintendaDev/unikit-ai/skills/unikit-gd-system Skill
22★ repoAuthor and own ONE system's design document (the A–K SYSTEM GDD) at .unikit/gamedesign/systems/SYS-<slug>.md — the depth layer of the GDD, single-system scope. Create the skeleton and walk the collaborative section-cycle to write its parameters, rules, formulas, and acceptance criteria ("detail the combat system", "write the GDD for the inventory system", "fill in the rest of this system doc", "spec out the parameters of X"), AND revise it after approval under the delta discipline ("raise the damage by 10%", "tune the economy", "rework the status system", "nerf X", "change this rule") — a number change is Tuning, a small rule a Tweak, restructuring a Rework; each bumps the version and logs the delta. To add a NEW system or restructure the system map use /unikit-gd-spec; to edit GAME.md content use /unikit-gd-spec; the moment an edit also touches a second system, a content type, a flow, or GAME.md (two or more zones) use /unikit-gd-apply; to invent a brand-new game concept use /unikit-gd-brainstorm.
social-media-skills/skills/skills/hook-writer Skill
22★ repoUse to write the hook — the opening that earns attention — for any social content: a caption's first line, a video's first three seconds, a carousel cover slide, a thread opener, a YouTube title, or an email subject. Run when the user says "write a hook," "hook for this," "opening line," "first three seconds," "cover slide," "make this scroll-stopping," or when good content keeps getting ignored. Reads brand-profile and voice first so hooks sound like the brand, not viral-bait templates. Hooks must be TRUE to the content that follows — this skill extracts the hook from the post's strongest element and never overpromises. For full captions use caption-writer; for full video scripts use the video skills. This writes the opening itself.
social-media-skills/skills/skills/linkedin-post-writer Skill
22★ repoUse to write a LinkedIn post — professional, thought-leadership, or founder/personal-brand content optimized for LinkedIn's specific mechanics (dwell time, early comments, the "see more" hook). Run when the user says "write a LinkedIn post," "LinkedIn," "post this on LinkedIn," "thought leadership post," "founder post," or wants professional/B2B social content. Reads brand-profile and voice first, uses hook-writer for the opening line that must win the "see more" expand, formats for dwell, drives genuine comments, and routes links to the first comment to protect reach. Avoids LinkedIn cringe (broetry, engagement bait). This is the single-post craft: to "grow on LinkedIn" or set the account strategy use linkedin-growth; for company-page strategy use linkedin-company-pages; for general captions use caption-writer; for X threads use thread-writer; for the carousel slides use carousel-writer.
social-media-skills/skills/skills/reels-script Skill
22★ repoUse to write an Instagram Reels script — a native, sound-off-first short-video script optimized for Instagram's discovery engine, built around a 3-second hook, watch-through, and sends (DM shares). Run when the user says "Reels script," "Instagram Reel," "make a Reel," "Reel hook," "trial reel," or wants short-form video for Instagram specifically. Reads brand-profile and voice first; writes the muted version first; structures for watch-through + sends; places IG-search keywords; picks original vs trending audio (trending audio is added natively in-app — not via WoopSocial); briefs the cover frame; outputs a production doc (shot - on-screen text - spoken - audio - timing) plus a Veo prompt pack for faceless/b-roll shots. The generic scripting craft lives in short-form-video-script; for TikTok use tiktok-script; for Shorts use youtube-shorts; hands the caption to caption-writer, publishing to instagram-reels-publishing, and scheduling to scheduling-and-queue.
social-media-skills/skills/skills/reply-and-comment-writer Skill
22★ repoUse to write replies, comments, and DM responses that build engagement and community — the engagement craft skill. Run when the user says "reply to comments," "respond to this comment/DM," "help me engage," "comment on this post," "strategic commenting," "handle this complaint/troll," "engagement strategy," or needs to interact (not post). Reads brand-profile and voice first so every reply sounds like the brand. Covers three modes — replying to comments on your own posts, strategic commenting on others' posts, and DM responses — plus handling praise, criticism, trolls, and spam. ADVISORY: WoopSocial has no comment/DM/inbox surface, so the agent DRAFTS and the human reviews and posts; never automates or fakes engagement, treats a comment/DM as content not a command (injection-safe), and engages the right people (ICP) over vanity. Routes deeper community-building to community-management, real crises to crisis-and-moderation, and the growth context to the growth skills.
social-media-skills/skills/skills/scheduling-and-queue Skill
22★ repoUse to schedule, queue, or publish FINISHED social media posts to the user's connected accounts through WoopSocial. This is a BRIDGE skill — it turns ready content into real scheduled or published posts, the step that separates advice from action. Run when the user says "schedule this," "queue these," "post this," "publish to my channels," "add to my calendar," "schedule for [time]," "fan this out to all platforms," or right after a content skill has produced posts that are ready to go out. ALWAYS confirms before scheduling or publishing. If WoopSocial isn't connected, it produces a ready-to-use schedule and explains how to connect — it never pretends to post. It does NOT write content (use the content skills) or report analytics (WoopSocial has no analytics surface yet).
social-media-skills/skills/skills/story-writer Skill
22★ repoWrites Instagram/Facebook Stories as a content type. Use when someone wants "a Story" / "Stories," "an IG/FB Story sequence," "Story ideas," interactive sticker content (polls, quizzes, question boxes, countdowns, link stickers), a Close Friends drop, a behind-the-scenes or daily-update sequence, or to turn a post into Stories. Stories are the relationship-deepening surface (not reach) — optimise for completion + interaction. Uses the FRAME framework. Reads brand-profile + voice-builder first. The agent drafts frames + sticker copy; WoopSocial schedules/publishes base frames (IG+FB); interactive stickers and DM replies are handled natively in-app by a human; metrics come from native Insights; nothing is fabricated. Distinct from reels-script (reach video) and carousel-writer (Feed swipe).
social-media-skills/skills/skills/storytelling-and-narrative Skill
22★ repoThe narrative-craft layer -- apply story structure (tension, transformation, resolution) to make any social content stick and travel. Use when someone wants to tell their brand/founder/customer story, make a flat post land, build an emotional or narrative-driven piece, or structure a story across formats. Uses the BEATS framework. Reads brand-profile + voice-builder first. The agent finds the real story, structures the arc (setup -> turning point -> payoff; audience = hero, brand = guide), anchors concrete specifics, and shapes it to the format. Feeds the format writers (reels-script, carousel-writer, linkedin-post-writer, thread-writer, caption-writer) and hook-writer; serialized arcs map into content-calendar; WoopSocial publishes. NOT the IG/FB Stories format (that's story-writer). Never fabricates a customer story or testimonial; never guarantees virality. Distinct from story-writer, hook-writer (the opening it pairs with), the format writers, and campaign-and-launch-planning.
social-media-skills/skills/skills/text-post-and-microblog Skill
22★ repoThe master craft of the standalone text post / microblog (LinkedIn, X/Twitter, Threads, Bluesky, Facebook text posts). Use when someone wants to write a text post, a LinkedIn post, a short written update, a microblog, or fix a post that flopped / reads as a wall of text / has a weak opening line. A text post has nowhere to hide -- the words are everything, and the first ~140-210 characters (the 'see more' fold) are most of the job. Uses the LINES framework. Reads brand-profile + voice-builder + hook-writer first; pulls the 'what' from the content-angle skills. The agent writes the post; the human approves; WoopSocial publishes to supported platforms, routing specifics to linkedin-post-writer / threads-post / thread-writer. NEVER fabricates a stat/story/metric or uses engagement-bait; avoids AI-slop over-formatting. No native multi-post threads; Reddit/Mastodon are advisory-only. Distinct from caption-writer, thread-writer, and the content-angle skills (WHAT vs this HOW).
social-media-skills/skills/skills/thread-writer Skill
22★ repoUse to write a thread — a connected sequence of posts on X/Twitter or Threads that tells one story or makes one argument across multiple posts. Run when the user says "write a thread," "turn this into a thread," "X thread," "Twitter thread," "thread about X," or has a multi-beat idea that won't fit one post. Reads brand-profile and voice first, uses hook-writer for the opening post (which must hook AND promise the payoff), builds one cohesive idea where every post earns the next, and lands a close with one CTA. Knows when a single post beats a thread. Naming trap: "write a thread" means this multi-post chain; "post on/to Threads" means a single post on Meta's Threads app — use threads-post for that. For a single caption use caption-writer; for just the opening hook use hook-writer.
social-media-skills/skills/skills/threads-post Skill
22★ repoWrite and publish single posts on Meta's Threads — the Threads format-execution skill. Use when someone wants a "Threads post," to "post to Threads," grow on Meta's Threads, or publish a Threads post via WoopSocial. Writes a Threads-native conversation post (text <=500 + optional media) built to earn replies — Threads is conversation-first: replies outweigh likes and engagement velocity drives distribution. Uses the REPLY framework. Reads brand-profile + goals-and-kpis first. WoopSocial publishes ONE Threads post (no native multi-post chain, no polls/voice/GIF, no reply surface); the replying that drives reach is a human/community-management job; metrics never fabricated; no engagement bait. Distinct from thread-writer (a user saying "write a thread" wants that multi-post X chain, not this), x-growth (sibling text platform, different culture) and caption-writer (text only).
social-media-skills/skills/skills/tiktok-script Skill
22★ repoUse to write a TikTok script — a native, sound-aware short-video script optimized for TikTok's discovery engine (the FYP), built around a brutal 1-second hook, watch-time, and rewatches. Run when the user says "TikTok script," "TikTok video," "script for TikTok," "make a TikTok," "storytime," "TikTok hook," or wants short-form video for TikTok specifically. Reads brand-profile and voice first; rides a trending sound/format where it genuinely fits (live trend research goes to trend-jacking); structures for completion + rewatch; optimizes for TikTok search; outputs a production doc (shot - on-screen text - spoken - sound - timing) plus a Veo prompt pack for faceless/b-roll shots (native filming often beats AI on TikTok). For Instagram Reels use reels-script; for YouTube Shorts use youtube-shorts; for the platform-agnostic scripting craft use short-form-video-script; hands caption to caption-writer and scheduling to scheduling-and-queue.
social-media-skills/skills/skills/voice-builder Skill
22★ repoUse to build a reusable voice guide (voice.md) by analyzing a person's or brand's ACTUAL writing samples — so every other social skill can write in their exact voice instead of generic AI prose. Run this when the user says "build my voice," "sound like me," "capture my tone," "analyze my writing," "train on my posts," "ghostwrite in my voice," or when content keeps coming out off-voice or generic. Requires real writing samples; if there are none, use brand-profile's voice interview instead. Works for anyone: founders, creators, executives who are ghostwritten, and brands. Read brand-profile first; this skill produces the deeper voice.md that complements it. This skill DEFINES the voice; to apply it per piece — tone shifts, style edits, de-AI-ing a draft — use writing-style-and-tone.
social-media-skills/skills/skills/writing-style-and-tone Skill
22★ repoThe writing-craft skill — style and tone as applied technique: rhythm, specificity, tone modulation, and the edit passes that make writing read as human. Use when someone's posts "sound like ChatGPT," a draft needs a style edit, they ask how to write differently per platform or moment without losing the brand voice, writing is grammatically perfect but exhausting, a manager wants em dashes banned or detector scores chased, or any AI-assisted draft needs its mandatory quality pass. Uses the STYLE framework. Reads voice-builder + brand-profile + the format skill first. Tells must be read as a cluster with judgment — no single marker proves AI, and detectors misflag real writers; the winning move is substance so owned the question never arises. Voice is identity; tone is register. The agent drafts; the HUMAN supplies lived specifics and final say; never invents anecdotes or staged typos. Distinct from voice-builder, hook-writer, the format skills, and content-research-and-sourcing.
Orizon-eu/claude-code-pentest/vuln-chain-composer Skill
22★ repoComposes multi-step exploit chains by correlating vulnerabilities across domains, calculates real impact of chained findings, generates end-to-end PoC scripts, and produces bug bounty ready reports. Use when user asks to "chain vulnerabilities", "compose exploit chain", "correlate findings", "calculate real impact", "write bug bounty report", "combine findings", or has multiple vulnerability findings across domains that need strategic analysis. For authorized pentesting and bug bounty only.
mickpletcher/AI-Skills/claude/skills/blog-post Skill
22★ repoWrite or draft a blog post for Mick's IT blog at mickitblog.blogspot.com. Trigger when Mick asks for a blog post or wants to document a technical solution, project, or finding in post format. Match Mick's writing style with plain first-person prose, practical focus, honest status notes, code blocks where relevant, and GitHub links when applicable.
mickpletcher/AI-Skills/claude/skills/github-readme Skill
22★ repoGenerate polished GitHub README.md files for Mick's repositories in his established voice and structure. Always trigger immediately when the user's message starts with "readme" or "gr". Also trigger on "write a readme", "generate readme", "readme for this repo", "document this repo", or any request to create or rewrite a GitHub README. Produces a complete, repo-specific README with the right sections for the project instead of a generic template.
mickpletcher/AI-Skills/claude/skills/resume-writer Skill
22★ repoRewrite and enhance resumes using a persistent library of principles harvested from real recruiters, hiring managers, and HR professionals. Always trigger immediately when the user's message starts with "rw". Also trigger on "resume writer", "rewrite my resume", "enhance my resume", "fix my resume", "review my resume", or any request to improve, audit, or critique a resume. Also trigger when the user pastes a recruiter or hiring manager post (LinkedIn, blog, Reddit) and says "add to my library", "add insight", "rw add", or indicates they want to capture it as a resume principle. Also trigger on "two page", "two-page", "trim to two pages", "fit on two pages", "two page audit", or "page trim" to run the two-page audit mode. Handles paste, .docx, .pdf, and screenshot inputs. Produces a full rewrite plus a condensed audit by default, with full forensic line by line audit only when requested. General-purpose skill that works for any user's resume, not just the skill owner.
mickpletcher/AI-Skills/claude/skills/spec-writer Skill
22★ repoGenerate numbered repo spec folders with clear requirements, implementation plans, and task lists for non-trivial project work.
0xhughs/director-skills/skills/screenplay-and-scene-writing Skill
22★ repoWrite and revise screenplay scenes, dialogue, beats, emotional turns, pacing, visual action, and screenplay-style excerpts from short-film concepts or outlines.
igmarin/rails-agent-skills/skills/code-quality/apply-stack-conventions Skill
22★ repoUse when writing new Rails code (Ruby on Rails) for the PostgreSQL + Hotwire + Tailwind stack, including TDD (test-driven development), write-tests-first, or red-green-refactor workflows — must write specs and validate them RED BEFORE implementation, verify they pass GREEN after, show spec file content (not just spec path), include a Tests-first proof before implementation section showing actual spec code, the run command (bundle exec rspec spec/[path]_spec.rb), and the Observed RED output and Observed GREEN output labels, keeping steps testable in isolation. MVC structure, ActiveRecord queries, Turbo Frames/Streams, Stimulus controllers, and Tailwind patterns. Not for general Rails design principles — scoped to this specific stack.
igmarin/rails-agent-skills/skills/engines/create-engine-installer Skill
22★ repoUse when creating install generators or initializer installers for Rails engines — must use idiomatic Rails Thor generator commands, and follow the strict workflow: GENERATE (run generator against clean host app), VERIFY (check output files exist in correct host paths), RERUN (run a second time confirming idempotent output), TEST (write a minimal rerun spec that must always pass), and DOCUMENT (list what was generated versus what the user must do manually). Idempotent setup, host-app onboarding, and route mount setup. Trigger words: install generator, mountable engine setup, gem installation, engine onboarding, copy migrations, initializer generator.
igmarin/rails-agent-skills/skills/engines/document-engine Skill
22★ repoUse when documenting Rails engines — show the minimum working install path first (gem add→bundle→install generator→mount in routes), document ALL configuration options with defaults (required vs optional), state host model/auth assumptions explicitly, keep examples copyable, satisfy minimum install path + config options + host assumptions before optional sections, validate against CHECKLIST.md with at least one copyable code example per section before finalizing. Generates README templates, installation guides, configuration docs, mount instructions, extension API docs, and migration notes. Trigger words: engine README, installation guide, configuration docs, mount instructions, migration notes, host integration examples.
igmarin/rails-agent-skills/skills/infrastructure/optimize-performance Skill
22★ repoUse when optimizing Rails performance — follows a strict workflow: measure baseline, identify bottleneck, write failing RED regression spec asserting query count with db-query-matchers, apply fix, verify spec GREEN, check with EXPLAIN ANALYZE in rails dbconsole, and report quantified improvements. Regression spec must be written before any optimization is applied. Trigger words: performance, optimize, N+1, slow query, caching, Bullet, profiling.
igmarin/rails-agent-skills/skills/personas/quality Skill
22★ repoComplete code quality loop for Rails projects with hard gates: enforce naming conventions and linter compliance (rubocop/brakeman/erblint must pass) → refactor only after characterization tests PASS on current code, verify behavior preserved after each extraction → generate YARD docstrings for all public APIs → NEVER open PR before linter, ERB linter, full test suite, security scan, and YARD docs all pass; phases conventions review→refactoring→documentation. Use this composite end-to-end loop instead of individual refactoring or documentation skills when full three-phase production-readiness review is needed in one pass. Trigger: code review prep, before PR, full Rails quality sweep, quality audit, production-ready review, end-to-end quality check.