The catalog
613,297 rows, by stacks then stars
ommakes/Skills/gtm-positioning Skill
21★ repoFramework-based skill for B2B product positioning, GTM strategy selection, and website messaging. Use when someone asks for help positioning their product, choosing a GTM strategy, writing homepage or website copy, messaging for different buyer personas, content strategy by awareness stage, or ad and landing page copy. Based on the Fletch framework by Anthony Pierri.
ommakes/Skills/metrics-tagging Skill
21★ repoAnalyze UI mockups, screenshots, or prototype frames to identify all trackable interactions and generate a complete analytics event taxonomy table. Use this skill whenever a designer uploads a screen, mockup, prototype screenshot, or UI frame and wants to know what should be tagged, what events to fire, or how to document analytics for handoff. Also trigger when someone asks to "tag this screen," "identify events," "create a tagging spec," "what should we track," or "build an event table" for any UI. If a designer shares any visual of a UI and mentions analytics, tracking, tagging, GTM, events, or metrics — use this skill.
ommakes/Skills/righter Skill
21★ repoApply UX content writing principles to review existing UI copy or write new UI copy from scratch. Use this skill whenever someone asks you to: review, audit, critique, or improve UI text, error messages, button labels, tooltips, empty states, onboarding copy, form helper text, or any software interface copy. Also trigger when someone asks you to write new UI copy, label a button, draft an error message, write a modal, or create any in-product text. If the request involves words that appear inside software — use this skill.
ommakes/Skills/vois-components Skill
21★ repoComponent selection rubrics organized by job-to-be-done. Use after vois-patterns determines structure, before vois-tokens applies tokens. Optionally records each choice via the vois_record_component_choice MCP tool if one is available. Use when deciding between similar components — Dialog vs Drawer, Toast vs Banner, Select vs Combobox, etc.
ommakes/Skills/vois-patterns Skill
21★ repoStructural decision trees for container types, form states, table layouts, and page-level patterns. Use before vois-tokens. Routes to righter skill for all microcopy (labels, errors, buttons, helpers). Use when building pages, forms, features, workflows.
ommakes/Skills/vois-tokens Skill
21★ repoRules and patterns for building UI with shadcn/ui, Tailwind v4, and Motion against a Vois design token set. Use when building components, pages, or any UI that should conform to the workspace design system. Covers spacing, typography, color tokens, component architecture, animation, accessibility, and modern CSS patterns.
arpitbbhayani/ape-skills/ape-review-blog Skill
21★ repoReviews engineering blog drafts. Use this skill whenever the user says "ape review blog", "review blog", "review this post", "give feedback on draft", "what is wrong with this post", or pastes a blog draft asking for critique, feedback, or editorial review. Also trigger when the user shares a draft and asks if it is ready to publish. Always use this skill for any engineering blog review request, even if the user just says "thoughts?" after pasting a post.
arpitbbhayani/ape-skills/ape-rewrite-blog Skill
21★ repoRewrites an engineering blog draft by first running the ape-review-blog skill on it and then applying every suggested fix to produce a revised version. Use this skill whenever the user says "ape rewrite blog", "rewrite blog", "rewrite this post", "apply review suggestions", "fix the draft", "rewrite the draft", or shares a blog file and asks to apply review feedback. Also trigger when the user has already received a review and wants the suggestions implemented in a new file. Always use this skill for any engineering blog rewrite request where the goal is to produce a fixed-up draft, not just a review. The rewrite is written to a sibling file with the `-ape.md` suffix.
arpitbbhayani/ape-skills/ape-style-markdown Skill
21★ repoApply consistent, professional Markdown formatting rules whenever producing or reformatting Markdown output. Use this skill when generating any Markdown document, when the user asks to reformat or clean up existing Markdown, when producing README files, technical docs, notes, or any other content that will be rendered as Markdown. Trigger even when the request seems simple -- any Markdown output should follow these rules. Do not use this skill for non-Markdown outputs such as plain text, HTML, or code-only responses.
arpitbbhayani/ape-skills/ape-write-pseudocode Skill
21★ repoGuidelines for writing pseudocode for functions and algorithms. Use this skill whenever the user asks to write pseudocode, sketch out an algorithm, or describe the logic of a function at a high level. Trigger on phrases like "write pseudocode", "sketch this algorithm", "pseudocode for this function", or "describe the logic".
gaia-react/gaia/.claude/skills/file-tech-debt Skill
21★ repoFile a new tech-debt GitHub issue for an out-of-scope code-review finding, building the dedup key, checking for an existing open or declined-closed match, and only if none exists, creating the issue with the right labels and touching the debt-count staleness sentinel. Trigger on natural-language asks like "file a tech-debt issue", "record this as tech-debt", "open a tech-debt issue for this out-of-scope finding", or "file this finding as debt". Do NOT trigger on draining, fixing, listing, or prioritizing existing debt (that's `/gaia-debt`), nor on general "clean up the code" or "fix this bug" asks that aren't about filing a new tracked issue.
gaia-react/gaia/.claude/skills/gaia-handoff Skill
21★ repoGenerate a comprehensive GAIA session handoff document, accomplishments, decisions, current state, open questions, so context can be cleared or compacted without losing anything. Trigger on `/gaia-handoff` or natural-language asks like "write a handoff", "hand off this session", or "document where we are before I clear context".
gaia-react/gaia/.claude/skills/gaia-pickup Skill
21★ repoRestore context from the most recent GAIA session handoff and suggest the next action. Trigger on `/gaia-pickup` or natural-language asks like "pick up where we left off", "resume from the handoff", or "continue the last session".
gaia-react/gaia/.claude/skills/gaia-react-perf Skill
21★ repoDiagnose React render performance by driving a micro-interaction, capturing real renders, and surfacing memo-defeating reference instability with a recommended structural fix. Measure-only: it emits a diagnosis, it does not auto-fix. Trigger on `/gaia-react-perf` or natural-language asks like "profile renders", "measure renders", "why is X re-rendering", or "diagnose render performance". Do NOT trigger on vague "feels slow", "janky", or "optimize my app".
gaia-react/gaia/.claude/skills/gaia-wiki Skill
21★ repoGAIA wiki maintenance, sync, consolidate, lint. Runs the full chain with no sub-arg, or a single stage when named (sync | consolidate | lint); append --force to override drift gating. Trigger on `/gaia-wiki <stage>` or natural-language asks like "sync the wiki", "run the wiki maintenance chain", "consolidate the wiki", or "lint the wiki".
gaia-react/gaia/.claude/skills/new-component Skill
21★ repoScaffold a new React component with optional Storybook story and Vitest test files. Use this skill whenever the user asks to "create a component", "make a button", "scaffold a card", "add a new component", or asks for a new file under `app/components/` following the project's component pattern (PascalCase folder, index.tsx, tests/).
gaia-react/gaia/.claude/skills/new-hook Skill
21★ repoScaffold a new custom React hook with a Vitest test file. Use this skill whenever the user asks to "create a hook", "make a useFoo hook", "scaffold a custom React hook", "add a hook under app/hooks", or describes a piece of reusable React state/effect logic that warrants extraction into a named `use*` hook.
gaia-react/gaia/.claude/skills/new-route Skill
21★ repoScaffold a new route with its page component, test, story, and optional i18n keys. Use this skill whenever the user asks to "create a route", "add a new page", "scaffold /dashboard", "wire up a new route under _public+ or _session+", or anything that implies adding a file under `app/routes/` with a matching `app/pages/{Group}/{PascalName}Page/` folder.
gaia-react/gaia/.claude/skills/new-service Skill
21★ repoScaffold a new API service with request functions, Zod schemas, URL constants, and optional MSW mock handlers. Use this skill whenever the user asks to "add a service", "create the projects API", "scaffold a new GAIA service", "wire up CRUD for users", or anything implying a new folder under `app/services/gaia/{name}/` with parsers/types/requests + matching `test/mocks/{name}/` collections.
gaia-react/gaia/.claude/skills/playwright-cli Skill
21★ repoAutomates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
gaia-react/gaia/.claude/skills/react-code Skill
21★ repoPatterns and conventions for writing and editing React code, including components and hooks. Use this skill whenever writing or reviewing React components, hooks (useEffect, useCallback, useState), event handlers, or component extraction decisions. Also trigger when debugging stale closures, infinite re-renders, or unnecessary re-renders caused by memoization issues, or when deciding whether to add a dependency, reach for a web-platform API (Intl, URL, crypto.randomUUID), or hand-roll a primitive. Also trigger when choosing a React 19 idiom, deciding between forwardRef and ref-as-prop, useContext and use(), or Context.Provider and the Context shorthand; when conditional rendering risks the && numeric-0 leak; or when tempted to reach for React's form Actions (useActionState, useFormStatus, useOptimistic) instead of React Router's form handling.
gaia-react/gaia/.claude/skills/release-notes Skill
21★ repoMaintainer-only. Translate a version's GAIA CHANGELOG entries into plain-language public release notes for the marketing site (gaiareact.com). Writes a release-data `.ts` file under `../website/src/pages/changelog/releases/` plus an editorial-decisions report for human review. Use whenever the maintainer wants the adopter-facing notes for a version, e.g. "write release notes", "generate the changelog page entry", "translate the CHANGELOG for the website", "what's new on the site for v1.5.0", "public notes for 1.4.0", or right after cutting a release, and for one-time backfill of historical `## [x.y.z]` blocks. This is the website-notes step only. It does NOT edit `CHANGELOG.md`, it is not how you cut a release (version bump, manifest, and tag are `/gaia-release`), and it is not for an adopter's own app's release notes.
gaia-react/gaia/.claude/skills/skeleton-loaders Skill
21★ repoFor building skeleton loading states that are pixel-perfect matches of real content. Use this skill whenever adding loading states to components, building skeletons for async data, handling pending loader states in route transitions, or implementing the shimmer animation pattern. Also trigger when the user asks about preventing layout shift during data fetching.
gaia-react/gaia/.claude/skills/tailwind Skill
21★ repoPatterns and conventions for all Tailwind styling. Use this skill whenever writing Tailwind class names, combining conditional classes, building component variants, or choosing between twJoin and twMerge. Also trigger when the user asks about custom values, defining @theme tokens or CSS variables, naming color/spacing tokens, rem vs px, responsive breakpoints, or avoiding template literal class strings.
gaia-react/gaia/.claude/skills/tdd Skill
21★ repoTest-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
gaia-react/gaia/.claude/skills/typescript Skill
21★ repoPatterns and conventions for all TypeScript code. Use this skill whenever writing or reviewing TypeScript, naming identifiers, typing exports, choosing between type and interface, using Zod schemas, structuring function parameters, or enforcing code patterns like avoiding switch statements and enums.
gaia-react/gaia/.claude/skills/update-deps Skill
21★ repoAutonomous Dependabot, auto-discover outdated packages, audit overrides, apply migrations for major bumps, resolve conflicts, run quality gate. Trigger when the user clicks the statusline `Run /update-deps` indicator or asks "update dependencies", "bump deps", "run dependabot".
gaia-react/gaia/.claude/skills/update-gaia Skill
21★ repoPull the latest GAIA release into this project without clobbering customizations. Three-way merge per file using .gaia/manifest.json classes. Trigger when the user clicks the statusline `Run /update-gaia` indicator or asks "update GAIA", "pull the latest GAIA", "apply the new GAIA release".
tizzy916/scholar-wendao-skill/examples/stiegler-perspective Skill
no license21★ repoBernard Stiegler(贝尔纳·斯蒂格勒,1952-2020)的学术分析镜片。 基于 8 部本地一手 PDF(法语原版 + 英译 + 中译)、395 部 OpenAlex 元数据档案、 6 部核心著作的概念地图交叉验证(against Obsidian 6 个 ground-truth 概念笔记), 提炼 6 个核心概念、3 个次级概念、6 条方法论进路、完整的智识谱系与五项诚实边界。 默认输出第三人称学术分析("从 Stiegler 的 organology 视角看……")。 对话/角色扮演模式作为 opt-in,需用户明确激活。 当用户提到「用 Stiegler 的视角」「Stiegler 会怎么分析」「Stiegler 镜片」 「Stiegler perspective」「pharmakon 框架」「organology 视角」「第三持存分析」 「为我用 Stiegler 的概念解读这段材料」「数字资本主义批判」「技术哲学分析」 「废人化诊断」「象征的贫困分析」时使用。 即使用户只是说「换 Stiegler 的角度想想」「这是 pharmakon 哪一面」也应触发。
Lambenthan/paper-discipline-skills/paper-confirm-before-doing Skill
21★ repo论文写作中遇到任何模糊指令(改、整理、润色、重写、找出、统一、清理、看看、处理一下…), 在调用任何写文件 / 编辑文件 / 批量操作工具之前,必须先用一段话向用户陈述 「我打算怎么做、改哪里、不改哪里」,并明确等待用户确认后再动手。 Use when 用户对论文 / 章节 / 段落 / 文献 / 图表 / 参考文献给出宽泛指令、 未指定具体范围或方法、未限定「只改 X 不改 Y」等边界。
Lambenthan/paper-discipline-skills/paper-logical-consistency Skill
21★ repo当用户改动论文里的核心声明(研究问题、核心论点、因果关系、边界条件、假设、关键结论、对已有研究的态度)时, 必须先扫描该声明在全文其他章节的出现位置,列出来让用户核对哪些需要联动修改,再开始动手。 本 Skill 抓的是「论证一致性」(语义级),不是「术语一致性」(机械级)——两者互不替代。 Use when 用户改了核心论点、研究问题、主要结论、方法边界、假设; 或要求重写涉及核心声明的段落;或在交付前要求"检查一下逻辑"。
Lambenthan/paper-discipline-skills/paper-one-session-one-task Skill
21★ repo当用户在一次对话里同时提出多个论文写作任务("顺便也帮我..."、"另外..."、"还有..."), 必须先把这些任务列出来让用户挑一个,拒绝在同一个会话里串行做完所有事。 Use when 用户的一条请求里出现两个以上独立的写作 / 修改 / 核查任务, 或在已经在做 A 任务时临时追加 B 任务。
Lambenthan/paper-discipline-skills/paper-parallel-audit Skill
21★ repo在执行 ≥ 30 条目的批量核查 / 批量修改任务(引用核查、术语一致性检查、格式统一、文献元数据补齐)时, 必须采用"派多个 Agent 并行 + 每个 Agent 输出 JSON + 主进程汇总落盘 + 分批断点续跑"的标准模式, 不得在主会话里串行单线程跑全量。 Use when 任务规模 ≥ 30,涉及对独立条目的同质操作(每个条目处理逻辑相同、之间无依赖)。
Lambenthan/paper-discipline-skills/paper-pilot-before-batch Skill
21★ repo在执行任何 ≥ 30 条目的批量任务(批量改文件、批量核查引用、批量重命名、批量格式统一)之前, 必须先在 3–5 个样本上跑一遍,把样本结果给用户看,确认逻辑正确后再推全量。 Use when 用户请求处理"全部"、"所有"、"批量"、"逐个"某类对象, 且对象数量 ≥ 30,或数量未知("把整个目录的...")。
Lambenthan/paper-discipline-skills/paper-protect-terminology Skill
21★ repo在跨多文件批改、术语统一、整篇论文润色、章节重写等可能改动专业术语 / 缩写 / 人名 / 概念命名的操作之前, 必须先显式列出"保护术语清单",让用户确认哪些词不得被同义替换或改写,再开始执行。 Use when 用户要求跨章节修改、批量替换、整篇润色、术语统一、规范化、 或对出现专业术语 / 缩写 / 模型名 / 算法名 / 自定义概念的段落做改写。
Paper translate advisor feedback
Lambenthan/paper-discipline-skills/paper-translate-advisor-feedback Skill
21★ repo当用户拿来导师的录音转写、便条、口头反馈、批注、邮件意见时, 禁止直接喂 AI 改文章;必须先把口语化 / 模糊 / 隐含的反馈翻译为 「位置 + 改什么 + 改成什么 + 标准 + 不动哪里」的可执行指令清单,让用户确认后再开始改。 Use when 用户提供导师反馈(录音、批注、便条、邮件、聊天截图、口述), 并要求"按导师意见改一下"。
Lambenthan/paper-discipline-skills/paper-using-skills Skill
21★ repo《Claude Code 科研手记》论文写作纪律 skill 集的入口与强制触发器。 建立"1% 可能适用就必须调用"的硬规则,列出本系列各核心纪律 skill 的触发条件, 防止用户在赶论文 / 紧张 / 熟练之后跳过该有的检查动作。 Use when 开始任何科研写作场景:写论文、改论文、整理参考文献、 画图、整理导师反馈、跑批量任务、改 Word、提交前检查 等。
Lambenthan/paper-discipline-skills/paper-verify-before-handoff Skill
21★ repo在把任何成果交付给用户("改完了"、"已完成"、"可以发给导师"、"可以提交")之前, 必须运行一份硬检查清单:术语一致性、引用完整性、数据正确性、图表编号、 内部交叉引用、字数 / 格式合规、未完成 todo 残留、AIGC pattern(涉及文段改写时跑 chinese-de-aigc 五维自评)、 论证一致性(涉及核心声明改动时跑 paper-logical-consistency 复核)、 改动概要——任意一项 fail 都不能宣告完成。 Use when 你即将说「改完了 / 完成了 / 可以提交了 / 可以发给导师了」、 或用户问「是不是可以了」「还有什么要检查的吗」。
Lambenthan/paper-discipline-skills/paper-writing-discipline Skill
21★ repo当用户在科研写作过程中踩到一个本系列 paper-* skill 没覆盖的新坑、 并表示"以后...我都要这样做"、"下次记得..."、"这种情况要先..."、"加一条新规则"时, 帮用户把这条新规则按 4 个判断题筛过,合格则按本 skill 提供的模板提炼成一个新的 paper-* skill 落盘。 Use when 用户说"以后...都要..."、"下次记得..."、"这种情况要先..."、 "帮我把这个习惯固化下来"、"加一条新规则"。
indranilbanerjee/contentforge/skills/cf-analytics Skill
21★ repoTrack content quality scores, pipeline timing, and compliance trends with insights and alerts.
indranilbanerjee/contentforge/skills/cf-audit Skill
21★ repoAudit content library for freshness decay, coverage gaps, and optimization opportunities.
indranilbanerjee/contentforge/skills/cf-brief Skill
21★ repoGenerate research-backed content briefs with keywords, competitors, intent, and SEO strategy from a topic.
indranilbanerjee/contentforge/skills/cf-calendar Skill
21★ repoPlan content calendars with scheduling, deadlines, team assignments, and Google Calendar sync.
indranilbanerjee/contentforge/skills/cf-connect Skill
21★ repoSet up an MCP connector with step-by-step instructions. Use to connect Notion, Canva, Webflow, etc.
indranilbanerjee/contentforge/skills/cf-cowork-setup Skill
21★ repoOne-shot setup that wires ContentForge for team usage in Anthropic Cowork. Verifies Cowork environment, checks for a Google Drive integration, creates the canonical Drive folder layout, and confirms the team-ready output routing. Use this the first time a Cowork user installs ContentForge OR when files aren't landing in Drive.
indranilbanerjee/contentforge/skills/cf-environment Skill
21★ repoDetect the runtime environment (Cowork sandbox vs local Claude Code) and report which ContentForge capabilities work in it. Use this when the user asks 'will this work in Cowork', sees unexpected file-path behavior, or wants a capability matrix before running a long pipeline.
indranilbanerjee/contentforge/skills/cf-help Skill
21★ repoShow the ContentForge user guide, available skills, pipeline overview, examples, and troubleshooting
indranilbanerjee/contentforge/skills/cf-integrations Skill
21★ repoShow active and available MCP connectors with workflow impact. Integration status dashboard.
indranilbanerjee/contentforge/skills/cf-publish Skill
21★ repoPublish finished content to Webflow or WordPress via MCP connectors with preview, verification, and HTML export fallback
indranilbanerjee/contentforge/skills/cf-social-adapt Skill
21★ repoRepurpose finished articles into platform-specific social media posts for LinkedIn, Twitter/X, Instagram, Facebook, Threads, TikTok, Bluesky, and YouTube Shorts
indranilbanerjee/contentforge/skills/cf-style-guide Skill
21★ repoImport brand voice profiles from documents or URLs. Use when setting up or updating a brand.
indranilbanerjee/contentforge/skills/cf-switch-backend Skill
21★ repoSwitch tracking backend (local/airtable/google) with optional data migration
indranilbanerjee/contentforge/skills/cf-template Skill
21★ repoCreate custom content type templates beyond the 5 built-in types with structure and quality standards.
indranilbanerjee/contentforge/skills/cf-translate Skill
21★ repoTranslate content into 15 languages preserving brand voice, citations, and SEO. Three localization levels.
indranilbanerjee/contentforge/skills/cf-variants Skill
21★ repoGenerate scored A/B test variations of headlines, hooks, CTAs, and intros ranked by optimization goal.
indranilbanerjee/contentforge/skills/cf-video-script Skill
21★ repoProduce video scripts with hooks, scenes, and B-roll for YouTube, TikTok, Reels, and explainers.
indranilbanerjee/contentforge/skills/content-refresh Skill
21★ repoRefresh existing content with updated data, sources, and SEO while preserving rankings and brand compliance.
indranilbanerjee/contentforge/skills/contentforge Skill
21★ repoProduce publication-ready, fact-checked, brand-aligned content via 10-phase autonomous pipeline. Use for any content need.
cmertdalli/polisci-review/templates/claude-skill Skill
21★ repoRun a public-facing political science pre-submission audit with journal personas, stage gating, and evidence-grounded issue reporting
cmertdalli/polisci-review/templates/codex-skill Skill
21★ repoRun a political science pre-submission audit with journal-aware personas, stage-aware standards, and evidence-grounded issue reporting.