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

ctx Skill

リポジトリ ↗

作者:stevesolun★ 593 (whole repo)58 個の skill

★ Stars are for the whole repo, not each skill

Pick the skill to install

What it does

This repo is a collection of 58 skills

  • Connects Instruction files the AI reads
  • Account or key Not confirmed yet (README not read yet)
  • Category コーディング
Maker’s original description
CTX Fit finds the cheapest AI coding setup that reliably works on your repository, then applies the winner as a reviewable change.
作者向け:README にバッジを付ける

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

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

一緒に使える

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

REA

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

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

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

Fallow

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

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

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

似た Skill

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

似たものと比べる
これ
ctx
reaandrej-karpathy-skillsgraphifyMoneyPrinterTurbo
作者stevesolunmorlutomultica-aiGraphify-Labsharry0703
Skill 数581111
GitHub スター593463,670233,682148,887143,987
最終コード更新2026年10月15日2026年11月17日2026年4月20日2026年11月17日2026年11月16日
ライセンスMITMIT–Apache-2.0MIT

stevesolun による 58 個の 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 58 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 58 See all on GitHub

  • agents-md-protocol

    Create or review an AGENTS.md file so coding agents get stable repo-local instructions: environment setup, testing, style, security boundaries, PR policy, and handoff rules. Use when a repo lacks durable agent guidance or when a custom harness needs a predictable context file.

  • ask-matt

    Recommend the smallest Matt Pocock skill or short skill sequence that fits the user's current goal.

  • cavecrew

    Decision guide for delegating to caveman-style subagents. Tells the main thread WHEN to spawn `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit), or `cavecrew-reviewer` (diff review) instead of doing the work inline or using vanilla `Explore`. Subagent output is caveman-compr…

  • caveman

    Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tok…

  • caveman-commit

    Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /cave…

  • caveman-compress

    Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman-compress…

  • code-review

    Review a Git diff against repository standards and its originating requirements. Use for pull requests, branches, work-in-progress changes, or changes since a commit, tag, or merge-base.

  • codebase-design

    Design or improve module interfaces using deep-module heuristics. Use when deciding where a seam belongs, reducing caller-facing complexity, improving testability or navigability, or comparing module designs.

  • ctx-dispatch

    Coordinate nontrivial work in the ctx repository when a task has independent investigation, implementation, or test lanes; compute-heavy checks; or repetitive changes suited to scripts or codemods. Use for decomposition and concurrency decisions, not simple edits or questions.

  • ctx-verify

    Select proportional validation for changes or reviews in the ctx repository. Use before handing off material code, workflow, migration, documentation, security, packaging, or release changes; before a PR; or when asked whether a change is adequately tested. Do not use for pure questions with no cha…

  • diagnosing-bugs

    Diagnose hard bugs and performance regressions with reproducible evidence, focused hypotheses, and proportional instrumentation. Use when something is broken, failing, throwing, intermittently wrong, or unexpectedly slow.

  • docs

    Repo-aware recommendation manager for ctx. Scans the active repository, identifies stack and workflow signals, recommends a capped set of skills, agents, and MCP servers, and unloads helpers that no longer match the current work after user confirmation. Harnesses are recommended by the custom-model…

  • domain-modeling

    Clarify domain concepts, language, boundaries, and durable architectural decisions. Use when terminology is ambiguous, the user is shaping a domain model, or a design depends on resolving what concepts mean.

  • grill-me

    A relentless interview to sharpen a plan or design.

  • grill-with-docs

    A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

  • grilling

    Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

  • handoff

    Compact the current conversation into a handoff document for another agent to pick up.

  • implement

    Implement work from a spec, ticket, or agreed conversation. Use explicitly when the user wants an existing plan carried through to working code.

  • improve-codebase-architecture

    Analyze a codebase for high-leverage architectural improvements and explain evidence, tradeoffs, and next steps. Use explicitly for architecture audits or deep-module refactoring opportunities.

  • prototype

    Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

  • research

    Investigate questions using high-trust primary sources and traceable citations. Use when the user asks for research, current documentation or API facts, source verification, or evidence-backed comparison.

  • resolving-merge-conflicts

    Resolve an in-progress Git merge or rebase conflict while preserving the relevant intent of both sides. Use when conflict markers or an interrupted merge/rebase need investigation and resolution.

  • setup-matt-pocock-skills

    Configure repository-local tracker, triage, and domain-document conventions needed by the Matt Pocock engineering skills.

  • tdd

    Apply test-driven development with small, behavior-focused feedback loops. Use when the user asks to build or fix something test-first, mentions red-green-refactor, or wants integration tests.

  • teach

    Teach a skill or concept at the user's current level, optionally preserving a lightweight multi-session learning record.

  • to-spec

    Synthesize an implementation-ready spec from the current conversation and relevant repository context. Use explicitly when the user wants agreed work captured as a spec or PRD.

  • to-tickets

    Break a plan, spec, or conversation into dependency-aware, independently verifiable tickets. Use explicitly when the user wants work sliced for local planning or an issue tracker.

  • triage

    Classify and advance issues or external pull requests through the configured triage workflow. Use explicitly to inspect queues, evaluate an item, recommend a state, or apply an authorized transition.

  • wayfinder

    Map a large, unclear, multi-session effort as linked decisions, then advance the map until the route to the destination is clear.

  • writing-great-skills

    Design or revise concise skills with clear triggers, proportional constraints, progressive disclosure, and realistic validation.

Skill と MCP の違い

MCP = 手

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

Skill = 手順書

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

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

使えるアプリ

Claude CodeCodex

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

インストール

Pick a skill first

This repo has 58 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 ↑

話し合い

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

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

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

ログインして投稿

GitHub の情報

GitHub スター
593
Stars are for the whole repo, not each skill
提供元
stevesolun
ライセンス
MIT
最終コード更新
2026年10月15日
repo 内の SKILL.md(翻訳版とテンプレートを含む)
30
トピック
agents, ai-agents, anthropic, automation, claude, claude-code, context-management, developer-tools, harness, knowledge-graph, llm, llm-wiki