DeL-TaiseiOzaki

Diagnose enabled external connections with read-only checks and report status plus next actions. Use for 「接続チェックして」 or connection failures.

Select and configure only the external services the user needs, one verified connection at a time. Use for 「接続セットアップして」 or initial connection setup.

Always load the root contract, shared vault rules, and relevant prior findings at the start of every task.

Create or refresh today's morning Daily briefing from Hermes-staged calendar and task data. Use for 「今日の Daily」 or morning briefing requests.

Extract clean Markdown from a supplied web-page URL with Defuddle CLI. Do not use for URLs that already end in .md.

Distill durable Daily and Inbox content into Wiki or agent knowledge with user approval and Daily backlinks. Use for EOD distill or 「今日の振り返り」.

Query live Hermes-owned external services through `hermes chat -q`. Use when required data has not already been captured in Inbox.

Aggregate one or more Inbox sources into today's Daily note with append-only summaries and source wikilinks. Use for Slack, meetings, code, clippings, or chat-log aggregation.

Codex CLI handles planning, design, and complex code implementation. Use for: architecture design, implementation planning, complex algorithms, debugging (root cause analysis), trade-off evaluation, code review. External research is NOT Codex's job — use…

ALWAYS activate this skill at the start of every task. Load shared rules from .agents/ and project design context before executing any task.

Simplify and refactor code while preserving functionality and library constraints.

Implement features using Test-Driven Development (TDD) with Red-Green-Refactor cycle.

Unified feature planning & implementation skill — replaces the old /add-feature and /start-feature skills (both trigger phrases still apply here). MODE=existing (formerly /add-feature): add a feature to an established codebase with Codex-first collaboration —…

Analyze project structure, populate .agents/docs/DESIGN.md, and write the thin Repository Identity section in .agents/STATE.md.

Two-phase Agent Teams execution — replaces the old /team-implement and /team-review skills. Phase 1 IMPLEMENT (formerly /team-implement): parallel implementation with teammates per module/layer, file-ownership separation, and a shared task list with…

Record a project design decision into .agents/docs/DESIGN.md through the shared typed writer. Use when the user says "record this", "add to design", "document this", "記録して", or asks what has been decided so far — and when a design decision has just been made…

Use to decide when to invoke the Claude Code CLI and how. Claude specializes in deep reasoning — plans, hypercritical reviews, multi-file impact analysis, and pipe-fed log analysis. Includes invocation patterns and cross-check usage with Codex.

Use when an architectural decision has been made or is about to be made. Decides whether the decision belongs in docs/DESIGN.md, what level of detail to record, and what NOT to record. Operates as a judgment skill, not a fixed procedure — for the procedure…

Use when evaluating a library, framework, or external service for adoption. Walks evaluation axes (fit, maintenance, license, footprint, integration cost) and produces a recommendation with explicit trade-offs. Output goes under docs/research/.

Use when reviewing a diff, a PR, or a series of recent commits. Produces a severity-graded report covering correctness, security, performance, concurrency, maintainability, and Definition of Done compliance. Pairs well with pipe input and with Codex…

Use when a bug is reported, a test is failing, or production is misbehaving. Provides observation patterns and diagnostic moves rather than a fixed sequence — every bug has its own shape. Pairs naturally with pipe-fed log analysis.

Use to decide when to invoke the Codex CLI and how. Codex specializes in tight iterate-loops, small refactors, lint cycles, and test additions. Includes invocation patterns and anti-patterns.

Use before writing any non-trivial code. Produces a written plan that names every file to touch, the order of work, the test strategy, the rollback path, and the open questions. Code is not written during this skill.

Use when assessing a feature, service, or full repo for security risk. Maps the threat surface, walks the OWASP Top 10, and emits a finding report with severity counts. Suitable as a release-gate skill.