2,807 件 ・ 関連度順
概要と使いどころ
Use when starting work in a repository under repositories/ that may lack CI configuration. Detects missing CI workflows (GitHub Actions, GitLab CI, CircleCI) and alerts the user to add one. Skips repos marked as research-only.
日本語の概要は準備中です。原文の説明を表示しています。
Scan projects for credential leaks, secrets in code, insecure patterns, LLM API key exposure, PII leakage to external AI services, and .env/.gitignore misconfigurations. Especially useful for data and API integrations, regardless of implementation language.
日本語の概要は準備中です。原文の説明を表示しています。
Team conventions for Python development — credentials, API clients, LLM response parsing, testing patterns, and data pipeline structure. Covers dotenv loading, retry logic, secret validation, and pipeline anti-patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to measure command execution time or optimize a feedback loop. Records explicit measurements and recommends faster alternatives such as unit tests versus integration tests. It is opt-in; it does not run on every command.
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementing features, fixing bugs, or refactoring code that may invalidate existing docs. Detects stale documentation by matching the code diff against in-repo doc files and applies targeted updates. Relevant when code changes rename, remove, or add APIs, fields, config keys, or CLI flags. Also applies when the user says "update docs", "check docs", or "are the docs stale", or when reviewing a branch for documentation accuracy.
日本語の概要は準備中です。原文の説明を表示しています。
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive regression model diagnostics and assumption checking. Use when validating regression models, checking assumptions (linearity, homoskedasticity, normality, independence), detecting outliers/influence, testing multicollinearity, or when user mentions residuals, heteroskedasticity, VIF, Cook's distance, or diagnostic plots.
日本語の概要は準備中です。原文の説明を表示しています。
Design randomized controlled trials for causal inference. Use when user mentions: randomized evaluation, RCT, field experiment, randomized experiment, treatment assignment, causal impact, experimental design, control group, intervention evaluation.
日本語の概要は準備中です。原文の説明を表示しています。
Handle ethical requirements, IRB approval, trial registration, and pre-analysis plans for RCTs. Use when user mentions: research ethics, IRB, informed consent, trial registration, pre-analysis plan, PAP, data security, vulnerable populations, research transparency.
日本語の概要は準備中です。原文の説明を表示しています。
Calculate statistical power and sample sizes for RCTs. Use when user mentions: power analysis, sample size calculation, minimum detectable effect, MDE, statistical power, effect size, clustering effects, design effect, ICC, intra-cluster correlation.
日本語の概要は準備中です。原文の説明を表示しています。
Implement randomization methods for RCTs. Use when user mentions: random assignment, treatment allocation, stratification, blocking, permutation randomization, cluster randomization, randomization balance, misfit handling, re-randomization.
日本語の概要は準備中です。原文の説明を表示しています。
Summary statistics, data exploration, and descriptive analysis. Use for: summary stats, describe data, data exploration, distributions, means, medians, correlations, cross-tabs.
日本語の概要は準備中です。原文の説明を表示しています。
Causal inference with treatment/control groups over time. Use when user mentions: treatment effects, policy evaluation, pre/post comparison, parallel trends, DID, DiD, difference in differences, natural experiment, quasi-experimental.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze data from randomized controlled trials. Use when user mentions: treatment effects, ITT analysis, LATE, TOT, compliance analysis, attrition, balance checks, heterogeneous effects, RCT results, experimental analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Core statistical methodology and pedagogical approach for all Inquiro analyses. Always loaded to maintain teaching quality and reproducibility standards.
日本語の概要は準備中です。原文の説明を表示しています。
Publication-quality statistical visualization with mandatory best practices. Use when creating plots, charts, figures, or any data visualization. Enforces accessibility, uncertainty display, proper labeling, and statistical accuracy.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic literature review methodology for social science research. Use when conducting systematic reviews, research synthesis, meta-analyses, scoping reviews, or comprehensive literature searches across economics, political science, sociology, education, public health, and development. Produces structured notebook cells with search strategy, evidence table, thematic synthesis, and gap analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Autonomous goal loop — give it ONE goal plus how to verify it, the agent runs check→fix→check itself and comes back only with the finished result (code with audit, research with fact-check, content with critique, audit/backtest). Self-verification instead of constant supervision, with hard safety guards. Vary the loop with a verification rubric designed before it runs. Triggers — "work autonomously to the result", "don't come back until it's done", "run the loop yourself", "drive it to done".
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate an incoming workflow upgrade — a skill, MCP server, subagent, library, external service, prompt, or pattern — through one disciplined pipeline before adopting it. Security is a blocking gate. Records every verdict so the same thing is never evaluated twice. Use when considering a new tool from a post, repo, or recommendation. Triggers — "vet this", "should we adopt", "is this safe to install", "evaluate this skill/MCP", "what do you think of this tool".
日本語の概要は準備中です。原文の説明を表示しています。
Prove — or honestly fail to prove — a specific technical claim: "the fix works", "it's deployed", "the service is running", "the site is done", "there are no vulnerabilities". Atomizes the claim, picks the shortest decisive signal on the evidence ladder, and returns a verdict from a fixed vocabulary (pass / partial / fail / skip) with an explicit coverage boundary. NOT code review, NOT a fix, NOT orchestration — only "what is proven, and what we merely hope". Triggers — "prove it works", "is it really done?", "are you sure?", "we deployed — is it live?", "verify that", "did we actually check?".
日本語の概要は準備中です。原文の説明を表示しています。
Council — 5 independent AI perspectives + mutual critique + synthesis (adapted from karpathy/llm-council for Claude Code). For high-stakes decisions where the answer does NOT follow unambiguously from the data — go/no-go before real consequences, critiquing a methodology, choosing between competing approaches, pressure-testing a conclusion you're attached to, designing risk controls. NOT for log/data analysis (the council has no data access) and not for factual lookups. Triggers — "convene the council", "run it past the council", "go/no-go", "pressure-test this".
日本語の概要は準備中です。原文の説明を表示しています。
Deliberate system-improvement loop — audit your own Claude Code setup (rules / memory / skills / MCP / agents / registry), evaluate incoming tools via /vet, adopt the worthwhile ones with discipline (backup → verify), and record every decision. Use when bringing in a tool/idea/collection to improve the setup, or when doing a tooling-improvement pass. Triggers — "upgrade the workflow", "audit our setup", "let's improve the tooling", "evaluate this for us", when handed a post/repo/reel with a tool.
日本語の概要は準備中です。原文の説明を表示しています。
Write an analytical longform piece — a 4-phase pipeline from raw idea to finished text, with research-backed facts and a devil's-advocate pass before publishing. Invoke /longread <topic>. Triggers — "write a longread about X", "write an analytical breakdown of Y", "write an expert post", "turn this into an article".
日本語の概要は準備中です。原文の説明を表示しています。
Preventive hygiene audit of your own Claude Code configuration — memory files, project context (CLAUDE.md), rules, permissions, skills — a deterministic scan of sizes / broken links / stale entries / excessive permissions / junk + interpretation + targeted fixes by agreement. Keeps the setup from rotting before it breaks. Triggers — "check the system", "system health", "workflow hygiene", "what to clean up", "audit memory", "optimize the system".
日本語の概要は準備中です。原文の説明を表示しています。