1.1万 件 ・ 関連度順
概要と使いどころ
Review a mathematical-modeling paper's model-assumption section against the complete problem statement. Diagnose whether each assumption is necessary, evidence-based, compatible with the task, appropriately simplified, and usable by the later model. Use for assumption review, not automatic full-paper review or unsupported assumption generation.
日本語の概要は準備中です。原文の説明を表示しています。
Review mathematical modeling competition papers from a complete problem and paper, with an optional strict bzd-paper-format-checker audit, itemized problem-specific scoring, a bottom-up low-score safeguard, and CUMCM award calibration by problem type, division, region, school and advisor. Generate a Chinese HTML judge report.
日本語の概要は準備中です。原文の説明を表示しています。
Review the model establishment, numerical solution, result analysis, model validation, and sensitivity or robustness sections of a mathematical-modeling paper against the complete problem. Use for core-model-section diagnosis, not automatic full-paper scoring or unsupported recomputation.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate the BZD mathematical-modeling Skills across problem reading, idea generation, model selection, paper drafting, section checks, final format/AIGC audits and judge-style scoring. Use when a user wants one entry point, an end-to-end competition workflow, the next appropriate Skill, or coordinated processing of a problem and paper.
日本語の概要は準備中です。原文の説明を表示しています。
Generate or review mathematical-modeling competition AI tool usage statements and the anonymous AI工具使用详情.pdf. Use when users provide real AI usage records, or when checking a paper, statement, details PDF, code, and AI records for completeness, anonymity, and consistency.
日本語の概要は準備中です。原文の説明を表示しています。
Run health checks on Claude Code configuration and sessions. Use when troubleshooting Claude Code issues. (cozempic — does not shadow Claude Code's built-in /doctor)
日本語の概要は準備中です。原文の説明を表示しています。
Audit project dependencies, frameworks, languages, and dev tools for known vulnerabilities, CVEs, and security anti-patterns. Use when the user mentions 'dependency audit,' 'npm audit,' 'CVE,' 'vulnerable packages,' 'supply chain security,' 'outdated dependencies,' 'known vulnerabilities,' 'security advisory,' 'package security,' 'framework vulnerability,' 'is this package safe,' or needs to check whether their stack has known security issues.
日本語の概要は準備中です。原文の説明を表示しています。
Same-epoch comparison of training runs across wandb, neptune, tensorboard, or mlflow. Aligns runs at the student's current step (never current-vs-final-of-baseline) and separates proxy metrics from downstream targets. Use when the user asks to compare runs, check if a run is improving, track lag against a baseline, rank experiments, or evaluate run-vs-run performance.
日本語の概要は準備中です。原文の説明を表示しています。
Evidence-before-action diagnosis of failing ML experiments. Probes the system before guessing causes, process list, dmesg, GPU stats, log scrollback, checkpoint state, then states a hypothesis as a hypothesis and runs a smoke before claiming a root cause. Use when the user asks why a run is failing, diverging, OOMing, hanging, slow, producing weird metrics, has crashed, or asks to debug, diagnose, troubleshoot, or investigate a training issue.
日本語の概要は準備中です。原文の説明を表示しています。
Pre-flight checklist for long-running ML training jobs covering config diff, run naming, path verification, monitoring setup, and restart-cleanup. Use when the user asks to launch, kick off, start, restart, or kill a training run, or mentions launching a multi-hour or multi-day GPU job (python train, accelerate launch, torchrun, deepspeed, sbatch, tmux training).
日本語の概要は準備中です。原文の説明を表示しています。
Creates isolated git worktrees with smart directory selection and safety checks. Use when starting isolated feature work.
日本語の概要は準備中です。原文の説明を表示しています。
Pre-deployment security audit organized by OWASP Top 10. Use when reviewing code before shipping or going to production.
日本語の概要は準備中です。原文の説明を表示しています。
Crisis communication and rapid-response workflows. Use when covering breaking news or coordinating fast fact-checking on deadline.
日本語の概要は準備中です。原文の説明を表示しています。
FOIA and public records workflows. Use when drafting requests, tracking submissions, checking exemptions, or appealing denials.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you have a written implementation plan to execute in a separate session with review checkpoints
日本語の概要は準備中です。原文の説明を表示しています。
Solana token market data via Birdeye — prices, OHLCV, trades, token metadata, security checks, and trader activity
日本語の概要は準備中です。原文の説明を表示しています。
Migrate from npm-installed metaswarm to the marketplace plugin — removes redundant files with safety checks
日本語の概要は準備中です。原文の説明を表示しています。
Monitor a PR through to merge — handle CI failures, review comments, and thread resolution automatically until all checks pass
日本語の概要は準備中です。原文の説明を表示しています。
Carry out the intent approved in `ready`, as meant, and prove it with checks that actually ran. Comes back to you if the work would change what you approved, keeps the project docs in step, and never merges on its own. Use when the user invokes the `go` skill after `ready`. Requires git.
日本語の概要は準備中です。原文の説明を表示しています。
Launch the app and hands-on verify that it works by interacting with it. Falls back to an existing integration test suite when there is no interactive surface in scope. Use when the user asks to "smoke test", "test it manually", "verify it works", "try it out", "run a smoke test", "check it in the browser", or "does it actually work". Not a unit test runner.
日本語の概要は準備中です。原文の説明を表示しています。
Execute multi-level exploratory testing of the app covering basic functionality, complex operations, adversarial testing, and cross-cutting scenarios, plus usability observations through a UX lens reported separately from defects. Deeper than $smoke-test. Use when the user asks to "exploratory test", "test thoroughly", "test all scenarios", "deep test", "test edge cases", "test everything", "break it", "find bugs by testing", "test usability", or "check the UX while testing".
日本語の概要は準備中です。原文の説明を表示しています。
Review a plan by running internal reviews and a peer review in parallel and returning combined findings. Use when the user asks to "review my plan", "check my plan", "critique my plan", or wants feedback on a plan.
日本語の概要は準備中です。原文の説明を表示しています。
Survey the codebase for analogous features, reusable utilities, and existing patterns relevant to a proposed change, reading any source the task names outside this repo. Returns structured findings without writing code. Use when the user asks to "survey patterns", "find existing patterns", "look for analogous features", "check how similar things are done", "find prior art for this change", or needs pattern context before planning a change.
日本語の概要は準備中です。原文の説明を表示しています。
Review a pull request by fetching PR comments, running a comprehensive code review, evaluating findings, and dispatching to implementation. Use when the user asks to "review PR", "review pull request", "review this PR", "check PR before merging", or "full PR review".
日本語の概要は準備中です。原文の説明を表示しています。