Surface Claude's assumptions about an objective approach before planning. Specialized diagnostic tool for reviewing AI assumptions.
Skills in this repository
majiayu000/claude-skill-registry - Page 51
SkillsMP has collected 5,485 skills from majiayu000/claude-skill-registry. Open a skill to review its source and details.
majiayu000/claude-skill-registryShowing 40 of 5,485 collected skills.
Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents and CLAUDE.md. Use when the user wants to understand, analyze, or map an existing codebase. Triggers on: "understand this codebase", "map the code", "analyze architecture",…
Research how to implement an objective before planning. Use when the user wants to investigate, research, or explore options before planning an objective. Triggers on: "research objective", "investigate before planning", "look into how to build", "what's the…
Data-independent acquisition (DIA) proteomics analysis with DIA-NN and other tools. Covers library-free and library-based workflows for deep proteome profiling.
Routes a vague symptom or complaint to the most relevant Clairvoyance skill via a decision tree. Use when someone describes a problem but doesn't know which skill to reach for. Not for running a comprehensive review (use design-review) or scanning a checklist…
Run diagnostics for the AItrader trading system. 运行 AItrader 交易系统诊断。 Use this skill when: - No trading signals are being generated (没有交易信号) - Need to check if AI analysis is working (检查 AI 分析是否正常) - Verifying technical indicator calculations (验证技术指标计算) -…
Source text: Chinese
Use to evaluate the current state of a diamond. Checks theory gates, confidence levels, and recommends next action.
Use to evaluate the current state of a diamond. Checks theory gates, confidence levels, and recommends next action.
Use this skill for systematic change analysis with risk scoring. Use when analyzing specific changesets, assessing risk of changes, preparing release notes, categorizing changes by type and impact. Do not use when quick context catchup - use catchup instead.…
Methodology for categorizing changes, assessing risks, and creating summaries from any changeset. Triggers: diff analysis, changeset review, risk assessment, change categorization, semantic analysis, release preparation, change summary, git diff Use when:…
Deterministic git diff inspection. Converts natural language intent into an explicit, auditable diff plan and emits a bounded summary and optional patch artifacts.
Differential abundance and state analysis for cytometry data. Compare cell populations between conditions using statistical methods. Use when testing for significant changes in cell frequencies or marker expression between groups.
Perform differential expression analysis of miRNAs between conditions using DESeq2 or edgeR with small RNA-specific considerations. Use when identifying miRNAs that change between treatment groups, disease states, or developmental stages.
Refines an active research session by drilling deeper into a subtopic. Use after tome:research to narrow results to a specific channel or angle.
Summarize vault learnings and activity for today or a date range.
This skill should be used when the user asks for "email digest", "daily digest", "email summary", "morning briefing", or wants a summary of recent emails. Generates a markdown digest grouped by priority.
Run diligence as a fast risk burn-down: build a ranked risk register (max 4), execute the fastest tests, and produce decision-changing evidence. Use when a deal advances past first meeting.
A time-boxed diligence sprint (3-7 days) with daily deliverables and decision gates. Burns down top 4 risks and produces IC-ready evidence. Use when a deal is live and you need speed without losing rigor.
Scans HN, Lobsters, Reddit, and tech blogs for community experience reports. Use when gathering practitioner opinions on a technology or approach.
Use when the user asks for a deep codebase analysis to identify and rank improvements, optimizations, architectural enhancements, or potential bugs aligned to developer, end-user, and agent jobs-to-be-done.
Read product and technical docs, then summarize requirements and gaps.
Search archived tickets by keywords to find related historical context.
Use when research phase is complete and you need to explore implementation
Analyze a user canvas and distill structured fears, steering targets, and synthesis features into a cognition sidecar file.
Dives deep into project questions using layered investigation (docs → code → analysis) to provide evidence-based answers with file:line citations. Use when asking "how does X work", "what is Y", "where is Z", or investigating features, APIs, configuration,…
Alpha and beta diversity analysis for microbiome data. Calculate within-sample richness, evenness, and between-sample dissimilarity with phyloseq and vegan. Use when comparing community composition across samples or testing for group differences in microbiome…
Run comprehensive agent-native architecture review with scored principles. Audits a codebase against 8 agent-native architecture principles (Action Parity, Tools as Primitives, Context Injection, Shared Workspace, CRUD Completeness, UI Integration, Capability…
Traces a workflow end-to-end through the harness-kit monorepo and creates a breadcrumb analysis doc in docs/breadcrumb_analysis/. Use this skill whenever the user wants to document a flow, trace a workflow, understand how a feature works across layers…
Audit whether an AI agent can autonomously close the loop on problems in a given area — from discovering a symptom to verifying a fix — without human intervention. Evaluates documentation, diagnostic tools, commands, logs, and flows for completeness and…
Analyzes code changes and identifies documentation gaps. Scans git history, catalogs existing docs, and generates comprehensive analysis reports.
PROACTIVELY search auto-generated documentation when receiving ANY user instruction. Search for function signatures, API documentation, class definitions, and code comments BEFORE implementing anything. Your codebase documentation is valuable - use it first.
Search technical documentation using executable scripts to detect query type, fetch from llms.txt sources (context7.com), and analyze results. Use when user needs: (1) Topic-specific documentation (features/components/concepts), (2) Library/framework…
Search internet for technical documentation using llms.txt standard (context7.com) and parallel exploration. ALWAYS use when user asks "how to use X library", "documentation for Y", "docs for Z", needs latest docs for any library/framework, or mentions…
[Documentation] Search technical documentation using executable scripts to detect query type, fetch from llms.txt sources (context7.com), and analyze results. Use when user needs topic-specific documentation, library/framework documentation, GitHub repository…
(ePost) Use when you need API docs, library references, or framework documentation for an unfamiliar package
Automatically classify and extract information from construction documents using NLP. Categorize RFIs, submittals, change orders, specifications, and contracts.
Deep research aggregator that searches Brave (Web), Perplexity (AI), GitHub (Code/Issues), ArXiv (Papers), YouTube (Videos), and Wayback Machine simultaneously. Provides a consolidated Markdown report with an ambiguity check and Agentic Handoff.
Five-phase reasoning protocol based on Musashi's Book of Five Rings. Ground (morphemic extraction), Water (pattern matching), Fire (unified derivation), Wind (predictions), Void (meta-closure). Use for cross-disciplinary insight discovery.
ユーザーの業務領域や目的を分析し、必要な機能を抽出する。プラグイン企画時、業務分析時、機能要件定義時、またはユーザーが業務領域分析、ドメイン分析、機能抽出、プラグイン設計に言及した際に使用する。
Source text: Japanese
Assess delivery health metrics. For software: DORA + APEX. For content/AI/service products: product-type-appropriate metrics.