1,232 件 ・ 関連度順
概要と使いどころ
Use when EZ_math_model model selection is unclear after the modeling decision tree, the problem spans multiple domains, or modeler needs several candidate approaches before writing modeling_plan.md.
日本語の概要は準備中です。原文の説明を表示しています。
Step 3 of the PaperOrchestra pipeline (arXiv:2604.05018). Execute the literature search strategy from outline.json — discover candidate papers via web search, verify them through Semantic Scholar (Levenshtein > 70 fuzzy title match, temporal cutoff, dedup by paperId), build a BibTeX file, and draft Introduction + Related Work using ≥90% of the verified pool. Runs in parallel with the plotting-agent. TRIGGER when the orchestrator delegates Step 3 or when the user asks to "find citations for my paper", "draft the related work", or "build the bibliography".
日本語の概要は準備中です。原文の説明を表示しています。
Decide what a papercut reel should be. Picks the topic, one familiar format, the audience level, the comment-keyword funnel and caption, studies competitor reels, and runs the post-publish autopsy. Use before any hook or script, or when reviewing how a posted reel did.
日本語の概要は準備中です。原文の説明を表示しています。
Search, post, monitor, and archive on Twitter/X via five tools: the official hosted X MCP server (full-archive search, trends, bookmarks, Articles via xurl bridge), x-search CLI (cost-tracked API v2 research with calendar-day windows, volume counts, multi-query fan-out, feeds, watchlists, posting), xurl (official CLI for any endpoint incl. media/DMs), bird CLI (free session-based reads/writes, frozen at 0.8.0), and Smaug bookmark archival. Triggers on: search tweets, tweets from today, what did X tweet, latest tweets from, tweet volume, expand a Twitter query, check Twitter for, post a tweet, tweet this, post to X, reply on Twitter, full-archive search, what's trending, check mentions, my mentions, timeline, DMs, monitor account, research topic on Twitter, my bookmarks, archive bookmarks.
日本語の概要は準備中です。原文の説明を表示しています。
Audits Claude Code repositories. Two-phase workflow — Phase 1 sweeps 14 hygiene categories (permissions, hooks, CLAUDE.md bloat, Skills hygiene, process-abstraction, plus structural) and an optional 7-layer leak check. Phase 2 executes [APPROVED] markers from the report file. Use for repo cleanup, pre-distribution sanity, post-feature hygiene, environment audit, process-abstraction discovery. Trigger on "audit my CC repo," "sweep my repository for hygiene," "check this CC environment," "find process abstraction candidates," "review my CLAUDE.md," "clean up my .claude directory," "pre-distribution hygiene check," "find layer leaks in my CC setup." Routes structural findings to rootnode-cc-design REMEDIATE. Composes with rootnode-critic-gate. CC-only — does not scan Claude Projects. Do NOT use for building a Skill (use rootnode-skill-builder), compiling a prompt (use rootnode-prompt-compilation), scoring a single prompt (use rootnode-prompt-validation), or auditing a Project (use rootnode-project-audit).
日本語の概要は準備中です。原文の説明を表示しています。
Post-implementation self-review. Use AFTER finishing ANY code implementation or change — before declaring it done, committing, or opening a PR — to critique your own work: re-read the diff adversarially, confirm unit tests cover every branch/edge, kill duplication, follow clean-code/SOLID and the repo's own docs & invariants, decide if something should become documentation, update/prune memory, and strip outdated comments. Trigger it whenever you've just written or modified code and are about to wrap up, even if the user didn't explicitly ask for a review.
日本語の概要は準備中です。原文の説明を表示しています。
Create or improve documentation based on the current conversation. Use this when a plan has been created and changes were requested because it didn’t follow the repository’s conventions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user needs to design, run, or audit product or GTM analytics — metric hierarchies and north stars, funnels, cohort retention, churn, pipeline velocity, forecasting, lead scoring, NRR, A/B tests, or analytical SQL — or uploads a dataset to analyze. Triggers on questions like "why did activation drop", "is this metric meaningful", "review my dashboard", or "what should I measure". For writing the spec that defines a feature's success metrics, use product-spec.
日本語の概要は準備中です。原文の説明を表示しています。
Design and execute A/B tests for ML models in production using traffic splitting, statistical significance testing, and canary/shadow deployment strategies. Measure performance differences and make data-driven decisions about model rollout. Use when validating a new model version before full rollout, comparing candidate models trained with different algorithms, measuring business metric impact of model changes, or when regulatory requirements mandate gradual rollout.
日本語の概要は準備中です。原文の説明を表示しています。
Plan a software release cycle with milestones, feature freezes, release candidates, and go/no-go criteria. Covers calendar-based and feature-based release strategies. Use when starting planning for a major or minor version release, transitioning from ad-hoc to structured release cadence, coordinating a release across multiple teams or components, defining quality gates for a regulated project, or planning the first public release (v1.0.0) of a project.
日本語の概要は準備中です。原文の説明を表示しています。
Implement audit trail functionality for R projects in regulated environments. Covers logging, provenance tracking, electronic signatures, data integrity checks, and 21 CFR Part 11 compliance. Use when an R analysis requires electronic records compliance (21 CFR Part 11), when you need to track who did what and when in an analysis, when implementing data provenance tracking, or when creating tamper-evident analysis logs for regulatory submissions.
日本語の概要は準備中です。原文の説明を表示しています。
Form a coherent gestalt — the whole that is more than the sum of its parts — from the panoramic perception produced by expand-awareness. Maps tensions and resonances between domains, identifies the emergent figure from the ground of multiple perspectives, tests the candidate whole for premature closure, and articulates the insight in a single sentence no single domain could have produced. Use after expand-awareness has surfaced raw multi-domain perception and before express-insight communicates the result.
日本語の概要は準備中です。原文の説明を表示しています。
Grade a trading card using PSA, BGS, or CGC standards. Covers observation-first assessment (adapted from meditate's unbiased observation), centering measurement, surface analysis, edge and corner evaluation, and final grade assignment with confidence interval. Supports Pokemon, MTG, Flesh and Blood, and Kayou cards. Use when evaluating a card before professional grading submission, pre-screening a collection for high-grade candidates, settling condition disputes between buyers and sellers, or estimating the grade-dependent value spread for a card.
日本語の概要は準備中です。原文の説明を表示しています。
Create a Work Breakdown Structure (WBS) and WBS Dictionary from project charter deliverables. Covers hierarchical decomposition, WBS coding, effort estimation, dependency identification, and critical path candidates. Use after a project charter is approved, when planning a classic or waterfall project with defined deliverables, breaking a large initiative into manageable work packages, or establishing a basis for effort estimation and resource planning.
日本語の概要は準備中です。原文の説明を表示しています。
Select an OCR/HTR engine by benchmarking candidates on the same labelled samples — source ground truth from open datasets (e.g. Hugging Face PAGE-XML corpora) or hand-transcription, wrap every engine behind a transcribe(image_path) -> str adapter (vision-LLMs via any OpenAI-compatible endpoint, dedicated HTR REST APIs, cloud OCR), and score with zero-dependency raw CER, lenient CER, WER, and a critical name/date token diff. Use when choosing an engine for handwriting or historical-document transcription, when published accuracy claims need honest verification on your own material, or when a records workflow must surface confident-but-wrong names and dates that a low aggregate CER hides.
日本語の概要は準備中です。原文の説明を表示しています。
Estimate how likely a protein therapeutic is to provoke an anti-drug antibody response, and locate the sequence regions responsible. Use this skill to tile a sequence into peptides, predict class II MHC presentation across a population-representative allele panel, aggregate predicted binders into a per-region and whole-molecule risk score, compare a candidate against its closest human germline, and decide which liabilities are worth deimmunising. Also trigger on immunogenicity, anti-drug antibody, ADA, T-cell epitope, MHC class II, HLA-DRB1, NetMHCIIpan, NetMHCpan, deimmunisation, tregitope, or population coverage.
日本語の概要は準備中です。原文の説明を表示しています。
Plan synthetic routes and judge whether a proposed molecule can actually be made, using AiZynthFinder's Monte-Carlo tree search over template-derived reactions and a purchasable building-block stock. Use this skill to configure expansion and filter policies, choose a stock file, run route search over a candidate set, and read the returned trees — solved fraction, route depth, and which building blocks a route bottoms out in. Also trigger on AiZynthFinder, retrosynthetic tree search, synthetic accessibility, SAscore, RAscore, building-block stock, reaction template, or route scoring.
日本語の概要は準備中です。原文の説明を表示しています。
Design small interfering RNA and antisense oligonucleotide sequences against a transcript, and screen them for the failure modes specific to nucleic-acid drugs. Use this skill to tile a target transcript, apply positional and thermodynamic selection rules including duplex asymmetry and nearest-neighbour melting temperature, scan candidates for seed-region complementarity to off-target transcripts, and lay out a chemical modification pattern — gapmer architecture, 2'-O-methyl and 2'-MOE wings, locked nucleic acid, and phosphorothioate placement. Also trigger on siRNA, antisense oligonucleotide, ASO, gapmer, RNase H, seed region, duplex asymmetry, 2'-MOE, locked nucleic acid, phosphorothioate, or GalNAc conjugate.
日本語の概要は準備中です。原文の説明を表示しています。
Use when work needs an isolated git worktree: new work, an existing ref, a gated feature workspace, a manifest-tracked loop run, or a candidate patch captured without touching the current checkout (`capture-isolated-patch`). Not for plain branches: use create-branch. Not for remote, credential, publish, deploy, or irreversible changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to audit comments in code files and propose structural replacements or deletions with per-candidate approval. Not for deterministic commented-out-code removal: use deslop.
日本語の概要は準備中です。原文の説明を表示しています。
Freeze one eligible Proto UI autonomous-maintenance candidate into a bounded mission packet and lease. Use before observation when a current request or governed queue supplies scope, oracle, baseline, capability, risk, budget, completion, and stop conditions. Do not observe, verify, repair, or invent a mission.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect one bounded Proto UI Issue queue slice and route ready governed work toward claim and implementation. Use for intake health, readiness, ownership, claim conflicts, stale state, or a candidate task search. This evidence leaf is read-only; authorized claim and implementation continue in their registered leaves.
日本語の概要は準備中です。原文の説明を表示しています。
Independently attempt to falsify one Proto UI autonomous-maintenance finding in a fresh non-mutating context. Use after pui-observe produced a candidate finding and route the result directly to remediation or closure when authority is clear.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare a reviewed Proto UI global release candidate as repository state after current project authority has chosen the exact version and stage. Use for draft Version identity, exact package metadata, notes, bill of materials, rehearsal, and publish dry-run. Publication remains a distinct privileged operation.
日本語の概要は準備中です。原文の説明を表示しています。