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

claude-night-market Skill

リポジトリ ↗

作者:athola★ 350 (リポジトリ全体)197 個の skill

★ スターはリポジトリ全体のもので、各 Skill のものではありません

インストールする Skill を選ぶ

できること

このリポジトリは 197 個の Skill をまとめたものです。複数の出どころの Skill をまとめた一覧です

  • 接続方法 AI が読む指示ファイルで、外部サービスを呼び出す手順を含みます
  • アカウントまたはキー GitHub, GH_TOKEN のキーが必要な手順があります(README より)
  • カテゴリ コーディング
作者の元の説明
23 Claude Code plugins: TDD enforcement hooks, git/PR workflows, spec-driven development, code review, project lifecycle, fix-from-error, maintenance automation, context optimization, research, and multi-LLM delegation. 186 skills, 128 commands, 54 agents.
作者向け:README にバッジを付ける

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

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/athola-claude-night-market.svg)](https://mcp.popnx.com/en/skills/athola-claude-night-market)

一緒に使える

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

REA

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

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

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

Fallow

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

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

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

似た Skill

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

似たものと比べる
これ
claude-night-market
reaandrej-karpathy-skillsgraphifyMoneyPrinterTurbo
作者atholamorlutomultica-aiGraphify-Labsharry0703
Skill 数1971111
GitHub スター350468,733234,332150,287144,566
最終コード更新2026年11月19日2026年11月19日2026年4月20日2026年11月18日2026年11月18日
ライセンスMITMIT–Apache-2.0MIT

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

インストールする Skill を選ぶ

使うものだけをインストールしましょう。名前を開くとその Skill のインストール方法が見られます

このセットは 197 個もあり、全部入れるには多すぎます。Skill の説明は毎回のチャットに読み込まれるため、AI が違う Skill を選びやすくなります。下の一覧から使うものだけを選んでください

  • additive-bias-defense

    Inverts burden of proof for code additions. Use when reviewing PRs, planning refactors, or running unbloat to challenge every addition's necessity.

  • agent-expenditure

    Tracks per-agent token usage and flags waste in parallel dispatch. Use when evaluating parallel agent efficiency or after a multi-agent run.

  • agent-teams

    Coordinates Claude agent teams over a filesystem protocol. Use for parallel agents with task dependencies.

  • api-review

    Evaluates API surface design, consistency, and exemplar alignment. Use when reviewing public API changes or before releasing a new API surface.

  • architecture-aware-init

    Selects architecture paradigm via research before scaffolding. Use when architecture is undecided and the choice needs justification and documentation.

  • architecture-diagram

    Generates a Mermaid architecture diagram showing high-level component relationships. Use when visualizing how plugins or modules fit together.

  • architecture-paradigm-client-server

    Applies client-server architecture for web/mobile apps. Use when designing systems with centralized backend services, trust boundaries, or offline-first sync.

  • architecture-paradigm-cqrs-es

    CQRS and Event Sourcing. Use when reads and writes need separate models or every state change needs an audit trail.

  • architecture-paradigm-event-driven

    Event-driven async messaging. Use when real-time or multi-subscriber systems need producers decoupled from consumers.

  • architecture-paradigm-functional-core

    Applies Functional Core, Imperative Shell to isolate logic from side effects. Use when business logic is entangled with I/O or unit tests are slow and brittle.

  • architecture-paradigm-hexagonal

    Hexagonal ports-and-adapters architecture. Use when the domain must stay testable apart from infrastructure.

  • architecture-paradigm-layered

    Layered n-tier architecture. Use for moderate systems needing presentation, domain, and persistence layers.

  • architecture-paradigm-microkernel

    Microkernel architecture with a minimal core and plugins. Use when third parties extend a platform's core.

  • architecture-paradigm-microservices

    Applies microservices for independent deployment and per-service scaling. Use when teams need autonomous release cycles with distinct capability scaling needs.

  • architecture-paradigm-modular-monolith

    Modular monolith with enforced internal boundaries. Use for service-level autonomy without a distributed system.

  • architecture-paradigm-pipeline

    Pipes-and-filters architecture. Use when data flows through discrete stages such as ETL, streaming, or CI/CD.

  • architecture-paradigm-serverless

    Serverless FaaS patterns. Use for bursty event-driven workloads with pay-per-execution cost and little infrastructure.

  • architecture-paradigm-service-based

    Applies coarse-grained service architecture for deployment independence. Use when independent deployment is needed but shared databases rule out microservices.

  • architecture-paradigm-space-based

    Applies data-grid architecture for high-traffic stateful workloads. Use when a single database cannot scale and in-memory partitioning is needed.

  • architecture-paradigms

    Routes to the right architecture paradigm. Use when choosing patterns for a new system or comparing architecture trade-offs.

  • architecture-review

    Assesses architecture decisions, ADR compliance, and coupling. Use when evaluating design changes or validating structural decisions before merging.

  • assisted-mastery

    Makes agent reasoning visible, surfaces tradeoffs, and fades help so humans build judgment. Use when reviewing or learning from agent-written code.

  • authentication-patterns

    Provides auth patterns for API keys, OAuth, and token management. Use when implementing or reviewing service authentication and credential handling.

  • blast-radius

    Analyzes code change impact with risk scoring and affected-node mapping. Use before merging to understand what a change touches and what lacks test coverage.

  • bloat-detector

    Detects codebase bloat via dead code, duplication, complexity, and doc bloat scans. Use when codebase feels large or before a release.

  • browser-recording

    Records browser sessions with Playwright and converts them to GIF. Use for web UI demos and tutorials.

  • bug-review

    Hunts bugs with evidence trails. Use when investigating unexpected behavior or before merging code with potential hidden defects.

  • call-chain

    Traces execution paths through the code graph with criticality scoring and Mermaid charts. Use when understanding how a function propagates through the system.

  • catchup

    Summarizes recent git changes for context recovery after session breaks. Use when resuming work after a gap or handing off to another session.

  • challenge

    Presents adaptive codebase challenge questions with multiple-choice and trace exercises. Use when testing contributor knowledge of the codebase.

  • class-diagram

    Generates a Mermaid class diagram showing types, inheritance, and composition. Use when visualizing class hierarchies or documenting a module public API.

  • clear-context

    Manages context overflow by handing off to a fresh subagent at 80% usage. Use when context pressure is critical and work must continue uninterrupted.

  • code-communities

    Detects architectural clusters and coupling boundaries via community detection on the code graph. Use when identifying module groupings or refactoring targets.

  • code-quality-principles

    Applies KISS, YAGNI, and SOLID principles for clean code with reduced complexity. Use when refactoring or reviewing code for over-engineering.

  • code-refinement

    Improves code quality across duplication, efficiency, and architectural fit. Use when code passes tests but quality is poor or before a major release.

  • code-search

    Searches GitHub for existing implementations, libraries, or patterns. Use when finding code examples or prior art on a topic during a research session.

  • commit-messages

    Generates conventional commit messages from staged changes. Use when committing and needing a well-formatted message. For full PR prep, use pr-prep.

  • compression-strategy

    作者による説明はありません

  • computer-control

    Automates desktop GUI workflows through the computer use API with screenshots. Use when scripting GUI interactions.

  • content-sanitization

    Provides sanitization guidelines for external content in skills and hooks. Use when loading GitHub Issues, PRs, WebFetch results, or any untrusted input.

  • context-map

    作者による説明はありません

  • context-optimization

    Optimizes context window via MECW principles and memory tiering. Use when context exceeds 30% or before long multi-step tasks.

  • cpu-gpu-performance

    Establishes CPU/GPU baselines before resource-intensive operations. Use before builds, training runs, or any task that pins cores or GPUs for over a minute.

  • curate

    Adds developer-authored annotations to the gauntlet knowledge base. Use when capturing tribal knowledge or rationale not visible in code.

  • damage-control

    Recovers broken agent state via crash recovery, context overflow, and merge conflict protocols. Use when an agent session fails or a worktree is corrupted.

  • data-flow

    Generates a Mermaid sequence diagram showing how data moves between components. Use when tracing request flows or documenting data transformation pipelines.

  • decision-journal

    Decision journal (tradeoffs, lessons learned), deferred-capture contract ([Deferred] issues, CLI args, source labels), storage templates. Use to log a lesson.

  • decisive-action

    Guides when to ask clarifying questions versus proceed autonomously. Use to reduce unnecessary clarifying questions when intent is clear.

  • deferred-capture

    作者による説明はありません

  • delegation-core

    Delegates execution to external CLIs (Gemini, Qwen, MiniMax, GLM, Muse, Codex, OpenCode, Glimmer). Use for execution tasks. Do not use for secrets.

  • dependency-graph

    Generates a Mermaid dependency graph showing import relationships between modules. Use when analyzing coupling, finding circular deps, or planning refactors.

  • dependency-verification

    Verifies a package exists before install, defending against hallucination and slopsquatting. Use when adding, recommending, or installing a package.

  • development-workflow

    作者による説明はありません

  • diff-analysis

    Analyzes changesets with risk scoring, categorization by type and impact, and release note preparation. Use when extracting insights from raw change data.

  • dig

    Refines an active research session by drilling deeper into a subtopic. Use after tome:research to narrow results to a specific channel or angle.

  • digital-garden-cultivator

    Manages digital garden notes, link structures, and health metrics. Use when curating a knowledge base, pruning stale notes, or tracking content maturity.

  • discourse

    Scans HN, Lobsters, Reddit, and tech blogs for community experience reports. Use when gathering practitioner opinions on a technology or approach.

  • do-issue

    Implements GitHub or GitLab issues via parallel subagents with review gates between task batches. Use when resolving multi-step issues end-to-end.

  • doc-consolidation

    Merges ephemeral report and analysis artifacts into permanent documentation. Use when LLM-generated markdown files have accumulated and need consolidation.

  • doc-generator

    Generates or remediates documentation with human-quality writing. Use when creating new docs, rewriting AI-generated content, or applying style profiles.

  • doc-importer

    作者による説明はありません

  • doc-updates

    Updates documentation after code changes with quality gates, slop detection, and accuracy checks. Use when code changes require corresponding doc updates.

  • document-conversion

    Converts documents and URLs to markdown via tiered fallback (MCP markitdown, native tools, user notice). Use when a skill must ingest PDF, DOCX, or URL content.

  • dora-metrics

    Computes DORA delivery-performance metrics from git and GitHub API. Use when assessing deployment frequency, lead time, or change failure rate.

  • dorodango

    Polishes working code through successive quality passes in fresh subagents. Use after tests pass when code needs multi-dimension refinement before release.

  • error-patterns

    Provides error classification, recovery, and graceful-degradation patterns. Use when implementing error handling or debugging resilience failures in any skill.

  • escalation-governance

    Assess whether to escalate models. Use when evaluating reasoning depth.

  • evaluation-framework

    Weighted scoring, rubrics, thresholds, agent-action utility by expected gain and cost. Use for quality gates or deciding if a tool call or dispatch is worth it.

  • extract

    Builds the gauntlet knowledge base from AST extraction and AI enrichment. Use when initializing or refreshing codebase knowledge for challenges.

  • feature-review

    Scores backlog items with RICE/WSJF/Kano and files GitHub issues for top candidates. Use when triaging a roadmap or prioritizing features for a sprint.

  • file-analysis

    作者による説明はありません

  • friction-detector

    Detect friction signals; graduate patterns into rules. Use for session retrospectives.

  • gauntlet-curate

    作者による説明はありません

  • gemini-delegation

    Delegates to the Gemini CLI. Use when delegation-core selects Gemini or 1M+ token context is needed.

  • gif-generation

    Converts webm/mp4 to optimized GIFs with ffmpeg. Use when post-processing recordings into shareable GIFs.

  • git-platform

    Detects git forge (GitHub/GitLab/Bitbucket) and maps CLI commands cross-platform. Use when writing skills that must run on any git hosting provider.

  • git-workspace-review

    Verifies workspace state and staged changes as a read-only preflight. Use before commits or PRs to confirm staged set is clean and correct.

  • github-initiative-pulse

    Generates markdown digests and CSV exports for GitHub initiative health. Use when reporting on issue/PR progress across a milestone or project.

  • graduated-implementation

    Ramps implementation ambition a notch only after the prior increment is understood. Use when building a feature you must understand, not just ship.

  • graph-build

    Builds or updates the code knowledge graph via tree-sitter AST and SQLite. Use when setting up the graph before search or blast-radius analysis.

  • graph-search

    Searches the code knowledge graph by function, class, or type using FTS5 full-text search. Use when locating code entities by name or qualified path.

  • harden

    Applies NIST/CWE security hardening to Python and Rust code. Use when auditing code for vulnerabilities or proposing concrete security remediations.

  • hook-authoring

    Guide creating Claude Code hooks with security-first design. Use for validation and enforcement.

  • hook-scope-guide

    Select hook scope (plugin, project, global) by audience. Use when authoring a hook.

  • hooks-eval

    Evaluate hook security, performance, and SDK compliance. Use for audits.

  • ideate

    Generate diverse solution candidates with category-spanning ideation methods and rotation. Use when stuck on a design or fighting repetitive LLM output.

  • install-watchdog

    Installs egregore watchdog daemon via launchd or systemd for autonomous relaunching. Use when setting up egregore on a new machine. Do not use on CI/CD runners.

  • justify

    Audits changes for additive bias and Iron Law compliance. Use when reviewing completed work before merging or after AI-assisted implementation.

  • karpathy-principles

    Pre-implementation gate covering think-first, simplicity, surgical edits, and verifiable goals. Use when starting implementation to verify the approach.

  • knowledge-intake

    Processes external resources into stored knowledge with quality scoring and routing. Use when ingesting articles, papers, or docs into a memory palace.

  • knowledge-locator

    Searches and navigates stored knowledge in memory palaces. Use when looking for previously stored information or cross-referencing concepts across palaces.

  • latent-space-engineering

    Shapes agent behavior via instruction framing and style transfer. Use when composing dispatch prompts or writing skill instructions for parallel review agents.

  • makefile-generation

    Generates Makefiles with testing, linting, formatting, and automation targets. Use when starting a project or standardizing build automation.

  • makefile-review

    作者による説明はありません

  • markdown-formatting

    Enforces markdown line-wrap and structure rules for clean git diffs. Use when writing or editing any committed markdown documentation or skill file.

  • math-review

    Verifies math-heavy code for algorithmic correctness and numerical stability. Use when reviewing scientific algorithms, ML models, or numerical code.

  • mcp-code-execution

    Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

  • media-composition

    Combines GIFs and videos into vertical or grid composites with ffmpeg. Use for multi-part tutorial media.

  • memory-clarity-probe

    Probe memory/summary clarity via dual anchor questions: task progress, info gaps. Use when verifying session state or summary before handoff or compression.

  • memory-palace-architect

    Designs memory palace structures with spatial layouts and domain organization. Use when creating a new palace or planning knowledge architecture by hand.

  • metacognitive-self-mod

    Analyze and improve the improvement process. Use for detecting regressions and meta-optimization.

  • methodology-curator

    Surface expert frameworks. Use when creating or evaluating skills, hooks, or agents.

  • mission-orchestrator

    Orchestrates full project lifecycle by auto-detecting state and routing to the correct phase. Use when starting or resuming a project mid-workflow.

  • modular-skills

    Build composable skill modules with hub-and-spoke loading. Use when token budget is tight.

  • onboard

    Guides a new developer through five staged challenge sets covering architecture, domain, patterns, and hardening. Use when onboarding contributors.

  • palace-diagram

    Generates Mermaid and ASCII diagrams of palace structure, knowledge topology, and synapse connectivity. Use when inspecting or presenting a palace visually.

  • palace-index-curator

    Curate the web-capture index. Use when the capture backlog grows, captures sit unprocessed at seedling/pending, or to surface stored research during work.

  • papers

    Searches academic literature via arXiv, Semantic Scholar, and open-access PDFs. Use when building literature reviews or finding formal research on a topic.

  • performance-review

    Detects time and space complexity hotspots via AST scan. Use when code feels slow, before performance-sensitive merges, or to find O(n²) regressions.

  • plugin-review

    Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.

  • pr-prep

    Prepares pull requests by running quality gates, drafting descriptions, and validating tests. Use when completing a feature and ready for review.

  • pr-review

    Reviews pull requests with scope validation, requirements compliance, and line comments. Use when reviewing GitHub or GitLab PRs.

  • precommit-setup

    Configures pre-commit hooks for linting, type checking, formatting, and testing. Use when setting up a new project or adding quality gates to an existing one.

  • progressive-loading

    Implements hub-and-spoke lazy loading to minimize token usage in large skills. Use when building multi-module skills that need conditional on-demand loading.

  • project-brainstorming

    Guides project ideation via Socratic questioning to produce a validated brief. Use before specification when requirements are unclear.

  • project-execution

    Executes implementation plans with progress tracking, checkpoint validation, and quality gates. Use after planning is complete and tasks are ready to implement.

  • project-init

    Scaffolds new projects with git, CI/CD workflows, pre-commit hooks, and build config. Use when starting a new Python, Rust, or TypeScript project from scratch.

  • project-planning

    Converts a specification into a phased, dependency-ordered implementation plan. Use after specification is complete and before execution begins.

  • project-specification

    Transforms project briefs into testable specifications with user stories and acceptance criteria. Use after brainstorming, before planning.

  • proof-of-work

    Enforces validation and evidence before claiming work complete. Use before declaring implementation done, creating a PR, or submitting deliverables for review.

  • pytest-config

    作者による説明はありません

  • python-async

    Async Python patterns via asyncio and aiohttp for I/O-bound concurrency. Use when adding async APIs, handling concurrent I/O, or debugging async code.

  • python-packaging

    Python package creation and PyPI distribution via pyproject.toml and entry points. Use when publishing a package or setting up build configuration.

  • python-performance

    Profiles Python code for performance bottlenecks and memory issues. Use when Python code is slow or when profiling for optimization before a release.

  • python-testing

    Python testing patterns with pytest, fixtures, TDD, mocking, async and integration tests. Use when writing or auditing a Python test suite.

  • quality-gate

    Orchestrates the QUALITY pipeline stage for egregore work items, running code review, unbloat, and test updates. Use when running quality checks before a PR.

  • quota-management

    作者による説明はありません

  • qwen-delegation

    Delegates to the Qwen CLI (Alibaba). Use when delegation-core selects Qwen or for large-context batch work.

  • release-health-gates

    Standardizes release approvals with GitHub-aware checklists and deployment gates. Use before releasing to production to verify all gates pass.

  • research

    Runs multi-source research across GitHub, HN, Reddit, arXiv, and Semantic Scholar. Use when surveying a technical topic across multiple channels.

  • response-compression

    Compresses verbose responses by removing filler and framing to save 200-400 tokens. Use when responses feel bloated or context is filling fast.

  • review-chamber

    Captures and retrieves PR-review findings in memory palaces. Use after PR review to store architectural decisions, patterns, and standards for future reference.

  • review-core

    Provides review-workflow scaffolding for context, evidence, and output. Use at the start of any detailed review to ensure consistent, comparable findings.

  • rigorous-reasoning

    Applies anti-sycophancy checklist to override agreement bias. Use when analyzing contested claims or avoiding socially convenient but inaccurate conclusions.

  • risk-classification

    Classifies agent tasks into 4 risk tiers (GREEN/YELLOW/RED/CRITICAL). Use when assessing action reversibility before committing to an approach.

  • rule-catalog

    Browse hookify rule catalog. Use when installing pre-built rules or browsing categories. Do not use when writing custom rules; use hookify:writing-rules.

  • rules-eval

    Evaluate Claude Code rules in .claude/rules/. Use for frontmatter, globs, and quality audits.

  • rust-review

    Audits Rust code for unsafe blocks, ownership issues, and Cargo dependency risks. Use when reviewing Rust code or before merging Rust changes.

  • safety-critical-patterns

    Applies NASA Power of 10 rules for safety-critical verifiable code. Use when auditing financial, medical, or high-reliability system code.

  • scope-guard

    Scores feature worthiness and enforces branch-size limits against overengineering. Use when evaluating whether a feature belongs in the current scope or branch.

  • sem-integration

    Provides sem semantic-diff detection, install-on-first-use, and fallback patterns. Use when building skills that consume git diff output.

  • service-registry

    Registers external services with health checks, quotas, and a usage logger for per-call cost and sessions. Use when adding rate-limited APIs or logging usage.

  • session-management

    Manages Claude Code sessions with naming, checkpointing, and resume strategies. Use when organizing long-running work or resuming across sessions.

  • session-palace-builder

    Builds session-scoped temporary memory palaces for extended conversations. Use when tracking state across interruptions in a multi-step project.

  • session-replay

    Converts a Claude Code session JSONL file into an animated GIF terminal replay. Use when creating demos or visual evidence from past sessions.

  • session-to-post

    Converts a Claude Code session into a blog post, case study, or Reddit post. Use when publishing dev blog content or community posts from real sessions.

  • setup

    Provisions the oracle ML inference daemon with onnxruntime via uv. Use when setting up local ONNX model inference for skill quality evaluation.

  • shared-patterns

    作者による説明はありません

  • shell-review

    作者による説明はありません

  • skill-authoring

    Guide creating Claude Code skills with TDD and persuasion principles. Use for new skill development.

  • skill-graph-audit

    Audit Skill() refs; detect hubs, isolates, and dangling targets. Use when auditing skills.

  • skills-eval

    Evaluate Claude skill quality through auditing. Use when reviewing or auditing skills.

  • slop-detector

    Detects AI-generated writing patterns in prose. Use when reviewing docs for slop, vague language, or identity leaks before publishing.

  • smart-sourcing

    作者による説明はありません

  • spec-writing

    Creates clear, testable specifications from feature descriptions with user stories. Use when starting a new feature and needing a spec before planning.

  • speckit-orchestrator

    Orchestrates Spec Driven Development by coordinating spec, plan, and task skills. Use when running the full speckit workflow from spec to implementation.

  • stack-create

    Initializes a stacked branch set from an ordered plan, one branch per slice with parent-child links. Use when a plan has 2+ sequentially dependent changes.

  • stack-mode

    Detects shared stack membership and iterates a command across all PRs in base-to-tip order. Use when a command supports --stack flag for multi-PR iteration.

  • stack-push

    Pushes all branches in a stack and opens or updates one dependent PR per slice. Use after stack-create to publish the stack or after adding commits to a slice.

  • stack-rebase

    Cascades a rebase through an entire PR stack after a base PR merges or upstream changes. Use when a stack needs to incorporate new base branch commits.

  • stewardship

    Applies stewardship virtues (Care, Curiosity, Humility, Diligence) to plugin work. Use when authoring plugins or reviewing code quality.

  • storage-templates

    作者による説明はありません

  • structured-output

    Formats review deliverables with consistent structure for comparable findings. Use when finalizing any review or analysis that must be shared or compared.

  • style-learner

    Extracts writing style patterns from exemplar text into a reusable profile. Use when creating a style guide or learning a specific author's voice.

  • subagent-testing

    Test skills via TDD in fresh subagents. Use when validating behavior or preventing bias.

  • summon

    Autonomous orchestrator for manifest work items through the development lifecycle. Use when running egregore to process a backlog automatically.

  • supply-chain-advisory

    Audits dependency supply chains for bad versions, lockfile drift, and artifact integrity. Use when adding deps, handling incidents, or releasing a plugin.

  • synthesize

    Merges, dedupes, ranks, and formats research findings into a report. Use after research agents return results from multiple channels to produce a ranked report.

  • task-planning

    Generates phased, dependency-ordered tasks from a specification. Use after the spec, before implementation.

  • tech-tutorial

    Plans, drafts, and refines technical tutorials for developers. Use when writing step-by-step guides or getting-started walkthroughs backed by working code.

  • test-review

    Evaluates test suites for coverage gaps, TDD/BDD compliance, and anti-patterns. Use when auditing test quality or before a major release.

  • test-updates

    Updates, generates, and validates tests using git-workspace context and TDD/BDD methodology. Use when code changes require new or updated test coverage.

  • testing-quality-standards

    Defines test quality metrics, coverage thresholds, anti-patterns, and pytest config. Use when setting test gates, a suite's coverage target, or pytest fixtures.

  • tiered-audit

    Runs a three-tier codebase audit (git history, targeted scans, full review) with gating. Use when auditing a codebase before release or after incidents.

  • token-conservation

    Enforces token quota management at session start with conservation and compression checks. Use at the start of every session or before large context loads.

  • triz

    Applies TRIZ cross-domain analogical reasoning to find solutions from adjacent fields. Use when stuck on a problem and needing inventive perspectives.

  • tutorial-updates

    Generates or updates tutorials from VHS tapes and Playwright specs with dual-tone markdown and GIF recording. Use when tutorial assets need refreshing.

  • unified-review

    Orchestrates multi-domain review (code, arch, tests, security) in a single pass. Use when thorough pre-release review is needed.

  • uninstall-watchdog

    Removes the egregore watchdog daemon and its associated files. Use when stopping automated session relaunching or cleaning up egregore infrastructure.

  • update-readme

    Refreshes README structure favoring concision (an index, not a manual). Use when the README needs a structural update after significant project changes.

  • usage-logging

    作者による説明はありません

  • utility

    作者による説明はありません

  • validate-pr

    Generates and self-executes a diff-derived test plan for a PR. Use when validating PR changes before merge. Do not use for code review; use sanctum:pr-review.

  • version-updates

    Bumps versions, updates changelogs, and coordinates version changes across files for releases. Use when preparing a release or bumping the project version.

  • vhs-recording

    Generates terminal recordings using VHS tape scripts and produces GIF outputs. Use when creating demo GIFs or documenting CLI workflows for tutorials.

  • voice-extract

    Extracts a user's writing voice from text samples via SICO comparative analysis. Use when building a voice profile for consistent generation.

  • voice-generate

    Generates text in a learned writing voice. Use when drafting content that must match a specific author's style profile extracted by voice-extract.

  • voice-learn

    Improves a voice profile by learning from manual edits. Use after editing generated text to refine registers and close voice drift over time.

  • voice-review

    Runs parallel prose and craft review agents against a voice profile. Use when checking generated content for AI patterns and voice drift before publishing.

  • vow-enforcement

    Classifies and enforces constraints via soft vows, hard vows, and Nen Court layers. Use when designing or auditing enforcement mechanisms for project rules.

  • war-room

    Convenes a multi-LLM expert panel to pressure-test hard-to-reverse decisions. Use when reversibility score is low and adversarial review is warranted.

  • war-room-checkpoint

    Assesses decision reversibility and risk at critical checkpoints. Use when a workflow reaches a high-stakes branch needing escalation check.

  • workflow-diagram

    Generates a Mermaid workflow diagram showing process steps, decisions, and state transitions. Use when documenting CI/CD pipelines or lifecycle processes.

  • workflow-improvement

    Evaluates and improves skills, agents, commands, and hooks after a workflow slice. Use when execution felt slow, confusing, repetitive, or fragile.

  • workflow-monitor

    Detects workflow failures and inefficient patterns then files GitHub issues. Use when a workflow step repeatedly fails or produces inconsistent output.

  • workflow-setup

    Configures GitHub Actions CI/CD workflows for testing, linting, and deployment. Use when setting up automation for a Python, Rust, or TypeScript project.

  • writing-rules

    Writes hookify rules in markdown that block dangerous commands or restrict AI behavior. Use when adding guardrails.

Skill と MCP の違い

MCP = 手

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

Skill = 手順書

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

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

使えるアプリ

Claude CodeCodexOpenCode

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

インストール

まず Skill を選んでください

このリポジトリには 197 個の Skill があります。上の一覧から選ぶと、その Skill のページに AI にインストールしてもらう方法や ZIP など、すべてのインストール方法が出ます

AI にインストールしてもらう
claude.ai にアップロード

Skill 一覧へ ↑

作者のコマンドで 197 個すべてインストールされます

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

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

話し合い

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

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

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

ログインして投稿

GitHub の情報

GitHub スター
350
スターはリポジトリ全体のもので、各 Skill のものではありません
提供元
athola
ライセンス
MIT
最終コード更新
2026年11月19日
repo 内の SKILL.md(翻訳版とテンプレートを含む)
197
トピック
ai-agents, architecture-patterns, awesome-claude-code, awesome-claude-skills, claude-agents, claude-code, claude-code-plugins, claude-code-plugins-marketplace, claude-commands, claude-hooks, claude-skills, code-review