agentsclimarketplace

Docs & writing

16,632 rows, by stacks then stars

3,030 of these skill files have been read, by 1,951 distinct authors, and what they tell an agent counted. What Docs & writing authors agree on, and what they forbid

  • Content quality editor

    risadams/ink-and-agency/skills/business-product/content-quality-editor Skill

    no license2★ repo

    Use this skill before publishing any AI-generated content — blog posts, READMEs, release notes, commit messages, PR descriptions, documentation, or social posts. Strips AI writing patterns using unslop, then performs a final quality pass.

  • Issue draft release notes

    risadams/ink-and-agency/skills/business-product/issue-draft-release-notes Skill

    no license2★ repo

    Draft a customer-facing release note for a Jira ticket from its context and linked merge requests. Read-only unless the user opts in to publish. Use when the user says "draft release notes", "write a release note", "release note for [TICKET-KEY]", or invokes /issue-draft-release-notes.

  • Issue dup find

    risadams/ink-and-agency/skills/business-product/issue-dup-find Skill

    no license2★ repo

    Scan all open issues in a Jira project and identify likely duplicates using semantic comparison. Produces a markdown report listing each suspected duplicate pair with a probability score and reasoning. Read-only — never modifies, links, or transitions tickets. Default project key is read from memory (`reference_jira_default_project.md`); accepts an override project key. Use when user says "find duplicates", "duplicate check", "dedupe issues", "find duplicate tickets", or invokes /issue-dup-find with or without a project key.

  • Technical writer

    risadams/ink-and-agency/skills/business-product/technical-writer Skill

    no license2★ repo

    Use when you need to create, improve, or maintain technical documentation including API references, user guides, SDK documentation, and getting-started guides.

  • Documentation engineer

    risadams/ink-and-agency/skills/developer-experience/documentation-engineer Skill

    no license2★ repo

    Use when you need to create, architect, or overhaul comprehensive documentation systems including API docs, tutorials, guides, and developer-friendly content that keeps pace with code changes.

  • Readme generator

    risadams/ink-and-agency/skills/developer-experience/readme-generator Skill

    no license2★ repo

    Use when you need a maintainer-ready README built from exact repository reality, with deep codebase scanning, zero hallucination, and optional git commit/push only when explicitly requested.

  • Defuddle

    risadams/ink-and-agency/skills/meta-orchestration/defuddle Skill

    no license2★ repo

    Extract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web page. Do NOT use for URLs ending in .md — those are already markdown, use WebFetch directly.

  • Research

    risadams/ink-and-agency/skills/meta-orchestration/research Skill

    no license2★ repo

    Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

  • Obsidian markdown

    risadams/ink-and-agency/skills/obsidian/obsidian-markdown Skill

    no license2★ repo

    Create 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.

  • Ai writing auditor

    risadams/ink-and-agency/skills/quality-security/ai-writing-auditor Skill

    no license2★ repo

    Use when you need to audit content for AI writing patterns and rewrite text to remove them.

  • Grill with docs

    risadams/ink-and-agency/skills/research-analysis/grill-with-docs Skill

    no license2★ repo

    Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

  • Daily standup prep

    risadams/ink-and-agency/skills/scrum-sprint/daily-standup-prep Skill

    no license2★ repo

    Generate a per-team standup markdown report by gathering activity over the last N days from Jira, GitLab, Confluence, and a local Git repo. Maps activity to team members from a roster CSV, renders a Mermaid kanban + randomized talking order, captures a `daily`-tagged sprint snapshot, and runs a clarity-council (infographics-expert burndown chart + statistics-expert forecast + scrum-master suggestions) for sprint pulse. Writes one file per team into the Obsidian vault. Use when the user says "daily standup prep", "standup report", "generate standup", "scrum prep", or invokes /daily-standup-prep.

  • Sprint plan

    risadams/ink-and-agency/skills/scrum-sprint/sprint-plan Skill

    no license2★ repo

    Convert the start-of-sprint canvas into a planning markdown report. Use when the user says "sprint plan", "sprint planning report", "convert sprint plan to markdown", or invokes /sprint-plan. Produces a sprint-goal summary, committed scope (carry-over vs new commit), capacity vs commitment with WIP-saturation risk, observations, and risks; auto-runs a clarity-council pass and writes a date-stamped report with a `-latest` pointer.

  • Sprint review

    risadams/ink-and-agency/skills/scrum-sprint/sprint-review Skill

    no license2★ repo

    End-of-sprint stakeholder report comparing the start.canvas (planning) to end.canvas (sprint close). Produces a markdown report fitting the standard SM template (Scrum Master, Sprint Accomplishments, Feature Demos, Customer Meetings, Status, Sprint Commitment, PI Confidence, Impediments). Applies team-specific overhead, wedge-balancing, and in-review overhead rules. Auto-runs a clarity-council session (statistics-expert + scrum-master + product-owner) for accomplishments/status/impediments synthesis. Use when user says "sprint review", "end of sprint report", "sprint stakeholder report", "sprint close report", or invokes /sprint-review.

  • Sprint sos report

    risadams/ink-and-agency/skills/scrum-sprint/sprint-sos-report Skill

    no license2★ repo

    End-of-week scrum-of-scrums report comparing two sprint snapshots and surfacing key findings, observations, trouble areas, and trends. Auto-detects which two snapshots to compare (most-recent two by snapshot_at) with `--from`/`--to` overrides for re-planning churn comparisons (e.g. compare `week 1` vs a mid-week `week 1.5`). Applies team-specific overhead, wedge-balancing, and in-review overhead rules from `_team-rules.md`. Auto-runs a clarity-council session (statistics-expert + scrum-master + product-owner). Use when user says "scrum of scrums", "sos report", "weekly sprint report", "sprint progress report", or invokes /sprint-sos-report.

  • Api documenter

    risadams/ink-and-agency/skills/specialized-domains/api-documenter Skill

    no license2★ repo

    Use when creating or improving API documentation, writing OpenAPI specifications, building interactive documentation portals, or generating code examples for APIs.

  • Writing apology calibrator

    risadams/ink-and-agency/skills/writing/writing-apology-calibrator Skill

    no license2★ repo

    Drafted apology in, calibrated apology out. Strips reflexive self-blame and over-apologizing that masking trains in, while keeping genuine accountability for things the user actually owes. Use when user says "calibrate this apology", "am I over-apologizing", "apology check", "did I say sorry too much", "is this too much", or invokes /writing-apology-calibrator.

  • Writing beats

    risadams/ink-and-agency/skills/writing/writing-beats Skill

    no license2★ repo

    Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

  • Writing cold open

    risadams/ink-and-agency/skills/writing/writing-cold-open Skill

    no license2★ repo

    Generates the first sentence of a message or email when you can't get past the blank cursor. Offers 2-3 openings matched to the relationship and goal, then steps out — you write the rest. Use when user says "cold open", "help me start this message", "how do I begin", "stuck on opening", "first sentence", or invokes /writing-cold-open.

  • Writing draft article

    risadams/ink-and-agency/skills/writing/writing-draft-article Skill

    no license2★ repo

    Guide the user from raw idea, topic, or draft to a finished, polished article through relentless questioning and iterative writing. Supports blog posts, social media posts, and long-form prose. Delegates to sibling skills (writing-humanize, writing-shape, writing-beats, writing-fragments) when appropriate. Use when the user wants to write something from scratch and have it completed.

  • Writing fragments

    risadams/ink-and-agency/skills/writing/writing-fragments Skill

    no license2★ repo

    Mine the user for raw writing fragments — claims, vignettes, sharp sentences, half- thoughts — and append them to one document as material for a future article. Use when the user wants to develop ideas before imposing structure, or mentions "fragments" or "raw material".

  • Writing humanize

    risadams/ink-and-agency/skills/writing/writing-humanize Skill

    no license2★ repo

    Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, and filler phrases.

  • Writing shape

    risadams/ink-and-agency/skills/writing/writing-shape Skill

    no license2★ repo

    Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.

  • Writing social script

    risadams/ink-and-agency/skills/writing/writing-social-script Skill

    no license2★ repo

    Generate a script for a specific social scenario you're dreading: declining a meeting, asking for a deadline extension, following up on silence, leaving a party early, asking for help, setting a boundary. Offers 2-3 phrasings from direct to softened. Use when user says "script for", "help me say", "how do I tell them", "I need to ask", "I need to decline", "social script", or invokes /writing-social-script.

  • Writing tone check

    risadams/ink-and-agency/skills/writing/writing-tone-check Skill

    no license2★ repo

    Reverse decoder — paste a draft message and get a read on how it will land before you send. Flags blunt, cold, accidentally passive-aggressive, or over-apologetic patterns. Use when user says "tone check", "how does this sound", "before I send this", "will this land okay", "check this draft", or invokes /writing-tone-check.

  • No ai traces

    26zl/universal-agent-skills/skills/no-ai-traces Skill

    2★ repo

    Keep delivered work free of AI self-reference, with no Co-Authored-By trailers or generated-with footers in commits and pull requests, and no comments, documentation, or changelog entries that narrate AI involvement, prompts, or the editing session. Use when writing commits, merge or squash messages, pull requests, release notes, changelogs, code comments, or documentation; do not use to bypass a policy that explicitly requires AI disclosure.

  • Secret hygiene

    26zl/universal-agent-skills/skills/secret-hygiene Skill

    2★ repo

    Never write, echo, or commit secret values such as API keys, tokens, passwords, or private keys; reference them through environment variables or a secret manager, and report discovered secrets without reproducing the value. Use when writing code, tests, configuration, documentation, logs, or shell commands that touch credentials; do not use to weaken cryptographic material handling that the product itself must perform.

  • Publish ready

    batteryshark/skill-tap/skills/development/publish-ready Skill

    2★ repo

    Prepare a repository for public release by removing development residue and dead paths, consolidating documentation, tightening generated-sounding prose, checking for secrets and local-machine references, and proving that surviving quickstarts and checks work. Use before open-sourcing, sharing, handing off, demonstrating, or releasing a project.

  • Work product audit

    batteryshark/skill-tap/skills/development/work-product-audit Skill

    2★ repo

    Audit repositories and public documentation for internal notes, defensive explanations, unexplained assertions, stale project residue, hidden assumptions, and generated-sounding meta commentary. Use when scanning launch material, cleaning public prose, or deciding which reasoning belongs outside the finished deliverable.

  • Project tracker

    batteryshark/skill-tap/skills/productivity/project-tracker Skill

    2★ repo

    Create or update compact durable Markdown memory for long-running projects, including current objective, status, workstreams, attempts, decisions, important artifacts, open questions, and next actions. Use when capturing project state, reconstructing context, preparing a handoff, recording a pivot, or making future sessions resumable across engineering, research, automation, writing, and other multi-session work.

  • Local ocr vlm

    batteryshark/skill-tap/skills/utilities/local-ocr-vlm Skill

    2★ repo

    Run OCR on local images through an OpenAI-compatible local vision endpoint (LM Studio, vLLM/vmlx). Use when you need offline, on-machine document OCR into markdown, including batch directory processing, without sending images to a hosted service.

  • Autonovel prose review

    DukeTwoCan/autonovel-agent-skills/skills/creative/autonovel-prose-review Skill

    2★ repo

    Autonovel Phase 3b.2 — user-triggered targeted prose review. Takes a scope (e.g. 'ch 7', 'ch 7-10', 'act 2', 'the heist arc') and emits line-level critique for that scope only. NOT auto-invoked by the pipeline. Designed for the user to sit with the agent and iterate on prose quality chapter-by-chapter or arc-by-arc. Conversational: the agent presents notes and asks the user which to apply rather than auto-fixing.

  • Autonovel

    DukeTwoCan/autonovel-agent-skills/skills/creative/autonovel Skill

    2★ repo

    Entry point for the autonovel pipeline — multi-phase novel-writing skill pack. Use when the user wants to write a novel from a seed concept, resume an in-progress novel, or learn what the pipeline does. Dispatches to phase-specific skills (foundation, drafting, revision, consistency-pass, prose-review, export) based on state.json. Reads $AUTONOVEL_WORKSPACE/$NOVEL_SLUG/state.json to decide which phase is current.

  • Competitor teardown

    Abhillashjadhav/PM-agent-OS/.claude/skills/competitor-teardown Skill

    no license2★ repo

    Discovery-stage skill: turns material about a competitor's product — pricing pages, docs, changelogs, screenshots, customer reports — into a structured teardown where every claim is marked observed or inferred. Use when the user names a competitor product and asks for a teardown, competitive analysis, or comparison — 'tear down X', 'how does our Y compare to theirs', 'what is X doing with their pricing' — or when /pm routes such a request here. Do NOT use to write positioning or battlecards (Strategy stage), to scrape or collect the competitor data itself, for company-culture questions, or when no competitor material or product is identified — with nothing to observe it asks for material rather than inventing findings.

  • Strategy review

    Abhillashjadhav/PM-agent-OS/.claude/skills/strategy-review Skill

    no license2★ repo

    Strategy-stage skill: pressure-tests a strategy document — every weakness it raises must cite the specific line it attacks. Use when the user provides their own strategy doc, positioning memo, or plan and asks for it to be stress-tested — 'pressure-test this strategy', 'tear it apart before the board does', 'red-team this memo', 'what's weak in this one-pager' — or when /pm routes such a request here. Do NOT use to author a strategy from scratch (there must be a doc to attack), to review PRs (/pr-review), to analyze a competitor's strategy (competitor-teardown), or for knowledge questions about strategy frameworks.

  • Linkedin newsletter scraper

    sam6dvpte34/lead-generation-skill/skills/linkedin-newsletter-scraper Skill

    no license2★ repo

    Collect newsletter data from LinkedIn — newsletter name, author, subscriber count, recent issues. Use when the user wants to prospect newsletter audiences or research content creators.

  • Website newsletter page scraper

    sam6dvpte34/lead-generation-skill/skills/website-newsletter-page-scraper Skill

    no license2★ repo

    Collect newsletter signals from website pages — company name, newsletter title, topic, contact, signup URL. Use when the user wants to identify companies with newsletter audiences.

  • Test discipline

    niksavis/basicly/.agents/skills/test-discipline Skill

    2★ repo

    Write isolated order-independent automated tests that assert on observable behavior rather than private internals. Use when writing reviewing or debugging any test (unit integration or end-to-end) in any language especially when tests share fixtures touch global or filesystem state flake depending on run order or reach into implementation details.

  • Release process

    niksavis/basicly/.claude/skills/release-process Skill

    2★ repo

    Prepare and publish semantic version releases using this repository's changelog-driven workflow. Use this when asked to cut a release, update CHANGELOG.md for a tag, review release notes quality, create/push tags, or verify GitHub release status.

  • Doc triage

    jamestexas/agents/skills/doc-triage Skill

    2★ repo

    Curated library of Claude Code subagents and skills (23 agents, 20 skills) with an idempotent installer that symlinks into ~/.claude. Frontmatter-driven; spec-compliant with Anthropic and Gemini schemas.

  • Readme restructure

    jamestexas/agents/skills/readme-restructure Skill

    2★ repo

    Curated library of Claude Code subagents and skills (23 agents, 20 skills) with an idempotent installer that symlinks into ~/.claude. Frontmatter-driven; spec-compliant with Anthropic and Gemini schemas.

  • Workflow audit

    jamestexas/agents/skills/workflow-audit Skill

    2★ repo

    Curated library of Claude Code subagents and skills (23 agents, 20 skills) with an idempotent installer that symlinks into ~/.claude. Frontmatter-driven; spec-compliant with Anthropic and Gemini schemas.

  • Project workflow

    tikhomirovv/agents-knowledge/skills/project-workflow Skill

    no license2★ repo

    Universal project workflows for software repos — brainstorm ideas, maintain docs, research and file backlog issues, implement with PR/MR. Works with GitHub and GitLab. Use when discussing features, exploring the codebase, creating or updating issues, writing documentation, or implementing tracked work.

  • Release runbook

    nibzard/skills/skills/release-runbook Skill

    2★ repo

    Universal release workflow: detect project type, init versioning if needed, run tests, bump version, tag, push, and create GitHub release. Works with Python, Go, Node.js, Rust, Java, .NET, Ruby, PHP, and multi-language projects.

  • Release runbook

    nibzard/skills/skills/release-runbook/skills/release-runbook Skill

    2★ repo

    Universal release workflow: detect project type, init versioning if needed, run tests, bump version, tag, push, and create GitHub release. Works with Python, Go, Node.js, Rust, Java, .NET, Ruby, PHP, and multi-language projects.

    The same file is in 2 other repositories

  • Write skills

    avivsinai/skills-marketplace/plugins/skill-authoring/skills/write-skills Skill

    2★ repo

    Create or revise agent skills. Use when adding a new skill file, renaming a skill, simplifying an existing skill, improving trigger descriptions, or deciding what belongs in a skill versus references, scripts, assets, or ordinary docs. This is the judgment layer — authoring principles and failure modes for manual, principle-level work; prefer skill-creator when the user wants end-to-end interactive creation with generated test harnesses or quantitative description optimization.

    The same file is in 1 other repository

  • Ontology technical plan writer

    Mokee04/ontology_research/ontology-technical-plan-writer Skill

    no license2★ repo

    Draft or refine a technical planning document template for an ontology project. Use when the user wants a technical proposal, planning brief, or reusable template that connects scope, competency questions, standards reuse, modeling approach, validation, governance, and execution phases without drifting into a business-only pitch.

  • Ielts writing task1 examiner

    Bosh-Kuo/awesome-agent-toolkit/examples/.agents/skills/ielts-writing-task1-examiner Skill

    no license2★ repo

    IELTS Writing Task 1 examiner — evaluates, corrects, and rephrases Academic or General Training Task 1 essays. Use when the user pastes an IELTS Writing Task 1 question and their essay and wants: (1) band scores on each official criterion (TA, CC, LR, GRA) plus an overall band score, (2) inline Markdown corrections on the original essay (strikethrough errors, inline code for corrections), (3) detailed correction analysis, (4) a Band 7–9 model answer with selective HTML highlighting, (5) model answer analysis, and (6) a topic language bank covering chart/letter collocations, useful phrasal verbs where natural, high-band vocabulary, and synonyms. Triggers on phrases like "批改 Task 1", "evaluate my IELTS writing", "IELTS Task 1 correction", or any submission of an IELTS Task 1 prompt + essay.

  • Ielts writing task2 examiner

    Bosh-Kuo/awesome-agent-toolkit/examples/.agents/skills/ielts-writing-task2-examiner Skill

    no license2★ repo

    IELTS Writing Task 2 examiner — evaluates, corrects, and rephrases Academic or General Training Task 2 essays. Use when the user pastes an IELTS Writing Task 2 question and their essay and wants: (1) band scores on each official criterion (TR, CC, LR, GRA) plus an overall band score, (2) inline Markdown corrections on the original essay (strikethrough errors, inline code for corrections), (3) detailed correction analysis, and (4) a Band 7–9 model paraphrase with analysis, and (5) a topic language bank covering collocations, phrasal verbs, high-band vocabulary, and synonyms. Triggers on phrases like "批改 Task 2", "evaluate my IELTS writing", "IELTS Task 2 correction", or any submission of an IELTS Task 2 prompt + essay.

  • Product prd

    Bosh-Kuo/awesome-agent-toolkit/examples/.agents/skills/product-prd Skill

    no license2★ repo

    Generate or update a project-level Product Requirements Document (PRD.md) after the user and AI have already discussed requirements, target users, product goals, implementation approach, workflow, and key technical decisions. Focuses on product overview, vision, core objectives, user personas, high-level feature groups, tech stack, system architecture key components, and phased roadmap / future work. Use when the user asks to create a PRD, write a product PRD, document project requirements, summarize the whole project direction, or produce a global project context file for future AI implementation work. Do not use for single-feature specs, acceptance criteria, detailed technical design, or implementation tasks.

  • Spec writer

    Bosh-Kuo/awesome-agent-toolkit/examples/.agents/skills/spec-writer Skill

    no license2★ repo

    Generates feature specification documents based on provided code and functional descriptions. Focuses on system analysis and product logic rather than implementation details. Code is treated as the single source of truth.

  • Ielts writing task1 examiner

    Bosh-Kuo/awesome-agent-toolkit/examples/.claude/skills/ielts-writing-task1-examiner Skill

    no license2★ repo

    IELTS Writing Task 1 examiner — evaluates, corrects, and rephrases Academic or General Training Task 1 essays. Use when the user pastes an IELTS Writing Task 1 question and their essay and wants: (1) band scores on each official criterion (TA, CC, LR, GRA) plus an overall band score, (2) inline Markdown corrections on the original essay (strikethrough errors, inline code for corrections), (3) detailed correction analysis, (4) a Band 7–9 model answer with selective HTML highlighting, (5) model answer analysis, and (6) a topic language bank covering chart/letter collocations, useful phrasal verbs where natural, high-band vocabulary, and synonyms. Triggers on phrases like "批改 Task 1", "evaluate my IELTS writing", "IELTS Task 1 correction", or any submission of an IELTS Task 1 prompt + essay.

  • Ielts writing task2 examiner

    Bosh-Kuo/awesome-agent-toolkit/examples/.claude/skills/ielts-writing-task2-examiner Skill

    no license2★ repo

    IELTS Writing Task 2 examiner — evaluates, corrects, and rephrases Academic or General Training Task 2 essays. Use when the user pastes an IELTS Writing Task 2 question and their essay and wants: (1) band scores on each official criterion (TR, CC, LR, GRA) plus an overall band score, (2) inline Markdown corrections on the original essay (strikethrough errors, inline code for corrections), (3) detailed correction analysis, and (4) a Band 7–9 model paraphrase with analysis, and (5) a topic language bank covering collocations, phrasal verbs, high-band vocabulary, and synonyms. Triggers on phrases like "批改 Task 2", "evaluate my IELTS writing", "IELTS Task 2 correction", or any submission of an IELTS Task 2 prompt + essay.

  • Product prd

    Bosh-Kuo/awesome-agent-toolkit/examples/.claude/skills/product-prd Skill

    no license2★ repo

    Generate or update a project-level Product Requirements Document (PRD.md) after the user and AI have already discussed requirements, target users, product goals, implementation approach, workflow, and key technical decisions. Focuses on product overview, vision, core objectives, user personas, high-level feature groups, tech stack, system architecture key components, and phased roadmap / future work. Use when the user asks to create a PRD, write a product PRD, document project requirements, summarize the whole project direction, or produce a global project context file for future AI implementation work. Do not use for single-feature specs, acceptance criteria, detailed technical design, or implementation tasks.

  • Spec writer

    Bosh-Kuo/awesome-agent-toolkit/examples/.claude/skills/spec-writer Skill

    no license2★ repo

    Generates feature specification documents based on provided code and functional descriptions. Focuses on system analysis and product logic rather than implementation details. Code is treated as the single source of truth.

  • Ielts writing task1 examiner

    Bosh-Kuo/awesome-agent-toolkit/skills/ielts-writing-task1-examiner Skill

    no license2★ repo

    IELTS Writing Task 1 examiner — evaluates, corrects, and rephrases Academic or General Training Task 1 essays. Use when the user pastes an IELTS Writing Task 1 question and their essay and wants: (1) band scores on each official criterion (TA, CC, LR, GRA) plus an overall band score, (2) inline Markdown corrections on the original essay (strikethrough errors, inline code for corrections), (3) detailed correction analysis, (4) a Band 7–9 model answer with selective HTML highlighting, (5) model answer analysis, and (6) a topic language bank covering chart/letter collocations, useful phrasal verbs where natural, high-band vocabulary, and synonyms. Triggers on phrases like "批改 Task 1", "evaluate my IELTS writing", "IELTS Task 1 correction", or any submission of an IELTS Task 1 prompt + essay.

  • Ielts writing task2 examiner

    Bosh-Kuo/awesome-agent-toolkit/skills/ielts-writing-task2-examiner Skill

    no license2★ repo

    IELTS Writing Task 2 examiner — evaluates, corrects, and rephrases Academic or General Training Task 2 essays. Use when the user pastes an IELTS Writing Task 2 question and their essay and wants: (1) band scores on each official criterion (TR, CC, LR, GRA) plus an overall band score, (2) inline Markdown corrections on the original essay (strikethrough errors, inline code for corrections), (3) detailed correction analysis, and (4) a Band 7–9 model paraphrase with analysis, and (5) a topic language bank covering collocations, phrasal verbs, high-band vocabulary, and synonyms. Triggers on phrases like "批改 Task 2", "evaluate my IELTS writing", "IELTS Task 2 correction", or any submission of an IELTS Task 2 prompt + essay.

  • Product prd

    Bosh-Kuo/awesome-agent-toolkit/skills/product-prd Skill

    no license2★ repo

    Generate or update a project-level Product Requirements Document (PRD.md) after the user and AI have already discussed requirements, target users, product goals, implementation approach, workflow, and key technical decisions. Focuses on product overview, vision, core objectives, user personas, high-level feature groups, tech stack, system architecture key components, and phased roadmap / future work. Use when the user asks to create a PRD, write a product PRD, document project requirements, summarize the whole project direction, or produce a global project context file for future AI implementation work. Do not use for single-feature specs, acceptance criteria, detailed technical design, or implementation tasks.

  • Spec writer

    Bosh-Kuo/awesome-agent-toolkit/skills/spec-writer Skill

    no license2★ repo

    Generates feature specification documents based on provided code and functional descriptions. Focuses on system analysis and product logic rather than implementation details. Code is treated as the single source of truth.

    The same file is in 3 other repositories

  • Paper writing

    kinhluan/skills/.agent-skills/paper-writing Skill

    2★ repo

    Write or structure academic papers, thesis chapters, or technical reports. Use when drafting a conference paper, journal article, thesis chapter, or any academic writing. Covers structure, academic tone, LaTeX, and section-by-section guidance.