2,771 件 ・ 関連度順
概要と使いどころ
Validates defensive controls with paired authorized action and observation evidence, distinguishing blocked, prevented, detected, responded, and telemetry-gap outcomes. Use for purple-team validation design or offline fixture review; not unsanctioned testing or production efficacy claims.
日本語の概要は準備中です。原文の説明を表示しています。
Conducts hypothesis-driven, evidence-preserving threat hunts with bounded negative conclusions and telemetry-gap handling. Use for hunt hypotheses, scoped offline analysis, or analytic follow-up; not unscoped scanning, malware execution, or generic intelligence summaries.
日本語の概要は準備中です。原文の説明を表示しています。
Draws architecture diagrams as editable draw.io files with a fixed house style, C4 levels, evidence-tagged shapes, and optional multi-view identity checks. Use when producing a system context, container, component, deployment, data flow, sequence, state, or ERD, or redrawing an ASCII or Mermaid one.
日本語の概要は準備中です。原文の説明を表示しています。
Plans risk-based test portfolios and acceptance evidence; does not write or execute tests.
日本語の概要は準備中です。原文の説明を表示しています。
Creates evidence-backed current or target architecture diagrams; not UI design.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnoses incidents from operational evidence and proposes recovery; does not change live systems.
日本語の概要は準備中です。原文の説明を表示しています。
Builds dependency-ordered delivery plans from requirements and repository evidence; read-only.
日本語の概要は準備中です。原文の説明を表示しています。
Documents current architecture from implementation evidence; does not propose a target or audit fitness.
日本語の概要は準備中です。原文の説明を表示しています。
Create, revise, and format thesis or dissertation Word documents with strict academic formatting control. Use when an AI agent needs to generate or revise thesis content, normalize Word styles, follow a school template, fix captions or page numbers or section levels, or produce evidence-based Mermaid figures and LaTeX-formatted code listings for a thesis document.
日本語の概要は準備中です。原文の説明を表示しています。
Enhanced academic paper review response workflow with Agy/CLI collaborative analysis and multi-perspective discussion. Produces structured rebuttal documents with evidence-based strategies. Triggers on "rebuttal", "respond to reviewers", "review response", "审稿回复".
日本語の概要は準備中です。原文の説明を表示しています。
Quick execution for small tasks — minimal run lifecycle (start + done) with evidence recording. Full LLM capability, scoped to mechanically clear tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate Elixir/Phoenix bugs root-cause first. Reproduce failures, cite evidence, and use optional native DeepSeek Harness subagents only when useful.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate Elixir/Phoenix bugs root-cause first. Reproduce failures, cite evidence, and use optional native OpenCode subagents only when useful.
日本語の概要は準備中です。原文の説明を表示しています。
Review changed Elixir/Phoenix code read-only. Check requirements, cite evidence, deduplicate, and return a verdict.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate Elixir/Phoenix bugs root-cause first. Reproduce failures, cite evidence; Codex subagents are optional.
日本語の概要は準備中です。原文の説明を表示しています。
Review changed Elixir/Phoenix code read-only. Check requirements, cite evidence, deduplicate findings, and return a severity-based verdict.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate Elixir/Phoenix bugs root-cause first. Reproduce failures, cite evidence, and use optional Amp subagents only when useful.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user needs to turn a real software engineering / computer science project and an existing thesis draft into a submission-ready undergraduate thesis manuscript. Trigger for requests such as "根据项目把论文改成定稿", "按学校模板排版成最终版", "复制初稿后生成定稿 Word", "为定稿降查重", "根据PaperPass报告降AIGC", "继续在手改初稿上改", "恢复原来的图表和数据库说明", or when academic-paper-strategist has already produced an evidence-backed rewrite plan. Outputs a cleaned manuscript, final DOCX workflow, and a separate rework report.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user needs to plan, de-risk, or ground a software engineering / computer science undergraduate thesis from a real codebase before final writing. Trigger for requests such as "根据项目写毕业论文", "先做论文大纲", "用真实项目材料规划论文", "检查论文是否脱离代码", "根据检测报告降查重", "根据AIGC报告改写定稿", "继续在手改初稿上改", or when an existing draft thesis must be reworked against a school format sample. Produces an evidence-backed outline, chapter rewrite plan, figure plan, and handoff package for academic-paper-composer.
日本語の概要は準備中です。原文の説明を表示しています。
Turn one confirmed security finding into a disclosure-ready GitHub advisory with root cause, proof of concept, impact, and source evidence. Use for reporting an established vulnerability, not discovering or validating one.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically verifies suspected security bugs to eliminate false positives. Produces TRUE POSITIVE or FALSE POSITIVE verdicts with documented evidence for each bug.
日本語の概要は準備中です。原文の説明を表示しています。
Operational rubric that turns "don't make AI slop" into observable properties, severity levels, evidence requirements, and repair actions for interface design. Use as the reference rubric when building or reviewing marketing sites, product interfaces, dashboards, portfolios, or e-commerce pages, especially alongside frontend-design.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes recent CI failures on pull requests to identify flaky tests, using retry outcomes (failed attempt → green re-run) and cross-PR recurrence as evidence, and maintains a local longitudinal ledger so flakiness can be tracked over time. TRIGGER when: the user wants to find flaky tests, correlate recent CI failures, check which tests fail across PRs or recover on retry, or refresh the flakiness trend report. DO NOT TRIGGER when: babysitting a single PR's CI until green → monitoring-pull-requests; diagnosing or fixing one specific failing test → the bug-analysis skills.
日本語の概要は準備中です。原文の説明を表示しています。
Verify Open Claude Code package integrity, release tests, and automation evidence. Use when asked whether an OCC release is published, tested, or fully automated.
日本語の概要は準備中です。原文の説明を表示しています。