2,667 件 ・ 関連度順
概要と使いどころ
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
日本語の概要は準備中です。原文の説明を表示しています。
Use after completing any non-trivial task. The agent self-rates its output on 5 axes — accuracy, completeness, clarity, actionability, conciseness — with concrete evidence per criterion. Produces a structured 1-5 scorecard with specific improvement suggestions.
日本語の概要は準備中です。原文の説明を表示しています。
Route agent work through AccInt's MCP memory loop: retrieve prior outcomes, resolve frames, and close commitments with evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Responds to security incidents in cloud environments (AWS, Azure, GCP) by performing identity-based containment, cloud-native log analysis, resource isolation, and forensic evidence acquisition adapted for ephemeral cloud infrastructure. Activates for requests involving cloud incident response, AWS security incident, Azure compromise, GCP breach, cloud forensics, or cloud identity compromise.
日本語の概要は準備中です。原文の説明を表示しています。
Parse Windows Prefetch files to determine program execution history including run counts, timestamps, and referenced files for forensic investigation.
日本語の概要は準備中です。原文の説明を表示しています。
Parse Windows LNK shortcut files to extract target paths, timestamps, volume information, and machine identifiers for forensic timeline reconstruction.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze Microsoft Outlook PST and OST files for email forensic evidence including message content, headers, attachments, deleted items, and metadata using libpff, pst-utils, and forensic email analysis tools for legal investigations and incident response.
日本語の概要は準備中です。原文の説明を表示しています。
Standard Operating Procedures for web research, documentation lookup, evidence synthesis with citations.
日本語の概要は準備中です。原文の説明を表示しています。
Examine Linux system artifacts including auth logs, cron jobs, shell history, and system configuration to uncover evidence of compromise or unauthorized activity.
日本語の概要は準備中です。原文の説明を表示しています。
Standard Operating Procedures for read-only codebase exploration, symbol search, dependency mapping, code tracing, code review, architecture analysis, technical research, source evaluation, and evidence-based reporting.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate compromised Docker containers by analyzing images, layers, volumes, logs, and runtime artifacts to identify malicious activity and evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze Windows LNK shortcut files and Jump List artifacts to establish evidence of file access, program execution, and user activity using LECmd, JLECmd, and manual binary parsing of the Shell Link Binary format.
日本語の概要は準備中です。原文の説明を表示しています。
Audit a codebase as a read-only senior advisor, prioritize evidence-backed improvements, and write self-contained implementation plans. Use for codebase audits, improvement roadmaps, focused planning, plan review, plan reconciliation, or executing an existing improve plan through an isolated Codex worktree. The advisor never edits source code; execution uses codex-improve and returns to the main agent for review.
日本語の概要は準備中です。原文の説明を表示しています。
Read public X/Twitter post URLs as structured evidence through the ADHX API. Use for relevant user-provided or research-discovered x.com, twitter.com, or adhx.com links. ADHX does not search X, and long-form Article content may be incomplete.
日本語の概要は準備中です。原文の説明を表示しています。
Synthesize user interviews, observations, surveys, support tickets, reviews, or feedback into traceable themes, insights, tensions, opportunities, and research gaps; use when evidence must inform product or design decisions.
日本語の概要は準備中です。原文の説明を表示しています。
使用有界本地报告诊断 Codex Flight Control 的安装、runtime、文档、持久状态、Wave、Guidance、Private Skill、角色策略、托管工作区、Evidence、Completion Gate 和恢复状态。用户询问飞控状态、健康、支持信息、恢复分析或阻断原因时使用；禁止上传数据或执行破坏性修复。
日本語の概要は準備中です。原文の説明を表示しています。
使用状态绑定的最小 Tool Surface、exact Action Gateway、来源可追踪的 MissionSpec 与 Verification Manifest、宿主无关 Flight Progression Engine、可选且无权威的 App Server continuation、顺序持久 Wave、一层原生 Agent、困难后强制战术指导、证据型 Capability Profile、显式 Manual Verification、不可变宿主 Evidence、恢复检查点和仅本地 Git，治理复杂 Codex 开发。用户要求飞控接管、继续、自主开发、修复或完成多步骤软件项目，需要有界并行子代理，或实现前必须建立文档工程时使用。
日本語の概要は準備中です。原文の説明を表示しています。
Create, verify, transfer, and resume compact project handoff packets for long-running Codex work. Use after a second observed automatic context compaction, immediately after a third compaction, when attention or constraints degrade, a major phase ends, the user asks to move work into a fresh task, work must pause, or an existing handoff needs to be imported. Do not interrupt after the first normal compaction. Always ask before creating a new task, transfer the global roadmap only after explicit consent, preserve the old task title when available, then require the fresh task to ask what work matters most. Preserve objectives, constraints, decisions, evidence, approval boundaries, workspace state, validation, and risks without treating an old summary as current truth.
日本語の概要は準備中です。原文の説明を表示しています。
Work the review of a research run with rs_review — read the manuscript and record the panel's concerns with the evidence that grounds each one, keep the author's reply and the re-review's finding in their separate columns, run the devil's advocate with the concession threshold the tool enforces, and write the panel report and traceability matrix a response-to-reviewers letter is built from. Use when a document is ready for review, when a concern has to be answered or re-reviewed, or when an attack or a concession is being recorded.
日本語の概要は準備中です。原文の説明を表示しています。
Write the document of a research run — plan the question and the outline with rs_plan, write prose and declare its claims together with rs_write, choose the claim strength the evidence actually holds, follow the section structure the run's kind maps to, read the draft back, and build a watermarked draft before the gated clean build. Use when a run's document has to be written, a section drafted, a claim bound to a source, or a build attempted.
日本語の概要は準備中です。原文の説明を表示しています。
Re-verify active offers vs official sources, fix drifted terms, refresh evidence, then issue, PR, review, merge unattended; report-only/no-merge modes. Use for daily checks or stale-content issues. Don't use for adding or editing one offer, or CI.
日本語の概要は準備中です。原文の説明を表示しています。
Refine an existing skill in place with minimal diffs. Trigger when asked to improve a skill's trigger description/frontmatter, workflow text, metadata, scripts/references/assets; also for requests to iterate, refactor, rename, or fix a skill using usage/session-mining evidence (for example from /tw-seq).
日本語の概要は準備中です。原文の説明を表示しています。
Analyze a local codebase and infer the architecture it is actually using, including repo kind, best-fit dominant architecture, directly evidenced coexisting patterns, major subsystem exceptions, confidence, docs-vs-code drift, and repo-fit hints for downstream agents. Use when prompts ask what architecture a repo uses, whether it is really hexagonal or just layered, what subtle patterns shape a repo or slice, how a target slice fits a hybrid monorepo, whether documented architecture matches implementation, or when `/tw-tk` needs a repo-dialect preflight before making a minimal change.
日本語の概要は準備中です。原文の説明を表示しています。
Audit over-engineered codebases by factoring layers into live obligations, quotienting redundant distinctions, ablating unearned surface, and normalizing survivors while preserving required behavior. Use when change latency or agent difficulty comes from frameworks, plugins, DI, codegen, task runners, config indirection, ORMs, GraphQL, monorepo/infra tooling, or web stacks, or when asked to remove layers. Produces an evidence-backed Reduction Certificate, cuts, migration phases, proof signals, and rollback. Not for one local readability cleanup (use tw-complexity-mitigator).
日本語の概要は準備中です。原文の説明を表示しています。