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
jp-solumhealth/jpstack/investor-report Skill
1★ repoGenerate concise investor reports for Solum Health. Pulls metrics from Google Sheets, analyzes customer conversations from Fireflies, and produces a structured DOCX report matching the investor update template. Use this skill when the user says "investor report", "investor update", "monthly report for investors", "board update", "generate investor deck", "how are we doing this month", or any variation of wanting a periodic investor-facing summary. Default period: previous calendar month. User can specify a different period.
jp-solumhealth/jpstack/post-conference-insights Skill
1★ repoProduce branded conference recap one-pagers (1-2 page PDF) that position Solum Health as an industry thought leader. Use this skill whenever the user mentions a conference, summit, event, or expo they attended or want insights from. Also trigger on: "conference recap", "post conference insights", "event highlights", "conference one-pager", "summit recap", "what happened at [event]", "conference takeaways", "event summary", "write up from [event]", "key takeaways from [conference]", or anything involving turning conference attendance into a shareable client-facing document. Even if the user just names a conference ("HIMSS", "BHASe", "Becker's"), assume they want the full insight one-pager workflow unless they say otherwise.
jp-solumhealth/jpstack/team-feedback Skill
1★ repoFormat feedback for the Solum platform team — new rules (eligibility, insurance, copay), bug reports, and feature requests — using the WHEN/THEN/Example framework with Trading Partner IDs. Use this skill when the user wants to send feedback to the team or eng, report a platform bug, request a rule change, write a feature request, or convert raw clinic feedback into implementable rules. Triggers: "feedback for the team", "write this up for eng", "report this to the team", "new rule for the platform", "feature request", "convert this into a rule", "regla para la plataforma", or when the user pastes raw clinic feedback about eligibility, insurance, or copay behavior that needs to go to engineering.
jp-solumhealth/jpstack/weekly-retro Skill
1★ repoWeekly business retrospective for a solo founder. Reviews the past 7 days across all channels: deals closed/lost (HubSpot), calls made and quality (Fireflies), content published, outreach performance (Apollo), conference pipeline, and revenue vs. target. Produces a scored report with wins, losses, learnings, and priorities for next week. Use this skill when the user says "weekly retro", "weekly review", "how did this week go", "business retro", "founder retro", "end of week review", "weekly scorecard", "weekly report", or any variation of wanting a structured look-back at the past week's business performance. NOTE: This is different from gstack's /retro which analyzes engineering commit history and code patterns. This skill analyzes business execution: revenue, pipeline, calls, content, outreach.
Chrike/coding-agent-skills/skills/markdown-memory Skill
no license1★ repoUse when the user clearly asks to record, update, prune, or consult project-governed Markdown reference lessons about repeated mistakes, corrections, or confirmed approaches that must be versioned, shared, reviewable, or otherwise tied to repository history. Do not use for automatically loaded CLAUDE.md or .claude/rules instructions, host auto memory, handoff state, or decision-frontier planning.
KonH/ClaudeTools/plugins/k/skills/specify Skill
1★ repoCapture feature intent and acceptance criteria before planning begins, writing docs/specs/<YY_MM_DD_HH>_<name>/spec.md. Stops for user approval before the plan skill runs.
Yesterday-AI/ytstack/skills/oss-project Skill
1★ repoScaffold, polish, and publish open-source projects with AI-first documentation, governance, and CI. Use when: Starting a new OSS package, polishing/publishing an existing repo, setting up AGENTS.md / CONTEXT.md / DECISIONS.md / ROADMAP.md, onboarding AI agents to a codebase, or creating standard community files (README, LICENSE, CONTRIBUTING, CHANGELOG, CI pipelines, issue templates). Outputs repo description and tags at the end.
Yesterday-AI/ytstack/vendor/gstack/document-release Skill
1★ repoPost-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when asked to "update the docs", "sync documentation", or "post-ship docs". Proactively suggest after a PR is merged or code is shipped. (gstack)
Yesterday-AI/ytstack/vendor/gstack/landing-report Skill
1★ repoRead-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)
Yesterday-AI/ytstack/vendor/gstack/make-pdf Skill
1★ repoTurn any markdown file into a publication-quality PDF. Proper 1in margins, intelligent page breaks, page numbers, cover pages, running headers, curly quotes and em dashes, clickable TOC, diagonal DRAFT watermark. Not a draft artifact — a finished artifact. Use when asked to "make a PDF", "export to PDF", "turn this markdown into a PDF", or "generate a document". (gstack) Voice triggers (speech-to-text aliases): "make this a pdf", "make it a pdf", "export to pdf", "turn this into a pdf", "turn this markdown into a pdf", "generate a pdf", "make a pdf from", "pdf this markdown".
Yesterday-AI/ytstack/vendor/superpowers/skills/writing-plans Skill
1★ repoUse when you have a spec or requirements for a multi-step task, before touching code
The same file is in 12 other repositories
Yesterday-AI/ytstack/vendor/superpowers/skills/writing-skills Skill
1★ repoUse when creating new skills, editing existing skills, or verifying skills work before deployment
The same file is in 7 other repositories
yokeloop/yoke/skills/grill-docs Skill
1★ repoDocs-aware grilling: interrogates the user's plan one question at a time AND maintains the domain glossary (.yoke/context.md) and architecture decision records (.yoke/adr/) inline as decisions crystallise. Used to stress-test a plan against the project's language and documented decisions; for a plain interview that writes no files, use grill. Activates when the user writes "grill-docs", "grill with docs", "grill and update the glossary", "grill and write ADRs", "stress-test against the glossary", "challenge my plan and capture decisions".
claude-hangar/claude-hangar/core/skills/docs-team Skill
1★ repoLaunch parallel documentation agents: one detects what changed, one updates docs, one verifies completeness against the codebase. Use when: "docs team", "docs-team", "update docs", "documentation sweep", "stale docs".
Double loop execution reviewer
limerickgds/dashi-skills/skills/double-loop-execution-reviewer Skill
1★ repoA double-loop learning execution review skill. Reviews the execution history after a task is completed and turns it into a concise retrospective, handoff, or improvement memo. Use this whenever a coding, writing, research, planning, debugging, or operational task has just finished; whenever files, commands, tests, or deliverables were produced; whenever the user asks to summarize what was done, review the execution, create a handoff, capture lessons learned, or prepare for the next iteration; and especially when the user needs not only a summary of what happened, but a judgment about whether the original goal, assumptions, success criteria, or working rules should change before the next pass. If there is execution evidence in the conversation, err on the side of using this skill instead of waiting for the user to ask explicitly.
odere-pro/claude-wiki-pages-plugin/skills/markdown Skill
1★ repoQuery the wiki and render the answer as portable, GitHub-flavored markdown saved under vault/output/. Trigger when the user asks to "export X as markdown", "produce a markdown brief", "save the answer to the output folder", "give me a plain markdown version of …", or invokes /claude-wiki-pages:markdown directly. Reuses the query reading contract, then strips Obsidian-only syntax so the file is usable outside the vault.
odere-pro/claude-wiki-pages-plugin/skills/obsidian-markdown Skill
1★ repoCreate and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
odere-pro/claude-wiki-pages-plugin/skills/status Skill
1★ repoOne-command health check. Exercises every hook path and reports pass/fail per hook — without writing to vault/. Trigger when the user says "status", "health check", "is everything wired up", "did the install work", "dashboard", or invokes /claude-wiki-pages:status directly. Strictly read-only against vault content; any accidental write is the skill's own bug.
odere-pro/claude-wiki-pages-plugin/skills/voice Skill
1★ repoThe house writing voice for claude-wiki-pages — how to write prose that a newcomer actually wants to read and an engineer can trust. Defines two registers (explanatory and engineer), the rule for choosing between them, the LLM-artifact blocklist, the vocabulary and register-separation rules the doc gate enforces, and how to write a wiki page. Trigger when writing or editing any doc, README, guide, or wiki page, or when an agent asks "what voice should I write in", "how should this note read", or invokes /claude-wiki-pages:voice. Reference, not action — it teaches how to write, it does not write for you.
timdevai/proteus/skills/community/from-alireza/business-growth/skills/contract-and-proposal-writer Skill
1★ repoGenerate professional, jurisdiction-aware business documents: freelance contracts, project proposals, SOWs, NDAs, and MSAs. Structured Markdown output with docx conversion instructions. Covers US (Delaware), EU (GDPR), UK, and DACH (German law) jurisdictions. Not a substitute for legal counsel — use as strong starting points. Use when drafting a freelance contract, preparing a client proposal, writing an SOW for a new engagement, or producing an NDA before sharing sensitive material.
The same file is in 3 other repositories
timdevai/proteus/skills/community/from-alireza/engineering-team/playwright-pro/skills/report Skill
1★ repoGenerate test report. Use when user says "test report", "results summary", "test status", "show results", "test dashboard", or "how did tests go".
The same file is in 6 other repositories
timdevai/proteus/skills/community/from-alireza/engineering-team/skills/tdd-guide Skill
1★ repoTest-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and Mocha. Use when the user asks to write tests, improve test coverage, practice TDD, generate mocks or stubs, or mentions testing frameworks like Jest, pytest, or JUnit.
The same file is in 4 other repositories
timdevai/proteus/skills/community/from-alireza/engineering/grill-with-docs/skills/grill-with-docs Skill
1★ repoDocs-anchored grilling session — challenges a plan against the project's existing language (CONTEXT.md) and recorded decisions (docs/adr/), and updates those files inline as terminology and decisions crystallise. Use when user wants to stress-test a plan against documented domain language, or mentions "grill with docs".
The same file is in 3 other repositories
timdevai/proteus/skills/community/from-alireza/engineering/skills/changelog-generator Skill
1★ repoProduce consistent, auditable release notes from Conventional Commits. Separates commit parsing, semantic-bump logic, and changelog rendering for automated releases with editorial control. Use when cutting a release, generating CHANGELOG.md from git history, or automating release notes in CI.
timdevai/proteus/skills/community/from-alireza/engineering/skills/codebase-onboarding Skill
1★ repoAnalyze a codebase and generate onboarding documentation for engineers, tech leads, and contractors. Fast fact-gathering and repeatable onboarding outputs. Use when onboarding a new engineer, writing architecture-overview docs for a new project, or producing tech-lead briefings for unfamiliar repos.
The same file is in 3 other repositories
timdevai/proteus/skills/community/from-alireza/engineering/skills/runbook-generator Skill
1★ repoGenerate operational runbooks from a service name — deployment, incident response, maintenance, and rollback workflows. Templated structure customizable per environment. Use when documenting on-call procedures for a new service, standardizing incident response across teams, or producing runbooks before launching to production.
The same file is in 4 other repositories
timdevai/proteus/skills/community/from-alireza/engineering/write-a-skill/skills/write-a-skill Skill
1★ repoCreate new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.
The same file is in 3 other repositories
timdevai/proteus/skills/community/from-alireza/marketing-skill/skills/content-creator Skill
1★ repoDeprecated redirect skill that routes legacy 'content creator' requests to the correct specialist. Use when a user invokes 'content creator', asks to write a blog post, article, guide, or brand voice analysis (routes to content-production), or asks to plan content, build a topic cluster, or create a content calendar (routes to content-strategy). Does not handle requests directly — identifies user intent and redirects to content-production for writing/SEO/brand-voice tasks or content-strategy for planning tasks.
The same file is in 4 other repositories
timdevai/proteus/skills/community/from-alireza/marketing-skill/skills/content-strategy Skill
1★ repoWhen 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," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.
The same file is in 1 other repository
timdevai/proteus/skills/community/from-alireza/marketing-skill/skills/copywriting Skill
1★ repoWhen 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," or "CTA copy." For email copy, see email-sequence. For popup copy, see popup-cro.
The same file is in 1 other repository
timdevai/proteus/skills/community/from-alireza/marketing-skill/video-content-strategist/skills/video-content-strategist Skill
1★ repoUse when planning video content strategy, writing video scripts, optimizing YouTube channels, building short-form video pipelines (Reels, TikTok, Shorts), or repurposing long-form content into video. Triggers: 'start a YouTube channel', 'video content strategy', 'write a video script', 'repurpose into video', 'YouTube SEO', 'short-form video'. NOT for written blog content (use content-production). NOT for social captions without video (use social-media-manager).
The same file is in 1 other repository
timdevai/proteus/skills/community/from-alireza/product-team/code-to-prd/skills/code-to-prd Skill
1★ repoReverse-engineer any codebase into a complete Product Requirements Document (PRD). Analyzes routes, components, state management, API integrations, and user interactions to produce business-readable documentation detailed enough for engineers or AI agents to fully reconstruct every page and endpoint. Works with frontend frameworks (React, Vue, Angular, Svelte, Next.js, Nuxt), backend frameworks (NestJS, Django, Express, FastAPI), and fullstack applications. Trigger when users mention: generate PRD, reverse-engineer requirements, code to documentation, extract product specs from code, document page logic, analyze page fields and interactions, create a functional inventory, write requirements from an existing codebase, document API endpoints, or analyze backend routes.
The same file is in 2 other repositories
timdevai/proteus/skills/community/from-alireza/project-management/skills/team-communications Skill
1★ repoWrite internal company communications — 3P updates (Progress/Plans/Problems), company-wide newsletters, FAQ roundups, incident reports, leadership updates, status reports, project updates, and general internal comms. Use this skill any time the user asks to draft, edit, or format something meant for internal audiences. Trigger on keywords like "3P", "weekly update", "newsletter", "FAQ", "internal comms", "status report", "company update", "team update", "incident report", or any request to summarize work for leadership, teammates, or the broader company. Even casual requests like "write my update" or "summarize what my team did this week" should trigger this skill.
The same file is in 5 other repositories
timdevai/proteus/skills/community/from-alireza/ra-qm-team/skills/isms-audit-expert Skill
1★ repoInformation Security Management System (ISMS) audit expert for ISO 27001 compliance verification, security control assessment, and certification support. Use when the user mentions ISO 27001, ISMS audit, Annex A controls, Statement of Applicability (SOA), gap analysis, nonconformity management, internal audit, surveillance audit, or security certification preparation. Helps review control implementation evidence, document audit findings, classify nonconformities, generate risk-based audit plans, map controls to Annex A requirements, prepare Stage 1 and Stage 2 audit documentation, and support corrective action workflows.
The same file is in 5 other repositories
timdevai/proteus/skills/community/from-alireza/ra-qm-team/skills/quality-documentation-manager Skill
1★ repoDocument control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.
The same file is in 2 other repositories
timdevai/proteus/skills/community/from-alireza/ra-qm-team/skills/regulatory-affairs-head Skill
1★ repoSenior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017/745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.
The same file is in 5 other repositories
timdevai/proteus/skills/community/from-alireza/research/litreview/skills/litreview Skill
1★ repoAcademic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER / Decomposition / hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5/10/20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.
timdevai/proteus/skills/community/from-alireza/research/research/skills/research Skill
1★ repoDefault entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — "research [topic]", "look into [topic]", "what do we know about [topic]", "investigate [topic]", "find me information on [topic]", "do some research on [topic]", "I need to understand [topic]", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.
aroyburman-codes/compound-product-management/skills/zero-slop Skill
1★ repoUse when writing any prose — enforces extreme clarity by eliminating AI writing patterns, banned words, structural cliches, and filler. Produces writing that is specific, concise, and has exactly one meaning per sentence.
pgoell/pgoell-claude-tools/plugins/databricks/skills/databricks-docs Skill
1★ repoUse when the user asks a Databricks product question (Apps, DABs, Jobs, Lakebase, Model Serving, Pipelines, Unity Catalog, SQL Warehouses, MLflow, serverless, secrets, workflows) that databricks-core's CLI cheatsheet does not answer. Resolves a canonical URL from references/docs-index.md and fetches it with the host agent's WebFetch tool.
pgoell/pgoell-claude-tools/plugins/workbench/skills/writing-plans Skill
1★ repoCollection of my personal claude skills
pgoell/pgoell-claude-tools/plugins/workbench/skills/writing-spec Skill
1★ repoUse when a design discussion is ready to be written into a spec document, before any implementation planning. Synthesizes the conversation into a spec, runs a fresh-eyes self-review subagent, and gates on user approval before handing off to writing-plans.
pgoell/pgoell-claude-tools/plugins/writing/skills/writing Skill
1★ repoDraft, review, and finish long form prose, essays, talks, newsletters, memos, and briefings.
devcsde/oatda-skills/skills/oatda-translate-audio Skill
1★ repoUse when the user wants to translate foreign-language audio into English text using OATDA's unified audio API. Supports audio translation, Whisper-style translation, and the translate_audio MCP capability.
SivaJyothiPamarthy/prompt-enhancer-pack/skills/enhance-writing Skill
1★ repoEnhance a vague writing prompt into a detailed creative brief with audience, tone, structure, and quality constraints. Use when user types /enhance-writing followed by a writing task, or asks to improve a writing-related prompt.
bfowle/spirit-island/skills/si-rules-check Skill
no license1★ repoUse BEFORE writing any spirit-chapter Opening Strategy T1/T2/T3 blocks, Tempo Profile tables, or per-turn Energy/CP/elements claims. Returns the spirit's Wiki-verified starting state + growth-option decoder + legal-play-combination calculator, so the resulting turn-by-turn prose is mechanically valid rather than hallucinated. Resolves the class of bug caught on Shadows T1 (wrote "Concealing + Mantle" when Shadows starts 0E/1CP and neither G2 branch allows that combo).
diguike/book-claude-skill/examples/ch24-graduation/changelog-generator Skill
1★ repoGenerate a changelog from git commits using conventional commit format. 从 git 提交记录生成 CHANGELOG。
kenmulford/PMSkills/skills/closeout-report Skill
no license1★ repoGenerate a Project+ style project closeout report as .docx — baseline-vs-actual for scope/schedule/cost, deliverables acceptance log, open items and known defects, contract/vendor closure, and formal sign-off block. Use whenever a user needs a closeout report, project closure document, final report, phase-end report, or handover document. Triggers include "closeout report", "project closure", "final report", "handover", "close the project", "wrap-up report". Enforces never-invent discipline for variance numbers, acceptance status, and sign-offs.
kenmulford/PMSkills/skills/lessons-learned Skill
no license1★ repoGenerate a Project+ style lessons-learned register as .docx — one entry per lesson with category, what happened, root cause, impact, recommendation, and owner. Use whenever a user needs a lessons-learned document, retrospective write-up, post-mortem, project closeout learnings, or phase-gate retrospective. Triggers include "lessons learned", "retro", "retrospective", "post-mortem", "closeout learnings", "what went well", "what went wrong". Enforces never-invent discipline for root causes, never fabricates positive lessons to balance negatives, and preserves the user's exact phrasing.
kenmulford/PMSkills/skills/status-report Skill
no license1★ repoGenerate a Project+ style weekly project status report as .docx — executive summary, RAG with trend vs prior week, accomplishments, upcoming, risks vs issues (distinguished), asks, metrics, and dependencies. Use whenever a user needs to produce a status report, weekly update, steering committee update, stakeholder update, or "where are we" document. Triggers include "status report", "weekly status", "exec update", "sponsor update", "RAG status", "this week's update". Enforces never-invent discipline and structural consistency across reporting weeks so stakeholders can scan the same sections in the same order every time.
sunilgentyala/OmniRed/skills/utility/report-writing Skill
no license1★ repoRed team and penetration test report writing methodology. Covers executive summary, technical findings format, CVSS4 scoring, remediation guidance, and evidence documentation standards.
iker-gonzalez/antwork-skills/skills/antwork-repurpose Skill
1★ repoUse when the user wants to turn ONE piece of source content into platform-native posts through Antwork — a blog post, newsletter, long LinkedIn post, podcast/video transcript, or talk reshaped into versions for each platform. Trigger on phrases like "repurpose this", "turn this blog into posts", "make this into a LinkedIn + X + Threads version", "atomize this content", "spin this into social", or pasting long-form content and asking to distribute it.
natthasath/natthasath-marketplace/plugins/language/skills/translate Skill
1★ repoA Claude Code plugin marketplace bundling 12 plugins and 54 skills across PKM, project planning, DevOps, content writing, language, design, and productivity — install with a single command and start using slash commands right away.
natthasath/natthasath-marketplace/plugins/productive/skills/activity-report Skill
1★ repoA Claude Code plugin marketplace bundling 12 plugins and 54 skills across PKM, project planning, DevOps, content writing, language, design, and productivity — install with a single command and start using slash commands right away.
natthasath/natthasath-marketplace/plugins/refactor/skills/refactor-readme Skill
1★ repoรีแฟกเตอร์ไฟล์ README.md ให้เป็น pattern มาตรฐานเดียวกัน อ่านง่าย ดู minimal แบบ open-source repo บน GitHub — จัดโครงสร้าง section, ใส่ emoji ตาม convention, เพิ่ม badges และจัด code block / table ให้ scan ได้เร็ว ใช้ skill นี้ทันทีเมื่อผู้ใช้แชร์หรือขอปรับปรุงไฟล์ README เช่น "ช่วยจัด README ให้หน่อย", "refactor readme นี้", "ทำ README ให้สวยแบบ github", "เขียน README สำหรับโปรเจกต์ FastAPI", "README ดูรก ช่วยจัดใหม่" — แม้จะแค่แปะเนื้อหา README หรือบอกแค่ชื่อโปรเจกต์ ให้ trigger skill นี้เสมอ
pricklywiggles/fractally-claude-marketplace/plugins/stack-it/skills/document-stack Skill
no license1★ repoUse this skill to document a project's tech stack so both the agents working in the repo (in CLAUDE.md) and the humans reading it (in the README) know what it's built on and how to run it. It documents from the stack-it lockfile (`.claude/stack-it/stack.yaml`) when one exists, and otherwise infers the stack by analyzing the codebase. Use it proactively whenever someone wants their stack written down, even if they don't name the files. Phrasings like "document my stack", "add a tech stack section to the readme", "write up what this project uses for Claude/agents", "put my dependencies in CLAUDE.md", "generate a tech-stack doc", "what's this project built with, document it", or running it as the final step after install-stack / scaffold-and-verify to capture the result. It writes an agent-facing stack summary (tools, pinned versions, how to build/test/lint/run, conventions, caveats) into CLAUDE.md and a human-facing Tech Stack + Getting Started into the README, both inside a refreshable managed block so re-running resyncs cleanly. It does NOT install, choose, research, or verify tools (those are install-stack, decide-stack, scaffold-and-verify), and it does not edit the stack YAML: here the YAML is read-only input. Not for writing general project prose, API docs, or code comments.
pricklywiggles/fractally-claude-marketplace/plugins/stack-it/skills/setup-stack Skill
no license1★ repoUse this skill to run the entire stack-it pipeline end to end in one guided pass. It takes a project from nothing to a working, verified, documented tech stack by running each stage skill in order (identify-stack-slots, decide-stack, install-stack, scaffold-and-verify, document-stack), resumes from wherever the project already is, optionally sets up git and commits a checkpoint after each stage, and keeps a running task list so the user can see how much is left. Use it whenever someone wants their whole stack set up rather than just one step. Phrasings like "set up my stack", "set up my whole project stack", "help me start a new project from scratch", "pick, install, and verify my stack", "take me from zero to a working project", "bootstrap my project", or "run the whole stack-it pipeline" should trigger it. It pauses only where it genuinely needs the user (their tool picks in the decide stage, an install confirmation, a stack-fault re-pick, an OK before writing docs) and handles the loop where a broken tool sends verification back to re-decide. Reach for the individual stage skills instead when the user explicitly wants only one step (only choose tools, only install, only document); this orchestrator is for the full journey. It does not reimplement the stages; it sequences them.
justhandledlabs/skills/plugins/git-commit-writer-free/skills/git-commit-writer-free Skill
1★ repoGenerate conventional commit messages from staged git changes. Use when the user asks to write commit message, generate commit, what should my commit say, or after the user runs git add and wants a commit message for staged files.
justhandledlabs/skills/plugins/markdown-table-formatter/skills/markdown-table-formatter Skill
1★ repoAlign messy Markdown tables and normalize their columns, or build a table from CSV. Use when the user says "fix my markdown table", "align this table", or "csv to markdown table".
justhandledlabs/skills/plugins/outreach-writer-free/skills/outreach-writer-free Skill
1★ repoGenerate personalized B2B cold emails from lead profiles. Use when the user says "write a cold email", "outreach to", "generate email", "draft prospecting email", or asks to create prospecting outreach from a company name, prospect name, title, and optional trigger event using PAS, MEDDIC, Challenger, or auto-detected positioning. This writes a single email; for multi-lead campaigns and Day 1/3/7 sequences from a CSV, use outreach-writer-pro.