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

pstack-claude Skill

作者:michael-denyer★ 4,346 (whole repo)54 個の skill

★ Stars are for the whole repo, not each skill

Pick the skill to install

What it does

This repo is a collection of 54 skills

  • Connects Instruction files the AI reads; connects to nothing
  • Account or key No key needed
  • Category コーディング
Maker’s original description
Antigravity, Claude Code, Codex, Copilot, Gemini, Muse, OpenCode, Pi, and Prime Agent versions of Poteto's pstack. Rigorous agent workflows with Cursor primitives translated for other harnesses.
作者向け:README にバッジを付ける

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

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/michael-denyer-pstack-claude.svg)](https://mcp.popnx.com/en/skills/michael-denyer-pstack-claude)

一緒に使える

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

REA

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

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

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

Fallow

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

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

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

Desktop Commander

MCP server for terminal commands, file operations, and process management

作者:wonderwhy-er広く使われている↓ 74万/週★ 1万4 日前更新

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

似た Skill

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

似たものと比べる
これ
pstack-claude
reagraphifyarchifysecurity-audit-skill
作者michael-denyermorlutoGraphify-Labstt-a1icloudflare
Skill 数541111
GitHub スター4,346461,751148,35296,75773,156
最終コード更新2026年11月13日2026年11月16日2026年11月16日2026年11月15日2026年9月15日
ライセンスMITMITApache-2.0Apache-2.0MIT

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

Pick the skill to install

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

This set has 54 skills, too many to install at once: every installed skill’s description loads into every chat, so the AI picks the wrong one more easily. Pick only the ones you use from the list below

Showing 30 of 54 See all on GitHub

  • architect

    Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.

  • arena

    Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.

  • automate-me

    Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via plugin-dev:skill-development + unslop, optionally pulling fresh evidence from rece…

  • babysit

    Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.

  • blast-radius

    Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', reviewing a small diff you don't trust, or a brief that asserts something…

  • bro

    Restate the last message in plain human language, with no jargon. Use for /bro or when asked to say it plainly.

  • create-verification-skill

    Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", "make a driver skill for this repo", or when a project has no scripted way to prove UI/CLI/service b…

  • deslop

    Remove AI-generated code slop and clean up code style

  • figure-it-out

    Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions. Use for /figure-it-out or 'figure it out'.

  • fix-ci

    Find failing PR checks, inspect logs or external check links, and apply focused fixes

  • fix-merge-conflicts

    Resolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolution

  • get-pr-comments

    Fetch and summarize review comments from the active pull request

  • how

    Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.

  • interrogate

    Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Adversaries try to break a change or design, and only findings proven by a run survive.

  • maintain-verification-skill

    Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".

  • make-pr-easy-to-review

    Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff".

  • no-comments

    Spawn the comment-sicko subagent, fix accepted findings, and offer encodings for claimed constraints.

  • poteto-mode

    poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.

  • principle-attack-the-premise

    Apply when two or more fixes that share one premise have failed the same gate. Write the premise down and test it directly before you write another fix that assumes it.

  • principle-boundary-discipline

    Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.

  • principle-build-the-lever

    Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.

  • principle-encode-lessons-in-structure

    Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.

  • principle-exhaust-the-design-space

    Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.

  • principle-experience-first

    Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.

  • principle-fix-root-causes

    Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is legitimate.

  • principle-foundational-thinking

    Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.

  • principle-guard-the-context-window

    Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.

  • principle-laziness-protocol

    Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.

  • principle-make-operations-idempotent

    Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.

  • principle-migrate-callers-then-delete-legacy-apis

    Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.

Skill と MCP の違い

MCP = 手

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

Skill = 手順書

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

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

使えるアプリ

Claude CodeCodexCursorGemini CLIGitHub CopilotOpenCode

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

インストール

Pick a skill first

This repo has 54 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 54

コマンドを確認中 · 確認が通るとコピーボタンが出ます

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

話し合い

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

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

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

ログインして投稿

GitHub の情報

GitHub スター
4,346
Stars are for the whole repo, not each skill
提供元
michael-denyer
ライセンス
MIT
最終コード更新
2026年11月13日
repo 内の SKILL.md(翻訳版とテンプレートを含む)
30
トピック
agent-plugin, agent-skills, agentic-ai, anthropic, antigravity-skills, chatgpt, claude, claude-code, claude-code-skills, claude-plugin, claude-skills, code-review