プロトタイプ · プレビュー版:公式レジストリのすべてのサーバーを掲載し、30分ごとに同期しています。Google でログインするとレビューを書けます。プロトタイプ · 30分ごとに更新
PopNx MCPAIを使う人のためのMCPサーバー · やさしい言葉で解説

agent-skills Skill

リポジトリ ↗

作者:addyosmani★ 118,797 (whole repo)24 個の skill

★ Stars are for the whole repo, not each skill

Pick the skill to install

What it does

This repo is a collection of 24 skills

  • Connects Instruction files the AI reads
  • Account or key No key found in README or SKILL.md
  • Category コーディング
Maker’s original description
Production-grade engineering skills for AI coding agents.
作者向け:README にバッジを付ける

作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/addyosmani-agent-skills.svg)](https://mcp.popnx.com/en/skills/addyosmani-agent-skills)

一緒に使える

同じ作業で AI をサービスにつなぐ MCP

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

作者:morluto広く使われている↓ 38.9万/週★ 46.6万7 日前更新

MCP · サービスにつなぐパソコンで動く

Fallow

Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.

作者:fallow-rs広く使われている↓ 244.1万/週★ 5383一昨日更新

MCP · サービスにつなぐパソコンで動く

似た Skill

同じ種類の作業。Skill 一覧と同じ並び

似たものと比べる
これ
agent-skills
reaandrej-karpathy-skillsgraphifyMoneyPrinterTurbo
作者addyosmanimorlutomultica-aiGraphify-Labsharry0703
Skill 数241111
GitHub スター118,797467,235234,125149,873144,332
最終コード更新2026年11月14日2026年11月18日2026年4月20日2026年11月18日2026年11月18日
ライセンスMITMIT–Apache-2.0MIT

addyosmani による 24 個の Skill(指示セット)。AI が読んでそのとおりに作業します · MCP server ではありません

Pick the skill to install

Install only the ones you use. Open a skill to see how to install it

Install the whole set (24)

If you want every one, let the AI install them in one go. Know 2 things first

  • Every installed skill’s description is loaded into every chat. The more you install, the easier it is for the AI to pick the wrong one
  • Some skills duplicate tools the AI already has built in. Installing only the ones you use works better
Where to install
Please install all 24 skills from https://github.com/addyosmani/agent-skills: api-and-interface-design, browser-testing-with-devtools, ci-cd-and-automation, code-review-and-quality, code-simplification, context-engineering, debugging-and-error-recovery, deprecation-and-migration, documentation-and-adrs, doubt-driven-development, frontend-ui-engineering, git-workflow-and-versioning, idea-refine, incremental-implementation, interview-me, observability-and-instrumentation, performance-optimization, planning-and-task-breakdown, security-and-hardening, shipping-and-launch, source-driven-development, spec-driven-development, test-driven-development, using-agent-skills, for all my projects, putting each at ~/.claude/skills/<skill name> (in Codex use ~/.agents/skills/<skill name>, in Cursor ~/.cursor/skills/<skill name>). Folders in the repo: api-and-interface-design = skills/api-and-interface-design · browser-testing-with-devtools = skills/browser-testing-with-devtools · ci-cd-and-automation = skills/ci-cd-and-automation · code-review-and-quality = skills/code-review-and-quality · code-simplification = skills/code-simplification · context-engineering = skills/context-engineering · debugging-and-error-recovery = skills/debugging-and-error-recovery · deprecation-and-migration = skills/deprecation-and-migration · documentation-and-adrs = skills/documentation-and-adrs · doubt-driven-development = skills/doubt-driven-development · frontend-ui-engineering = skills/frontend-ui-engineering · git-workflow-and-versioning = skills/git-workflow-and-versioning · idea-refine = skills/idea-refine · incremental-implementation = skills/incremental-implementation · interview-me = skills/interview-me · observability-and-instrumentation = skills/observability-and-instrumentation · performance-optimization = skills/performance-optimization · planning-and-task-breakdown = skills/planning-and-task-breakdown · security-and-hardening = skills/security-and-hardening · shipping-and-launch = skills/shipping-and-launch · source-driven-development = skills/source-driven-development · spec-driven-development = skills/spec-driven-development · test-driven-development = skills/test-driven-development · using-agent-skills = skills/using-agent-skills. First show me every file and tell me whether any has scripts or changes machine settings, then tell me the full path you will install each one to and wait for me to agree.
Please install all 24 skills from https://github.com/addyosmani/agent-skills: api-and-interface-design, browser-testing-with-devtools, ci-cd-and-automation, code-review-and-quality, code-simplification, context-engineering, debugging-and-error-recovery, deprecation-and-migration, documentation-and-adrs, doubt-driven-development, frontend-ui-engineering, git-workflow-and-versioning, idea-refine, incremental-implementation, interview-me, observability-and-instrumentation, performance-optimization, planning-and-task-breakdown, security-and-hardening, shipping-and-launch, source-driven-development, spec-driven-development, test-driven-development, using-agent-skills, into the project this chat is open in (at .claude/skills/<skill name>; in Codex use .agents/skills/<skill name>, in Cursor .cursor/skills/<skill name>). Folders in the repo: api-and-interface-design = skills/api-and-interface-design · browser-testing-with-devtools = skills/browser-testing-with-devtools · ci-cd-and-automation = skills/ci-cd-and-automation · code-review-and-quality = skills/code-review-and-quality · code-simplification = skills/code-simplification · context-engineering = skills/context-engineering · debugging-and-error-recovery = skills/debugging-and-error-recovery · deprecation-and-migration = skills/deprecation-and-migration · documentation-and-adrs = skills/documentation-and-adrs · doubt-driven-development = skills/doubt-driven-development · frontend-ui-engineering = skills/frontend-ui-engineering · git-workflow-and-versioning = skills/git-workflow-and-versioning · idea-refine = skills/idea-refine · incremental-implementation = skills/incremental-implementation · interview-me = skills/interview-me · observability-and-instrumentation = skills/observability-and-instrumentation · performance-optimization = skills/performance-optimization · planning-and-task-breakdown = skills/planning-and-task-breakdown · security-and-hardening = skills/security-and-hardening · shipping-and-launch = skills/shipping-and-launch · source-driven-development = skills/source-driven-development · spec-driven-development = skills/spec-driven-development · test-driven-development = skills/test-driven-development · using-agent-skills = skills/using-agent-skills. First show me every file and tell me whether any has scripts or changes machine settings, then tell me the project name and the full path you will install each one to and wait for me to agree.

Uploading to Claude on the web and apps: you need 24 uploads, one ZIP per skill. Open each skill in the list below to download it

Checked against official docs 2026年11月12日 · Source: support.claude.com, code.claude.com, learn.chatgpt.com, cursor.com

  • api-and-interface-design

    Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

  • browser-testing-with-devtools

    Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools M…

  • ci-cd-and-automation

    Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.

  • code-review-and-quality

    Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch. Use when asked to review a diff or a pull request, even when…

  • code-simplification

    Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity. Use when asked to simplify, clean up, or reduce the ne…

  • context-engineering

    Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.

  • debugging-and-error-recovery

    Guides systematic root-cause debugging. Use when tests fail, builds break, something that worked yesterday broke, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need to figure out what broke and why — a systematic approach to finding and fixing the root cau…

  • deprecation-and-migration

    Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether t…

  • documentation-and-adrs

    Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

  • doubt-driven-development

    Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stake…

  • frontend-ui-engineering

    Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-gen…

  • git-workflow-and-versioning

    Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work acr…

  • idea-refine

    Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine t…

  • incremental-implementation

    Delivers changes incrementally in thin, verifiable slices. Use when implementing any feature or change that touches more than one file, or when picking up the next task from a plan. Use when rolling a change out behind a feature flag, when you're about to write a large amount of code at once, or wh…

  • interview-me

    Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly inv…

  • observability-and-instrumentation

    Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the availab…

  • performance-optimization

    Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.

  • planning-and-task-breakdown

    Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

  • security-and-hardening

    Hardens code against vulnerabilities. Use when auditing an input handler for vulnerabilities, when handling user input, authentication, data storage, or external integrations, or when checking a login flow is safe against the OWASP Top Ten. Use when building any feature that accepts untrusted data,…

  • shipping-and-launch

    Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

  • source-driven-development

    Grounds every implementation decision in official documentation. Use when you want to verify an approach against the official docs before implementing it, or when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness…

  • spec-driven-development

    Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single req…

  • test-driven-development

    Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality. Use when asked to add tests to a…

  • using-agent-skills

    Discovers and invokes agent skills. Use when starting a session, or when you need to decide which skill or workflow applies to the piece of work at hand. This is the meta-skill that governs how all other skills are discovered and invoked.

Skill と MCP の違い

MCP = 手

AI を外部のサービスやデータにつなぎます(例:Notion を読む、請求書を作る)。プログラムやサーバーが動いている必要があります。

Skill = 手順書

作業のやり方を AI に教えるテキストファイル。どのサービスにもつながりません。

重なる部分もあります。ツールを呼ぶスクリプト付きの Skill や、知識だけを渡す MCP もあります。やりたい作業から選んでください。

使えるアプリ

Claude CodeCodexCursorGemini CLIGitHub CopilotWindsurfOpenCodeKiro

提供元の README と repo のフォルダから判断

インストール

Pick a skill first

This repo has 24 skills. Pick one from the list above; its page shows every way to install it, including letting the AI install it and a ZIP

Let the AI install it
Upload to claude.ai

Go to the skill list ↑

The maker’s command installs the whole set of 24
Node.js を入れる(まだなければ)

もう入っていますか?先に確認 · ターミナルを開き、このコマンドを入力して Enter

node -v
  • バージョン番号(例 v26.13.1)が出る = 入っています。この手順は飛ばせます
  • "command not found"(Windows では "is not recognized")が出る = まだ入っていないか、入れた直後でターミナルを開き直す必要があります
ターミナルの開き方

Mac:⌘ + Space を押し、Terminal と入力して Enter

Windows:スタートメニューを開き、Windows PowerShell と入力して「開く」

まだ入っていない場合: 公式ダウンロードページで LTS 版と、クリックで進むインストーラーを選びます:Mac は .pkg、Windows は .msi。ダブルクリックして最後まで進めるだけで、curl コマンドは不要です

Node.js のダウンロードページを開く ↗

入れ終わったらターミナルを閉じて開き直し、同じコマンドをもう一度実行します。バージョン番号が出れば完了です: node -v

一度入れれば、Node.js を使うすべてのツールで使えます

npx skills add addyosmani/agent-skills

提供元の README から引用。提供元のコードをダウンロードして実行します

話し合い

質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。

まだ投稿はありません。最初の質問や共有をどうぞ。

ここの投稿は利用者によるもので、PopNx チームのものではありません。

ログインして投稿

GitHub の情報

GitHub スター
118,797
Stars are for the whole repo, not each skill
提供元
addyosmani
ライセンス
MIT
最終コード更新
2026年11月14日
repo 内の SKILL.md(翻訳版とテンプレートを含む)
24
トピック
agent-skills, antigravity, claude-code, codex, cursor, skills