agentsclimarketplace

Docs & writing

16,621 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

  • Csharp coding

    nguyenthdat/opencode-manager/registry/skills/csharp-coding Skill

    1★ repo

    Comprehensive idiomatic C#/.NET guidance: 186 prioritized rules across 15 categories covering memory/resource management, error handling, async/await, API and record design, LINQ, naming, nullability, dependency injection, testing, documentation, performance, project structure, analyzers, and anti-patterns. Use when writing, reviewing, refactoring, optimizing, or debugging C# or .NET code (`.cs`, `.csproj`, `Directory.Build.props`). Targets modern C# 12/13 and .NET 8/9 idioms (primary constructors, collection expressions, required members, nullable reference types, records) while respecting the project's declared language version and target framework.

  • Report builder

    metalaihq/trip-event-curator/skills/report-builder Skill

    1★ repo

    Build a single self-contained HTML report (report.html) from any skill's output in this plugin — conclusion cards first (miss-it-and-regret picks / booking deadlines / do-this-now), the day-by-day woven itinerary and evidence tables second, statistics and limits as footnotes — generated with Python standard library only, all CSS/JS inline, zero external CDN/fonts/images, and verified on disk (file exists + size > 0 + zero external load references) with an 'open report.html' instruction printed. Use when the user says 'report.html로 만들어줘', 'HTML로 뽑아줘', '파일로 정리해줘', '동행한테 공유할 수 있게', '보고서로 만들어', or complains '지난번 파일은 열리지도 않았어', 'HTML이 깨져'. The final output stage after trip-weaver, trip-brief, event-finder, or any other skill. Anti-regression rules ported verbatim from the meditherapy report-builder.

  • Add skill

    Paldom/skillskit/skills/create-skill-repo/assets/template/.claude/skills/add-skill Skill

    1★ repo

    Authors or improves an Agent Skill in this repo via the eval-first workflow - scope one purpose, write trigger evals, draft SKILL.md, validate, iterate. Use when the user asks to create, add, write, refine, or fix a skill ("add a skill for X", "improve triggering of Y"). Not for scaffolding a new repository or editing infrastructure (hooks, CI, the validator/scripts, docs).

  • Scientific review writer

    k-telux/SciReviewWriter/skills/scientific-review-writer Skill

    1★ repo

    Evidence-gated workflow for planning, drafting, revising, auditing, and packaging scientific literature reviews, thesis reviews, and paper-style manuscripts from source notes, PDFs, BibTeX, LaTeX, DOCX, figures, or reviewer feedback. Use when the work must be mechanism-first, citation-traceable, visually verified, privacy-safe, and explicit about uncertainty, competing interpretations, and publication readiness.

  • Report issue

    LeonardSEO/power-platform-skills-codex/plugins/canvas-apps/skills/report-issue Skill

    1★ repo

    Use this skill when the user wants to "report a bug", "file an issue", "report an issue", "submit a bug report", or report any problem with the canvas-apps plugin to the GitHub repository.

    The same file is in 1 other repository

  • Report issue

    LeonardSEO/power-platform-skills-codex/plugins/code-apps-preview/skills/report-issue Skill

    1★ repo

    Use this skill when the user wants to "report a bug", "file an issue", "report an issue", "submit a bug report", or report any problem with the code-apps plugin to the GitHub repository.

    The same file is in 1 other repository

  • Report issue

    LeonardSEO/power-platform-skills-codex/plugins/mcp-apps/skills/report-issue Skill

    1★ repo

    Use this skill when the user wants to "report a bug", "file an issue", "report an issue", "submit a bug report", or report any problem with the mcp-apps plugin to the GitHub repository.

    The same file is in 1 other repository

  • Add pdf report

    LeonardSEO/power-platform-skills-codex/plugins/mobile-app/skills/add-native/add-pdf-report Skill

    1★ repo

    Internal implementation skill invoked by /add-native for app-generated PDF report workflows using expo-print and, when present, expo-sharing.

    The same file is in 1 other repository

  • Add sharepoint

    LeonardSEO/power-platform-skills-codex/plugins/mobile-app/skills/add-sharepoint Skill

    1★ repo

    Use when the user wants to read or write SharePoint lists, manage documents in a SharePoint document library, or create a new SharePoint list from a Power Apps mobile app.

  • Report issue

    LeonardSEO/power-platform-skills-codex/plugins/mobile-app/skills/report-issue Skill

    1★ repo

    Use when the user wants to report a bug, file an issue, submit a bug report, or report any problem with the mobile-app plugin.

    The same file is in 1 other repository

  • Report issue

    LeonardSEO/power-platform-skills-codex/plugins/model-apps/skills/report-issue Skill

    1★ repo

    Use this skill when the user wants to "report a bug", "file an issue", "report an issue", "submit a bug report", or report any problem with the model-apps plugin to the GitHub repository.

    The same file is in 1 other repository

  • Report issue

    LeonardSEO/power-platform-skills-codex/plugins/power-automate/skills/report-issue Skill

    1★ repo

    Use this skill when the user wants to "report a bug", "file an issue", "report an issue", "submit a bug report", or report any problem with the power-automate plugin to the GitHub repository.

    The same file is in 1 other repository

  • Report issue

    LeonardSEO/power-platform-skills-codex/plugins/power-pages/skills/report-issue Skill

    1★ repo

    Use this skill when the user wants to "report a bug", "file an issue", "report an issue", "submit a bug report", or report any problem with the power-pages plugin to the GitHub repository.

    The same file is in 1 other repository

  • Docs drift guard

    mohamedzhioua/proofguard/skills/docs-drift-guard Skill

    1★ repo

    Blocks calling a code change "done" when it renamed, added, removed, or changed a public name, flag, command, default value, count, config key, or behavior but left the docs (README, CHANGELOG, docs/, examples, --help text, code comments/docstrings) still referencing the old surface. Best used reactively after code changes a public name, flag, command, default value, count, config key, or behavior. Use when the user says "rename", "change the flag", "update the API", "add a command", "bump the version", or after any change to a user-facing surface. DO NOT USE for pure internal refactors with no public surface, or for verifying tests (test-code quality is out of proofguard's scope; a test-quality-guard is in `deferred/`, not yet shipped); this guard checks that DOCS match the code after a change.

  • Specification writing

    jahfaliabdulrahman-dev/hermes-skills/skills/specification-writing Skill

    1★ repo

    Production-grade agent skills for Flutter, DevOps & AI Governance

  • Piensalo write

    ralfyishere/piensalo/skills/piensalo-write Skill

    1★ repo

    Writing and content-creation program: build the claim ledger and constraint checklist first, draft divergently, run separate argument/accuracy/style critic passes, compress without losing ledger items. Use for high-stakes prose - announcements, notices, abstracts, memos, docs - where every claim must be defensible and omissions are costly. Trigger phrases: 'draft', 'write the announcement/memo/notice', 'tighten this'.

  • Ad creative

    cskwork/supermarketer-skill/vendor/marketingskills/skills/ad-creative Skill

    1★ repo

    When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' 'static ads,' 'static ad concepts,' 'ad templates,' 'iMessage ad,' 'chat reveal ad,' 'fake DM ad,' 'ChatGPT ad,' 'Apple Notes ad,' 'AirDrop ad,' 'creative strategy,' 'creative roadmap,' 'creative retro,' 'hook writing,' 'creative review page,' 'present ad creative for approval,' 'motion video ad,' 'faceless video ad,' 'animated explainer ad,' 'motion collage ad,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.

    The same file is in 2 other repositories

  • Content strategy

    cskwork/supermarketer-skill/vendor/marketingskills/skills/content-strategy Skill

    1★ repo

    When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.

    The same file is in 5 other repositories

  • Copywriting

    cskwork/supermarketer-skill/vendor/marketingskills/skills/copywriting Skill

    1★ repo

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

    The same file is in 5 other repositories

  • Marketing plan

    cskwork/supermarketer-skill/vendor/marketingskills/skills/marketing-plan Skill

    1★ repo

    When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product. Also use when the user mentions "marketing plan," "growth plan," "GTM plan," "go-to-market plan," "AARRR plan," "90-day marketing plan," "12-month marketing roadmap," "fractional CMO plan," or "fCMO plan." Generates an exhaustive 13-section plan structured by AARRR (Acquisition, Activation, Retention, Referral, Revenue), customized to the client's current budget, team, and stage, mapped to future funding milestones, cross-referenced with the 139-idea marketing-ideas library and an embedded 17-section current-state audit rubric, with a full marketing operations stack showing which skills and MCP/API integrations execute each part. Outputs a Notion-paste-ready markdown document. For positioning and ICP context before planning, see product-marketing. For stage-specific deep work, see onboarding, signup, emails, referrals, pricing.

    The same file is in 3 other repositories

  • Sales enablement

    cskwork/supermarketer-skill/vendor/marketingskills/skills/sales-enablement Skill

    1★ repo

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

    The same file is in 4 other repositories

  • Cognitive ux docs

    kfeng209-oss/cognitive-ux/skills/cognitive-ux-docs Skill

    1★ repo

    Design and audit technical documentation, knowledge bases, help centers, and support websites using evidence-informed UX. Use when people must diagnose a problem and self-serve a solution; return task-based information architecture, search and zero-result behavior, article anatomy, escalation handoff, accessibility checks, and find-and-apply validation.

  • Skillproof

    Dafenxz0/skillproof/skills/skillproof Skill

    1★ repo

    Design, run, audit, and interpret evidence-based benchmarks for Agent Skills. Use when proving whether a SKILL.md improves outcomes, comparing baseline/automatic/forced use, testing activation or false activation, measuring quality/tokens/cost/latency, detecting regressions, or producing a reproducible SkillProof report. Also use to repair weak skill benchmarks or scope unsupported benchmark claims. Do not use for ordinary coding, writing, or analysis merely because it mentions tests, metrics, models, or benchmarks.

  • 507 setup

    ssdiwu/507-skills/code/507-setup Skill

    1★ repo

    为一个或多个代码项目做工作流初始化或全量规范巡检:核对 AGENTS、README、CHANGELOG、doc、术语、决策和代码目录现实,先报告再路由。Use when user says 项目初始化, 项目规范巡检, 工作流初始化, 校准 AGENTS, project setup, project bootstrap, scaffold. 不用于代码体检或架构 review;专项地图维护使用 507-map。

  • Database conventions

    andr-ca/agentharness/.claude/skills/database-conventions Skill

    1★ repo

    Use when designing a database schema, writing migrations, reviewing SQL queries, or choosing between relational and document models — covers naming, index strategy, migration safety, N+1 prevention, and transaction boundaries.

  • Harness promotion

    atlax-tech/harness-armor/skills/harness-promotion Skill

    no license1★ repo

    Inspect real code, configuration, tests, CI, and documentation in an existing non-managed repository, then add a truthful Harness Engineering layer without refactoring behavior. Use when promoting a legacy Node, Python, Java, or other codebase for safe AI-agent work. Do not use for empty/docs-only repositories, deployment promotion, managed-Harness sync, or automatic code modernization.

  • After

    RudrenduPaul/evolveguard/fixtures/labeled-non-breaking-edits/case-05-new-hook-network-call/after Skill

    1★ repo

    Writes a CHANGELOG entry from the latest commits and posts it to Slack.

  • Before

    RudrenduPaul/evolveguard/fixtures/labeled-non-breaking-edits/case-05-new-hook-network-call/before Skill

    1★ repo

    Writes a CHANGELOG entry from the latest commits.

  • Changelog writer

    whatsuppiyush/god-of-skills/engineering/changelog-writer Skill

    1★ repo

    Turn merged pull requests since the last release tag into a human changelog grouped by Added / Fixed / Changed / Removed, written in user-facing language, not commit-speak. Use whenever the user says "write the changelog", "release notes", "what changed since last release", "generate CHANGELOG", "notes for this version", or is about to cut a release and needs notes. Reach for it right after a version bump, before publishing a release on GitHub, or when a maintainer wants to tell users what is new without hand-reading 40 PR titles. Produces a ready CHANGELOG.md section with a one-line summary on top.

  • Email marketing

    whatsuppiyush/god-of-skills/marketing/email-marketing Skill

    1★ repo

    The playbook for owned-email marketing to an opted-in list: deliverability, list growth, writing and creative, sequences, segmentation, and the KPIs that matter. Use whenever the user is building or fixing an email program, a newsletter, or lifecycle flows, or says things like "my emails land in spam", "how do I grow my list", "write a welcome email", "set up abandoned cart", "which ESP", "my open rate dropped", "should I do double opt-in", "annual discount email", "launch sequence for my course", "segment my list", or asks what email metrics to track. Reach for it even when the request is a single email, because the send is only as good as the setup and audience behind it.

  • Sales outbound

    whatsuppiyush/god-of-skills/sales/sales-outbound Skill

    1★ repo

    The cold-outbound discipline: turn a stranger list into booked calls and closed deals with researched cold email, follow-ups, deliverability infrastructure, AI personalization, and founder-led selling. Use whenever the user is writing a cold email, building an outbound or cold-DM campaign, asks about reply rates / open rates / bounce rates, mentions subject lines, follow-up cadence, email deliverability or domain warmup, wants to find or verify prospect emails, source or scrape a lead list, personalize outreach at scale with AI, poach a competitor's customers, or set up founder-led / advice-approach sales. Reach for it on phrases like "my cold emails aren't getting replies," "write me a cold email," "how do I find their email," "should I use cold email," "warm up my domain," or "scale personalized outreach."

  • Seo cluster builder

    whatsuppiyush/god-of-skills/seo/seo-cluster-builder Skill

    1★ repo

    Turn ONE seed keyword into a full hub-and-spoke content plan grouped by real SERP overlap, not string similarity. Use whenever the user says "build a topic cluster", "content cluster", "pillar page", "hub and spoke", "content architecture", "group my keywords", "what pages should I write around X", or hands over a seed keyword and wants a content plan. Reach for it before anyone starts writing a batch of articles, when a blog has lots of overlapping posts cannibalizing each other, or when planning a new topic section from scratch. Returns a pillar page plus supporting spokes, each with intent and a target keyword, and a ready internal-link matrix.

  • Seo content brief

    whatsuppiyush/god-of-skills/seo/seo-content-brief Skill

    1★ repo

    Turn a target keyword into a fill-in brief a writer can execute: search intent, target and per-section word counts, the H2/H3 outline, entities and questions to cover, internal and external link suggestions, and a title tag plus meta description set. Use whenever the user says "write a content brief", "content brief for X", "SEO brief", "outline for this keyword", "what should this article cover", or is about to commission or write a page and wants it built to outrank the current top 10. Reach for it before drafting any SEO article or landing page. Output is a ready-to-hand-off brief template.

  • Brand voice codifier

    whatsuppiyush/god-of-skills/writing/brand-voice-codifier Skill

    1★ repo

    Distil ~10 of the user's best posts into a reusable voice guide they can paste at the top of any future writing prompt, so anything you write next sounds like them and not like generic AI. Use whenever the user says "capture my voice", "make a voice guide", "sound like me", "match my writing style", "codify our brand voice", "write in my tone", or hands over a batch of their own posts and wants future content to match. Reach for it before ghostwriting, before onboarding a new writer, or when AI drafts keep coming back sounding bland. Output is a loadable voice-guide document with rules, banned phrases, and before/after rewrites.

  • Copywriting messaging

    whatsuppiyush/god-of-skills/writing/copywriting-messaging Skill

    1★ repo

    Write and diagnose persuasive marketing copy: headlines, value props, landing pages, ad hooks, product descriptions, and brand narrative. Use whenever the user is writing or fixing copy, asks for a headline or tagline, says their "messaging isn't landing" or "converts poorly", wants a value prop that competitors can't also claim, needs to turn features into benefits, is handling objections or adding social proof, wants to mine customer language, or is polishing CTAs and micro-copy. Also reach for it on "make this ad stop the scroll", "our homepage reads like a pitch deck", "rewrite this so it sounds human not AI", "positioning", "reframe", or any request to structure copy with a framework (BAB, PAS, AIDA, hero's journey).

  • Ux writer

    shahrulestar/skills/skills/ux-writer Skill

    1★ repo

    Comprehensive UX writing and typography audit for UI text — landing pages, SaaS, web apps, dashboards, e-commerce, marketplaces, developer tools, CLI, browser extensions, mobile apps, AI/chat products, and more. Covers headings, body text, labels, buttons, placeholders, navigation, billing, onboarding, helper text, validation, empty states, i18n, and accessibility. Use when reviewing or rewriting visible copy for any product type. Trigger on "review copy," "typography audit," "SaaS copy," "landing page," "dashboard microcopy," "checkout copy," "mobile app strings," "extension popup," or "i18n copy."

  • Doc merge

    Chevis-Zhou/agent-skills/skills/doc-merge Skill

    1★ repo

    Merge, consolidate, and evolve Single Source of Truth (SSOT) documents by integrating new research or notes into an existing master document. Use this skill whenever the user wants to merge two or more documents, combine old and new research into one file, update a living document with new findings, consolidate notes into a master doc, or says things like "merge these docs", "integrate this into my doc", "update my SSOT", "combine these notes", "add this research to my master doc", "consolidate", or "weave this in." Also trigger when the user uploads two documents and asks to unify, reconcile, or synthesize them — even if they don't use the word "merge." Do NOT use for simple summarization, file format conversion, or translation tasks.

  • Thread to kb

    Chevis-Zhou/agent-skills/skills/thread-to-kb Skill

    1★ repo

    Distill the current chat thread into a concise knowledge update and integrate it into an existing knowledge base file already available in context — a Claude Project knowledge file, a Cowork folder doc, or a .md file in a Claude Code repo. Use this skill whenever the user says "update the KB", "save this to the doc", "document this discussion", "log this to [filename]", "add this to my notes", "capture what we just figured out", "fold this back into the project", "update [doc] with what we discussed", or any variant that means "take what just happened in this conversation and write it into the existing knowledge base." Trigger even when the user doesn't name the target file, as long as a KB file is clearly present in the project / folder / repo context. Do NOT use this skill for merging two uploaded documents (use doc-merge), for organizing a raw brain dump that has no existing target file (use messy-notes-organizer), or for first-time KB creation from scratch.

  • Paperflow thread

    MuKaramia/PaperFlow/skills/paperflow-thread Skill

    1★ repo

    Trace a research question or a set of intersecting keywords through the user's existing PaperFlow Obsidian library and turn networked notes into a transparent, stepwise linear argument. Use when a user asks to connect multiple concepts, organize a literature review, explain a question from vault evidence, identify library-level gaps, queue newly archived papers for later integration, revise an existing synthesis with version history, or co-write academic prose through discussion rather than receiving an instant full draft.

  • Conduct stakeholder interviews

    dineshrevunuru/SuperSkills/conduct-stakeholder-interviews Skill

    1★ repo

    Plans and runs stakeholder interviews for a new project or client engagement: identifies who to interview, builds a business-goals discussion guide (success metrics, definitions of failure, political context), maps stakeholders on a Mendelow power-interest matrix with an attitude overlay, and produces a communication plan. Use when starting a discovery or freelance client engagement — 'kick off with the client', 'who should I talk to before designing', 'interview the stakeholders', 'what does the business actually want', 'map the stakeholders', 'the client and their team want different things', or before writing any research plan or proposal. NOT for interviewing users (conduct-user-interview) or writing user-facing question guides (write-interview-guide).

  • Conduct user interview

    dineshrevunuru/SuperSkills/conduct-user-interview Skill

    1★ repo

    Runs a live semi-structured user interview end-to-end: consent and opening script, rapport warmup, broad-to-narrow funnel, neutral probing (echo/boomerang/Columbo), comfortable silence, observer management, live mistake recovery, closing, and the post-session debrief. Use when the ask is 'conduct/run/moderate a user interview', 'I have an interview session tomorrow', 'how do I probe without leading', 'the participant keeps giving one-word answers', 'stakeholders want to sit in on my interview', or prepping a facilitator cheat-sheet. NOT for writing the question guide (write-interview-guide) or moderating task-based usability tests (moderate-usability-session).

  • Design interaction flows

    dineshrevunuru/SuperSkills/design-interaction-flows Skill

    1★ repo

    Design-time interaction design: feature flows, task flows, user flows, and wireflows, plus PRD-to-scenario translation and systematic edge-case + failure-path enumeration. Use when asked to 'map the flow', 'design the user flow / task flow', 'design this feature end-to-end', 'translate this PRD into screens/scenarios', 'what are the edge cases', 'what happens if X fails', or before any high-fidelity screen work on a new feature. NOT for research-time experience maps (journey/empathy maps — that is map-customer-journey) and NOT for designing the content of each state (that is design-ui-states).

  • Document and govern design system

    dineshrevunuru/SuperSkills/document-and-govern-design-system Skill

    1★ repo

    Documents design-system components (variants, states, props, usage rules, content standards) and runs system governance — NN/g 6-dimension maturity assessment to pick the highest-leverage gap, contribution rules, review cycles with yes/no criteria, versioning and deprecation. Use when asked to 'document this component', 'write usage guidelines', 'audit our design system', 'set up a contribution process', 'people keep building one-offs', 'the system is drifting', or 'where should we invest in the design system next'. NOT for creating token values (build-token-system) or designing new component states (design-ui-states).

  • Handoff context

    dineshrevunuru/SuperSkills/handoff-context Skill

    1★ repo

    Compact a conversation into a handoff another agent can resume from — decisions + state + open threads + the ONE next action, never a transcript. Shaped to the ARIA Hub session-report schema so a handoff FEEDS the registry instead of inventing a parallel format. Use when a session is ending, context is running low, work passes to a fresh agent or sub-agent, or asked 'hand this off', 'write a handoff', 'summarize this for the next session', 'compact this so someone can pick it up', 'session summary for the Hub', 'wrap up so I can continue tomorrow'. Mode-switch: a 3-line quick pass vs a full state dump.

  • Model domain language

    dineshrevunuru/SuperSkills/model-domain-language Skill

    1★ repo

    Build the ONE shared name per concept — a ubiquitous language / domain model — used identically across client conversations, the design system, and the code. Challenge conflicting terms, sharpen fuzzy ones, scenario-test where concepts meet, and capture the resolved vocabulary in a GLOSSARY.md. Use when a term is overloaded or has rival synonyms ('does booking mean the slot or the record?', 'the client says appointment, the code says session'), when asked to 'define domain terms', 'build a glossary', 'harden the terminology', 'create a ubiquitous language', or 'this word means three things'; when a name conflict surfaces mid-build; or when another skill needs the domain vocabulary maintained. NOT for token VALUES (build-token-system) or UI-copy strings (write-ux-microcopy) — this owns the concept and its one true name; NOT for decision records (write-decision-rationale).

  • Moderate usability session

    dineshrevunuru/SuperSkills/moderate-usability-session Skill

    1★ repo

    Moderates a live usability-test session the NN/g way: think-aloud intro script, neutral re-prompts, echo/boomerang/Columbo probes, intentional silence, the no-premature-rescue rule, atomic note capture, and observer ground rules with a post-session debrief. Use when running or preparing to run a session with a real participant — 'moderate the session', 'run the usability test', 'facilitator script', 'think-aloud instructions', 'the participant is stuck / asks for help / went quiet — what do I say?', 'brief my observers', 'debrief after the session'. NOT for planning the study (plan-usability-test), writing the tasks (write-task-scenarios), or analyzing results afterward (analyze-usability-data).

  • Present and defend work

    dineshrevunuru/SuperSkills/present-and-defend-work Skill

    1★ repo

    Present research findings, defend design decisions under pushback, and write async BLUF status updates the way Dinesh does. Use when preparing a research readout ('present the findings', 'share what we learned', 'readout'), a design review where decisions will be challenged ('walk the client through it', 'defend this decision', 'stakeholders are pushing back', 'why did you design it this way'), or a written update ('send the team an update', 'status update', 'summarize where we are'). Covers finding structure, small-N honesty, video evidence, dissent handling, and answer-first writing.

  • Research technical docs

    dineshrevunuru/SuperSkills/research-technical-docs Skill

    1★ repo

    Investigate a TECHNICAL question against high-trust PRIMARY sources — official docs, source code, specs, first-party API references — trace every load-bearing assertion back to the authority that owns it, version-pin each citation, and save the findings as one cited Markdown file. Use when researching how a library/framework/API actually behaves before building on it, checking an API signature or config default, resolving 'does X support Y', 'is this deprecated', 'what changed in version N', 'how does Next.js / React / Framer Motion / GSAP / the Anthropic / ElevenLabs API do Z', or when an agent states a technical fact from memory and it needs sourcing. Researches DOCS and APIs — not markets (conduct-business-research), not users (the UX-research wing), not your own repo (codebase-design). Every assertion follows craft-critique's evidence protocol; the saved file files into build-research-repository.

  • Setup skill project

    dineshrevunuru/SuperSkills/setup-skill-project Skill

    1★ repo

    Configure a repo ONCE for the engineering/SHIP skills — decide where work items and specs live (issue tracker) and where domain/decision docs live (doc layout), then record it in one block the downstream skills read. Use before first use of the work-pipeline or SHIP skills on a repo, or when asked 'set up this project for the skills', 'where do tickets/issues live here', 'configure the issue tracker', 'set up CONTEXT.md / doc layout', 'wire up the engineering workflow', 'new repo before I start shipping', or 'run the project setup'. Run-once infra. SOLO DEFAULT = local markdown files; it mode-switches UP to a team tracker only when a team actually uses one — never assume an enterprise setup. The config is a CONTROL that stops each downstream skill from guessing where work lives.

  • Tell case study story

    dineshrevunuru/SuperSkills/tell-case-study-story Skill

    1★ repo

    Structure and write portfolio case studies and shipped-work narratives the way Dinesh does: one distinct claim per case, the outcome in line one, verifiable proof over process theatre, NDA-honest treatment where numbers can't be shown. Use when asked to 'write up this project,' 'write a case study,' 'is my case study strong,' build a portfolio project page, turn shipped work into a story (portfolio, LinkedIn, resume project blurb), or decide what a case should lead with or include. Structure and proof live here; sentence-level voice lives in writing-voice.

  • Write ai evals

    dineshrevunuru/SuperSkills/write-ai-evals Skill

    1★ repo

    Designs and runs evals for any AI feature the way Dinesh does — golden sets, grading rubrics, LLM-as-judge, hard safety gates, failure-mode taxonomies fed back into structural fixes, and AI-quality product metrics (acceptance, regeneration, edit-distance). ALSO owns the pre-design model capability assessment: what can this model actually do for this use case, cost-latency-quality tradeoffs, model-tier and provider choice. Use when asked 'which model should we use', 'is the small/cheap model good enough', 'how do we test the AI', 'write test cases for the bot', 'is it hallucinating', 'did the prompt change break anything', 'how do we know the AI is good', or BEFORE designing any LLM, voice, agent, or recommender feature. Measures failure; the user-facing failure UX belongs to design-ai-trust-and-failure-states.

  • Write client proposal

    dineshrevunuru/SuperSkills/write-client-proposal Skill

    1★ repo

    Writes freelance client proposals with tiered scope, value-anchored pricing, feasibility-checked timelines, and explicit assumptions + change control. Use when the user says 'write a proposal', 'scope this project', 'how much should I charge for this', 'the client asked for a quote', 'draft an SOW / statement of work', 'they want a price by Friday', or whenever a prospective or existing client needs a written offer of work for money. Also use to review a proposal before it goes out. Runs AFTER the problem is understood — if the client's problem is unsized or undefined, this skill routes to a paid discovery proposal instead.

  • Write decision rationale

    dineshrevunuru/SuperSkills/write-decision-rationale Skill

    1★ repo

    Writes lightweight decision records the way Dinesh's ARIA system does: 2–3 options each labeled with risk/reward and time, a chosen path with context-grounded reasoning, a MANDATORY What-Would-Change-This section, and a Decided → Revisiting → Superseded status lifecycle. Use when a meaningful choice between alternatives is being made or was just made — 'should we go with A or B', 'let's lock this in', 'document this decision', 'write a decision record', 'ADR', 'why did we choose X' — or when a tradeoff affecting timeline, quality, scope, or money is accepted, or when an old decision's assumptions have expired and its record needs a status update.

  • Write interview guide

    dineshrevunuru/SuperSkills/write-interview-guide Skill

    1★ repo

    Writes a semi-structured user-interview discussion guide (a.k.a. interview questionnaire) using NN/g's 7-step process: research questions in, funnel-ordered open questions out, with pre-written neutral probes, a coverage matrix mapping every question back to a research question, and a lint pass that catches leading, double-barreled, closed, and prediction questions. Use when asked to 'write interview questions', 'draft a discussion guide', 'prep an interview questionnaire', 'what should I ask users', or before ANY user interview is conducted. Not for running the interview live (conduct-user-interview), screeners (write-participant-screener), surveys (write-survey), or internal stakeholders (conduct-stakeholder-interviews).

  • Write participant screener

    dineshrevunuru/SuperSkills/write-participant-screener Skill

    1★ repo

    Writes a complete participant-recruiting screener plus the recruiting plan around it: behavioral (not demographic) qualifying criteria, intent-masking questions with plausible distractors, exclusion-first ordering, accept/reject/quota logic per question, professional-participant red-flag checks, and channels/incentives/over-recruit buffers. Use when recruiting for ANY study: 'write a screener', 'recruit participants', 'find people for this study', 'who qualifies', 'set up recruiting', 'screener survey', 'panel setup', 'how much incentive', 'people keep no-showing'. NOT for setting the participant profile or sample size (write-research-plan / plan-usability-test do that) and NOT for surveys that collect research data (write-survey).

  • Write problem statement

    dineshrevunuru/SuperSkills/write-problem-statement Skill

    1★ repo

    Writes a single, solution-free problem statement and derives a scoped, timeboxed discovery plan from it (discovery goals + research questions + solution icebox). Use at the START of any project, feature, or client engagement — when the user says 'write a problem statement', 'frame this problem', 'what problem are we actually solving', 'kick off this project', 'scope the discovery', or when someone arrives holding a SOLUTION ('we need a chatbot / an app / a redesign') and the underlying problem is unstated. This is the entry gate for every project: if no problem statement exists yet, load this skill before any research, design, or build skill.

  • Write research plan

    dineshrevunuru/SuperSkills/write-research-plan Skill

    1★ repo

    Writes a complete one-page UX research plan using NN/g's 5-section structure (Purpose & Goals, Participants, Method & Procedure, Logistics, Relevant Documents) — with method-agnostic research questions, a saturation-based sample size, and a mandatory feasibility gate. Use when preparing ANY user research: 'write a research plan', 'plan this study', 'prepare user research', 'set up user interviews', 'how many participants do we need', 'what should our research questions be', or when a stakeholder asks for research and no plan document exists yet. NOT for choosing the method itself (choose-research-method) or writing the questions asked to participants (write-interview-guide).

  • Write survey

    dineshrevunuru/SuperSkills/write-survey Skill

    1★ repo

    Drafts and audits self-administered surveys using NN/g's 10 survey best practices: a per-question bias lint (acquiescence, social desirability, framing, prediction, double-barreled, unbalanced scales), Likert vs. semantic-differential scale construction, and a survey-type-to-design-cycle-stage match. Use when asked to 'write a survey', 'draft survey questions', 'make a questionnaire', 'add an in-app / NPS / CSAT / post-test survey', 'review my survey for bias', or when choosing a rating scale. Not for interview questions (write-interview-guide), recruiting screeners (write-participant-screener), choosing an ongoing metrics program (define-ux-success-metrics), or statistical analysis of results (use-quantitative-evidence).

  • Write task scenarios

    dineshrevunuru/SuperSkills/write-task-scenarios Skill

    1★ repo

    Converts research goals into unbiased, realistic usability-test task scenarios via NN/g's 7-step goal→question→activity→scenario chain, then lints them against the 10 task-writing mistakes and forks them for quant vs qual studies. Use when preparing what participants will DO in a usability test — 'write test tasks', 'task scenarios', 'what should we ask users to do', 'draft tasks for the usability study', 'are these tasks leading?'. NOT for interview questions (write-interview-guide) or overall study planning (plan-usability-test).

  • Write ux microcopy

    dineshrevunuru/SuperSkills/write-ux-microcopy Skill

    1★ repo

    Write or review the words inside an interface — button/CTA labels, link labels, error messages, empty states, confirmation dialogs, field labels, helper text, tooltips, loading strings, notifications. Use when asked 'what should this button say?', 'write copy for this screen', 'review this error message', 'fill this empty state', 'name this CTA', or whenever a design/prototype needs its strings written or fixed. Grounded in NN/g microcopy frameworks (3 C's, 3 I's, 4Ss link labels, error-message guidelines). NOT for long-form writing (case studies, articles → writing-voice) or AI conversation behavior (→ design-conversational-interfaces).