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
stealth-engine/skills/skills/nextjs-locale-standalone Skill
4★ repoAdd locale-prefixed i18n routing to a single (non-monorepo) Next.js App Router site — a middleware/proxy that redirects `/` and any unprefixed path to `/<locale>/…` using the locale toggle's last choice (the NEXT_LOCALE cookie) then the browser's Accept-Language, a `[locale]` layout with a LocaleProvider + hooks, and a LocaleToggle that persists the choice. Use when adding bilingual/multilingual routing to a standalone Next.js site, building `/en-hk/…` `/zh-hk/…` URL namespaces, redirecting the root to a default-or-remembered locale, persisting a language switch across visits, or detecting browser language in middleware. For a monorepo that shares this logic across several apps via a workspace package, use nextjs-locale-monorepo instead.
stealth-engine/skills/skills/semantic-release-automation Skill
4★ repoAutomate versioning, changelog, tags, GitHub Releases, and npm publishing from Conventional Commits with semantic-release. Use when setting up or debugging automated releases, wiring a `.releaserc` / `release` config and the plugin pipeline (commit-analyzer, release-notes-generator, changelog, npm, git, github), making `main` cut a version on merge, generating CHANGELOG.md, publishing to npm or creating a GitHub Release per release, doing per-package releases in a monorepo (per-package tags + paths-filter matrix), pooling commits into a less-frequent release, or fixing a release that didn't fire / a CI loop from the release commit. Covers the single-package and monorepo flavors and the GitHub Actions workflow.
emaballarin/ccplugins/plugins/ccscience/skills/doc-coauthoring Skill
4★ repoGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
emaballarin/ccplugins/plugins/ccscience/skills/pdf-explore Skill
4★ repoUse this skill when the user has attached or pointed to a PDF, paper, report, or other document and the answer needs content from more than one place in it: summarize the methods or any other section, compare sections, find where a topic is discussed, read a value or label off a figure or chart, pull tables out as CSV, or find/list/extract every instance of something across the whole document (datasets, benchmarks, citations, figures, table rows, accession numbers — including appendices). It parses the PDF once in Python: pdf_pages (pages as persistent text), pdf_outline (TOC), pdf_tables (deterministic table extraction with per-table page provenance), pdf_images (embedded figures at native resolution), and prepare/assemble helpers that fan whole-doc relevance scans / per-page maps / structured extraction out over Task subagents so the pages never fill your own context. Complementary to the built-in Read(pages=...), which attaches ≤20 PDF pages as ephemeral vision dropped after one turn — reach for this skill for persistent text, whole-doc sweeps, tables, figures, and structured extraction Read can't do. For PDF creation/manipulation use reportlab/pypdf directly. Deps: pip install pypdfium2 pillow (plus pdfplumber for tables).
MarieLynneBlock/arcanum-artifex/skills/analysis/people-management/performance-review-writer Skill
no license4★ repoDraft performance reviews, self-assessments, peer reviews, and upward feedback in your own voice. Analyses your contributions, emails, and meeting history via WorkIQ, then produces honest, impact-focused drafts using the STAR format. USE FOR: write my performance review, draft self-assessment, peer review, 360 feedback, annual review, mid-year review, upward feedback, write review for colleague, performance appraisal.
MarieLynneBlock/arcanum-artifex/skills/analysis/requirements-document Skill
no license4★ repoGenerates a Business Requirements Document (BRD) or Functional Requirements Specification (FRS) skeleton populated from the user's input. It structures requirements with unique IDs, priority, source, and acceptance notes — making them traceable and reviewable.
MarieLynneBlock/arcanum-artifex/skills/analysis/write-epic Skill
no license4★ repoProduces a complete epic definition following Atlassian agile guidance. An epic captures a large initiative that is too big for a single sprint and must be decomposed into user stories.
MarieLynneBlock/arcanum-artifex/skills/analysis/write-user-story Skill
no license4★ repoProduces a complete, ready-to-groom user story following the standard Atlassian/agile format. It applies the INVEST criteria and the 3 Cs framework (Card, Conversation, Confirmation) to ensure each story is well-scoped, valuable, and testable — not just syntactically correct.
MarieLynneBlock/arcanum-artifex/skills/architecture/architecture-models-4plus1 Skill
no license4★ repoProduce Philippe Kruchten's 4+1 architectural view model for a software system, with rendered diagrams (Mermaid primary, PlantUML fallback for deployment) AND Miro RISEN prompts for each view. Use this skill whenever the user mentions "4+1", "architecture views", "architectural documentation", "logical view", "process view", "development view", "physical view", or "deployment view" — and also whenever the user asks to document system architecture, produce architecture blueprints, generate architecture diagrams, or prepare architecture content for review with non-developer stakeholders, even if they don't say "4+1" explicitly. Works with zero-input (user gives a paragraph, skill drafts a full architecture), interview mode (user has detailed context), or partial mode (user wants only one or two views). Flexes notation to audience — UML-flavoured for dev-only audiences, BPMN-style swimlanes for cross-functional audiences, simplified C4 for executives.
Create architectural decision record
MarieLynneBlock/arcanum-artifex/skills/architecture/create-architectural-decision-record Skill
no license4★ repoCreate an Architectural Decision Record (ADR) document for AI-optimised decision documentation.
MarieLynneBlock/arcanum-artifex/skills/development/api-design/openapi-to-application-code Skill
no license4★ repoGenerate a complete, production-ready application from an OpenAPI specification
MarieLynneBlock/arcanum-artifex/skills/development/java/java-docs Skill
no license4★ repoEnsure that Java types are documented with Javadoc comments and follow best practices for documentation.
MarieLynneBlock/arcanum-artifex/skills/development/test-strategy Skill
no license4★ repoProduces a test strategy document defining what to test, at which layer, with which tools, and to what coverage standard. It applies the test pyramid model, surfaces coverage gaps in existing codebases, and produces a concrete plan — not a generic "write more tests" recommendation.
MarieLynneBlock/arcanum-artifex/skills/document-production/docx Skill
no license4★ repoUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
MarieLynneBlock/arcanum-artifex/skills/document-production/xlsx Skill
no license4★ repoUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
MarieLynneBlock/arcanum-artifex/skills/documentation/documentation-writer Skill
no license4★ repoDiátaxis Documentation Expert. An expert technical writer specialising in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.
MarieLynneBlock/arcanum-artifex/skills/documentation/readme-blueprint-generator Skill
no license4★ repoIntelligent README.md generation prompt that analyses project documentation structure and creates comprehensive repository documentation. Scans .github/copilot directory files and copilot-instructions.md to extract project information, technology stack, architecture, development workflow, coding standards, and testing approaches while generating well-structured markdown documentation with proper formatting, cross-references, and developer-focused content.
MarieLynneBlock/arcanum-artifex/skills/scientific/clinical-reports Skill
no license4★ repoWrite comprehensive clinical reports including case reports (CARE guidelines), diagnostic reports (radiology/pathology/lab), clinical trial reports (ICH-E3, SAE, CSR), and patient documentation (SOAP, H&P, discharge summaries). Full support with templates, regulatory compliance (HIPAA, FDA, ICH-GCP), and validation tools.
MarieLynneBlock/arcanum-artifex/skills/scientific/markdown-mermaid-writing Skill
no license4★ repoComprehensive markdown and Mermaid diagram writing skill. Use when creating any scientific document, report, analysis, or visualisation. Establishes text-based diagrams as the default documentation standard with full style guides (markdown + mermaid), 24 diagram type references, and 9 document templates.
MarieLynneBlock/arcanum-artifex/skills/scientific/peer-review Skill
no license4★ repoStructured manuscript/grant review with checklist-based evaluation. Use when writing formal peer reviews with specific criteria methodology assessment, statistical validity, reporting standards compliance (CONSORT/STROBE), and constructive feedback. Best for actual review writing, manuscript revision. For evaluating claims/evidence quality use scientific-critical-thinking; for quantitative scoring frameworks use scholar-evaluation.
MarieLynneBlock/arcanum-artifex/skills/scientific/scientific-writing Skill
no license4★ repoCore skill for the deep research and writing tool. Write scientific manuscripts in full paragraphs (never bullet points). Use two-stage process with (1) section outlines with key points using research-lookup then (2) convert to flowing prose. IMRAD structure, citations (APA/AMA/Vancouver), figures/tables, reporting guidelines (CONSORT/STROBE/PRISMA), for research papers and journal submissions.
MarieLynneBlock/arcanum-artifex/skills/scientific/writing Skill
no license4★ repoUse this skill to create high-quality academic papers, literature reviews, grant proposals, clinical reports, and other research and scientific documents backed by comprehensive research and real, verifiable citations. Use this skill whenever the user asks for written output such as a report, paper...etc.
MarieLynneBlock/arcanum-artifex/skills/scientific/xlsx Skill
no license4★ repoUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
yaxeen/storytelling-skills/skills/storytelling-hooks Skill
4★ repoUse when writing any short-form video script, hook, opening line, or scroll-stopping content (TikTok, Reels, Shorts) for any niche or business — when the first 2 seconds must grab attention. Also the shared psychology core (six storytelling levers) that the other storytelling-suite skills reference.
yaxeen/storytelling-skills/skills/wireframe-writer Skill
4★ repoUse when planning the structure of a website page, landing page, or sales page for any niche or business — when you need a section-by-section wireframe aimed at one conversion. For critiquing an existing page, use wireframe-reviewer.
danielkinneyspears/federal-proposal-skills/skills/writing-executive-summaries Skill
4★ repoWrites the executive summary for a US Federal proposal. Use when the user needs an executive summary, an executive summary volume, a proposal summary, or the opening volume of a federal bid. Writes the executive summary as a persuasion document organized around customer hot buttons and win themes (not a table-of-contents recap) built to make the evaluator favor award before reaching the detailed volumes.
danielkinneyspears/federal-proposal-skills/skills/writing-past-performance Skill
4★ repoBuilds past performance write-ups for a US Federal proposal. Use when the user needs past performance, a past performance volume, past performance citations or references, CPARS or PPQ-based write-ups, or relevance narratives for a federal bid. Selects references for recency, relevancy, and quality; maps each prior contract to the current requirement on the dimensions Section M evaluates; and substantiates performance quality with evidence.
n-n-code/n-n-code-skills/.agents/skills/documenter-coauthoring Skill
4★ repoCompanion overlay for multi-round collaborative drafting of large specs, proposals, decision docs, and similar documents. Use when the workflow needs structured context gathering, explicit outline approval, section-by-section iteration, and reader-testing rather than a direct documentation pass.
n-n-code/n-n-code-skills/.agents/skills/documenter Skill
4★ repoBaseline overlay for substantial documentation authoring or restructuring: README, specs, ADRs, tutorials, how-to guides, reference docs, explanations, API docs, code comments, changelogs, and agent-facing docs. Use when the agent should classify doc type, ground claims in repo truth, and validate examples before finishing.
n-n-code/n-n-code-skills/.agents/skills/prompt-engineering Skill
4★ repoPrompt engineering workflow for designing, rewriting, debugging, evaluating, and optimizing LLM prompts, system prompts, developer prompts, few-shot examples, structured-output instructions, tool-use prompts, and prompt eval cases. Use when prompt behavior, reliability, safety, cost, latency, or model fit is the main task. Do not use for generic prose editing, model selection alone, or ordinary documentation work with no prompt artifact.
01clauding/claude-seo-skill/skills/seo-report Skill
4★ repoSEO reporting and analytics dashboard generation. Creates weekly digests, monthly performance reports, quarterly strategy reviews, and real-time dashboard templates. Use when user says "SEO report", "weekly digest", "monthly report", "dashboard", "SEO metrics", "performance summary".
lyymuwu/TokTrans/skills/token-trans Skill
4★ repoExplicit opt-in only. Translate multilingual requests through lightweight subagents, work normally, translate only the final answer back.
alexpialetski/doccraft/.claude/skills/doccraft-queue-audit Skill
4★ repoReconcile the dependency graph, pick-next queue, and backlog status across docs/stories/, docs/queue.md, and docs/backlog.md. Use after adding or editing a story (especially one with depends_on), after reshuffling priorities, or when the user asks "what can I work on next", "what's unblocked", "sanity-check the queue", "check my story dependencies", "fix the queue order", or "what parallel work is ready". In Agent mode (the tool can write files), apply objective mechanical fixes in the same turn and report what changed; in Ask / read-only mode, emit a proposal instead. Stop and report — never guess — on directed cycles, unknown depends_on ids, duplicate ids, or ambiguous editorial reorders.
alexpialetski/doccraft/.claude/skills/doccraft-session-wrap Skill
4★ repoAfter a design, research, business, or prioritisation thread, evaluate whether the conversation produced durable insight worth capturing in docs/, then propose only the artifacts that are clearly justified (ADR, research note, reference doc, business update, story, backlog/queue edit). Use when the user says "wrap this session", "propose docs artifacts", "what should we capture", "summarize this into docs", "end-of-session", or similar close-out phrasing. If nothing warrants capture, say so in one sentence and stop. Never write files unless the user explicitly asks to create or update them in the same turn — propose drafts only.
alexpialetski/doccraft/.claude/skills/doccraft-story Skill
4★ repoAuthor or update product stories (a.k.a. planning docs, backlog items, tickets, specs) as Markdown under docs/stories/ with a YAML frontmatter contract (id, status, impact, urgency, depends_on, tags, openspec). Use this whenever the user is creating a story, reprioritising work, writing acceptance criteria, linking a story to OpenSpec or an ADR, or editing anything under docs/stories/ — even if they call it a spec, ticket, backlog row, or planning doc.
alexpialetski/doccraft/templates/skills/doccraft-queue-audit Skill
4★ repoReconcile the dependency graph, pick-next queue, and backlog status across {{DOCS_DIR}}/stories/, {{DOCS_DIR}}/queue.md, and {{DOCS_DIR}}/backlog.md. Use after adding or editing a story (especially one with depends_on), after reshuffling priorities, or when the user asks "what can I work on next", "what's unblocked", "sanity-check the queue", "check my story dependencies", "fix the queue order", or "what parallel work is ready". In Agent mode (the tool can write files), apply objective mechanical fixes in the same turn and report what changed; in Ask / read-only mode, emit a proposal instead. Stop and report — never guess — on directed cycles, unknown depends_on ids, duplicate ids, or ambiguous editorial reorders.
alexpialetski/doccraft/templates/skills/doccraft-session-wrap Skill
4★ repoAfter a design, research, business, or prioritisation thread, evaluate whether the conversation produced durable insight worth capturing in {{DOCS_DIR}}/, then propose only the artifacts that are clearly justified (ADR, research note, reference doc, business update, story, backlog/queue edit). Use when the user says "wrap this session", "propose docs artifacts", "what should we capture", "summarize this into docs", "end-of-session", or similar close-out phrasing. If nothing warrants capture, say so in one sentence and stop. Never write files unless the user explicitly asks to create or update them in the same turn — propose drafts only.
alexpialetski/doccraft/templates/skills/doccraft-story Skill
4★ repoAuthor or update product stories (a.k.a. planning docs, backlog items, tickets, specs) as Markdown under {{DOCS_DIR}}/stories/ with a YAML frontmatter contract (id, status, impact, urgency, depends_on, tags, openspec). Use this whenever the user is creating a story, reprioritising work, writing acceptance criteria, linking a story to OpenSpec or an ADR, or editing anything under {{DOCS_DIR}}/stories/ — even if they call it a spec, ticket, backlog row, or planning doc.
Amalia6767/curator-skills/skills/tender-booklet-writing Skill
4★ repo为投标方案册子(画册)撰写专业的页面说明文档,用于汇报讲解、甲方阅读理解及后期方案沟通
roodlicht/accans-sec-skills/skills/ir-runbook Skill
no license4★ repoIncident Response runbook — NIST SP 800-61 phases (Preparation/Detection-Analysis/Containment-Eradication-Recovery/Lessons-Learned), per-scenario playbooks (ransomware, BEC, data exfil, credential compromise, cloud), regulatory reporting (NIS2 24h/72h, AVG breach 72h, DORA), comms templates, and post-incident review.
celticht32/Couchbase-Skills-for-Claude.ai/skills/couchbase/couchbase-coding-standards Skill
4★ repoApply coding standards and a style guide for writing production application code against Couchbase, combining general software-engineering best practices (naming, functions, error handling, testing, docstrings, version control, code review, secrets hygiene) with Couchbase-specific conventions (SDK idioms, document-key naming, exception and retry handling, durability, parameterized SQL++, connection lifecycle). Use whenever the user asks about coding standards, code style, a style guide, clean code, naming conventions, structuring Couchbase application code, idiomatic SDK usage, how to write or review Couchbase code, code-review checklists, linting, formatting, testing Couchbase code, or best practices for writing Couchbase apps. Distinct from couchbase-app-integration (SDK mechanics: pooling, durability, scan consistency) and couchbase-data-modeling (document design) — this is the how-to-write-and-review-the-code layer on top of them. Use proactively when reviewing or authoring code that touches Couchbase.
celticht32/Couchbase-Skills-for-Claude.ai/skills/couchbase/couchbase-transactions Skill
4★ repoDesign and implement Couchbase distributed ACID transactions across multiple documents. Use whenever the user asks about transactions, multi-document atomicity, ACID, transaction library, TransactionAttemptContext, commit, rollback, transaction retry, Active Transaction Records (ATRs), transaction expiry, transaction lost write, transaction conflict, transaction performance, cb_transaction_run, or 'how do I atomically update multiple documents.' Distinct from couchbase-app-integration (which covers single-document KV ops, subdocument ops, and has a brief transactions overview) — this skill is for users who need the full depth: designing around transactions, understanding the two-phase commit mechanics, debugging failures, and tuning performance. Use proactively when the user has a use case requiring consistency across multiple documents.
reaviz/skills/reachat/markdown Skill
no license4★ repoAI Skills for Reaviz Projects
TenWalk/ieee-skills/ieee-skills-claude/skills/ieee-letter Skill
4★ repoWrite or compress an IEEE communications LETTER for WCL (IEEE Wireless Communications Letters) or CL (IEEE Communications Letters): a single-contribution paper with a compressed introduction, no standalone related-work section, one system model, one core result (an algorithm OR a closed-form expression), and a tight simulation section under the current WCL/CL page budget. Use this whenever the target is a letter rather than a transactions paper — "write a WCL letter", "turn this into a letter", "我的论文要投WCL/CL", "压缩成letter", "写一篇通信快报", "letter写不下了怎么删", "cut my letter to fit", EDICS selection, and the WCL/CL submission checklist. For full transactions papers (JSAC/TWC/TCOM) use ieee-writing; for the results narrative use ieee-writing + ieee-experiments; for figures use ieee-figure. Bilingual: turns Chinese notes into a submission-ready English letter plus short Chinese explanations.
TenWalk/ieee-skills/ieee-skills-claude/skills/ieee-methods Skill
4★ repoWrite or audit IEEE communications Methods/System Model/Algorithm details for reproducibility: notation tables, simulation-parameter tables, solver settings, random seeds, channel/model assumptions, algorithm boxes, convergence statements, and complexity analysis. Use this when the user asks for "methods", "reproducibility checklist", "notation table", "complexity analysis", "algorithm box", "simulation parameters table", "复现性", "符号表", "复杂度", or wants a JSAC/TWC/TCOM/WCL/CL methods section checked for enough detail to reproduce. For drafting the broader paper argument use ieee-writing; for deciding which experiments to run use ieee-experiments.
TenWalk/ieee-skills/ieee-skills-claude/skills/ieee-polishing Skill
4★ repoPolish academic prose to IEEE-journal style at the sentence level — clarity, sentence length, section-appropriate tense, calibrated hedging, US English, acronym discipline, numbered-citation phrasing, and unit/number formatting. Also translate Chinese drafts into IEEE-style English. Use this whenever the user wants to "polish", "proofread", "improve the English", "make it publishable / native", "fix the grammar", "润色", "改成地道英文", "改成投稿级" on existing text. Tuned for IEEE communications papers (per-section tense for system model / problem formulation / proposed solution / numerical results). For building or restructuring the argument and sections, use ieee-writing instead.
TenWalk/ieee-skills/ieee-skills-claude/skills/ieee-response Skill
4★ repoDraft the two letters an IEEE submission needs — the point-by-point response to reviewers and the cover letter to the editor — so every comment is answered, every change is traceable to the revised manuscript, and the tone stays cooperative without conceding more than the evidence requires. Use this whenever the user is replying to a review or submitting a manuscript: "respond to reviewers", "rebuttal letter", "reviewer 2 says...", "write a cover letter", "我要回复审稿意见", "审稿回复", "投稿信", "怎么回复 reviewer". For changing the manuscript text the response promises, hand to ieee-writing/ieee-polishing; for new simulations a reviewer demands, hand to ieee-experiments.
TenWalk/ieee-skills/ieee-skills-claude/skills/ieee-writing Skill
4★ repoDraft, restructure, or plan IEEE communications-journal manuscript sections (JSAC, TWC, TC/TCOM, WCL, CL): abstract + Index Terms, introduction with a contributions list, related work, system model, problem formulation, proposed solution/algorithm, performance analysis (theorems/proofs), numerical results, discussion, conclusion, title — from author claims, derivations, simulation results, figures, notes, or Chinese drafts. Use this whenever the user wants to WRITE or REBUILD comms paper text: "help me write my paper", "draft the introduction", "写系统模型", "问题建模", "restructure this section", "把我的中文草稿写成英文论文", "写贡献点", "改写算法部分" — not merely fix grammar (use ieee-polishing). For a WCL/CL letter, use ieee-letter. Bilingual: turns Chinese notes into submission-ready English plus short Chinese explanations.
TenWalk/ieee-skills/ieee-skills-codex/skills/ieee-letter Skill
4★ repoWrite or compress an IEEE communications LETTER for WCL (IEEE Wireless Communications Letters) or CL (IEEE Communications Letters): a single-contribution paper with a compressed introduction, no standalone related-work section, one system model, one core result (an algorithm OR a closed-form expression), and a tight simulation section under the current WCL/CL page budget. Use this whenever the target is a letter rather than a transactions paper — "write a WCL letter", "turn this into a letter", "我的论文要投WCL/CL", "压缩成letter", "写一篇通信快报", "letter写不下了怎么删", "cut my letter to fit", EDICS selection, and the WCL/CL submission checklist. For full transactions papers (JSAC/TWC/TCOM) use ieee-writing; for the results narrative use ieee-writing + ieee-experiments; for figures use ieee-figure. Bilingual: turns Chinese notes into a submission-ready English letter plus short Chinese explanations.
TenWalk/ieee-skills/ieee-skills-codex/skills/ieee-methods Skill
4★ repoWrite or audit IEEE communications Methods/System Model/Algorithm details for reproducibility: notation tables, simulation-parameter tables, solver settings, random seeds, channel/model assumptions, algorithm boxes, convergence statements, and complexity analysis. Use this when the user asks for "methods", "reproducibility checklist", "notation table", "complexity analysis", "algorithm box", "simulation parameters table", "复现性", "符号表", "复杂度", or wants a JSAC/TWC/TCOM/WCL/CL methods section checked for enough detail to reproduce. For drafting the broader paper argument use ieee-writing; for deciding which experiments to run use ieee-experiments.
TenWalk/ieee-skills/ieee-skills-codex/skills/ieee-polishing Skill
4★ repoPolish academic prose to IEEE-journal style at the sentence level — clarity, sentence length, section-appropriate tense, calibrated hedging, US English, acronym discipline, numbered-citation phrasing, and unit/number formatting. Also translate Chinese drafts into IEEE-style English. Use this whenever the user wants to "polish", "proofread", "improve the English", "make it publishable / native", "fix the grammar", "润色", "改成地道英文", "改成投稿级" on existing text. Tuned for IEEE communications papers (per-section tense for system model / problem formulation / proposed solution / numerical results). For building or restructuring the argument and sections, use ieee-writing instead.
TenWalk/ieee-skills/ieee-skills-codex/skills/ieee-response Skill
4★ repoDraft the two letters an IEEE submission needs — the point-by-point response to reviewers and the cover letter to the editor — so every comment is answered, every change is traceable to the revised manuscript, and the tone stays cooperative without conceding more than the evidence requires. Use this whenever the user is replying to a review or submitting a manuscript: "respond to reviewers", "rebuttal letter", "reviewer 2 says...", "write a cover letter", "我要回复审稿意见", "审稿回复", "投稿信", "怎么回复 reviewer". For changing the manuscript text the response promises, hand to ieee-writing/ieee-polishing; for new simulations a reviewer demands, hand to ieee-experiments.
TenWalk/ieee-skills/ieee-skills-codex/skills/ieee-writing Skill
4★ repoDraft, restructure, or plan IEEE communications-journal manuscript sections (JSAC, TWC, TC/TCOM, WCL, CL): abstract + Index Terms, introduction with a contributions list, related work, system model, problem formulation, proposed solution/algorithm, performance analysis (theorems/proofs), numerical results, discussion, conclusion, title — from author claims, derivations, simulation results, figures, notes, or Chinese drafts. Use this whenever the user wants to WRITE or REBUILD comms paper text: "help me write my paper", "draft the introduction", "写系统模型", "问题建模", "restructure this section", "把我的中文草稿写成英文论文", "写贡献点", "改写算法部分" — not merely fix grammar (use ieee-polishing). For a WCL/CL letter, use ieee-letter. Bilingual: turns Chinese notes into submission-ready English plus short Chinese explanations.
sp-daewoon/chronicle/skills/index Skill
4★ repoGive your project one beautiful front door instead of scattered docs. Use when generating or refreshing a single navigation hub that links your ADRs, changelog and releases. Outputs Markdown or a self-contained HTML page based on your config, and adapts to any repo via config or auto-detection.
DjordjeMojsilovic/Djordjes-Claude-Setup/skill-seekers Skill
no license4★ repoConverts any documentation website, GitHub repo, API reference, or technical resource into a ready-to-upload Claude skill (SKILL.md file). Use when the user wants to turn documentation into a persistent skill — e.g. "make a skill from the FastAPI docs", "convert the Anthropic API reference into a skill", "I want Claude to know the Supabase docs", "turn this GitHub README into a skill". Analyzes the source, extracts the most useful patterns and procedures, and outputs a complete SKILL.md file.
warpirate/linkedin-maxxing/plugins/linkedin-maxxing/skills/find-ideas Skill
no license4★ repoUse when user wants to post on LinkedIn but has no concrete idea, has a vague topic that needs a sharper angle, or uploads a work artifact (PR description, meeting note, internal doc) and asks what to post about it. Trigger phrases include "help me come up with a LinkedIn post," "what should I write about," "I want to post something but I don't know what," "give me ideas for LinkedIn," "I have an idea but I don't know the angle." Run BEFORE any writing skill if user has not given a concrete, specific angle.
warpirate/linkedin-maxxing/plugins/linkedin-maxxing/skills/rewrite-profile Skill
no license4★ repoUse when user wants to improve their LinkedIn profile, is preparing for a job search, has changed roles, is positioning for a new audience (founder, consultant, recruiter), or has not touched their profile in over a year. Trigger phrases include "rewrite my LinkedIn profile," "optimize my profile," "fix my headline," "my About section sucks," "I want my profile to position me as X." Run audit-profile first if not already done.
warpirate/linkedin-maxxing/plugins/linkedin-maxxing/skills/write-comment Skill
no license4★ repoUse when user wants to leave a substantive comment on someone else's LinkedIn post, reply to comments on their own posts, get a batch of comment templates for engaging with their network, or use commenting as their primary growth strategy. Trigger phrases include "write a comment on this post," "how should I reply to this," "help me engage with my feed," or when user pastes a post URL or text and asks what to say.
warpirate/linkedin-maxxing/plugins/linkedin-maxxing/skills/write-dm Skill
no license4★ repoUse when user wants to send a LinkedIn message to one specific person rather than post publicly: a connection request note, cold outreach, warm intro reply, follow-up after no response, or reply to someone who DM'd them. Trigger phrases include "write a LinkedIn DM," "write a connection request," "I need to message [person]," "follow up on the message I sent," "reply to this person."
warpirate/linkedin-maxxing/plugins/linkedin-maxxing/skills/write-hook Skill
no license4★ repoUse when user has a LinkedIn post body but a weak opening, wants to A/B several hook angles before drafting the full post, or their existing post is not earning "see more" expand clicks. Trigger phrases include "write a hook," "fix my hook," "give me 5 hook variants," "the first line of my post is weak," "rewrite the opening." Hook must fit the 210-character LinkedIn fold.