skills/codex/SKILL.md
# Codex Skill for insight-agent ## 目的 この repo で Codex が迷わず作業開始できるようにするための最小ガイドです。 ## 最初に見る場所 1. `README.md` 2. `docs/src/output_schema_v2.json` 3. `insight_core/runner.py` 4. `insight_core/runtime_config.py` 5. `insight_core/request_loader.py` ## 正規入口 - API の本命は `run()` - CLI の本命は `python -m insight_core.cli run ...` - `run_pipeline_result()` / `run_insight_result()` は互換 wrapper ## 変更方針 - 入口を増やすより `run()` に寄せる - 挙動差分は config で吸収する - 入力形式差分は loader 層で吸収する - 出力形式差分は formatter 層で吸収する - 既定の外
npx skillsauth add rna4219/insight-agent skills/codexInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
この repo で Codex が迷わず作業開始できるようにするための最小ガイドです。
README.mddocs/src/output_schema_v2.jsoninsight_core/runner.pyinsight_core/runtime_config.pyinsight_core/request_loader.pyrun()python -m insight_core.cli run ...run_pipeline_result() / run_insight_result() は互換 wrapperrun() に寄せるoutput_schema_v2insight_core/pipeline.py は中核なので、責務追加は慎重に行うinsight_core/cli.py は薄い adapter に保つinsight_core/runtime_config.py の優先順位は default -> file -> env -> override -> request localraw は debug 用なので外部契約の中心にしないpython -m pytest -q
python -m insight_core.cli run --help
python -m insight_core.cli run -i examples/sample_request.json
output_schema_v2 で一致しているかInsightRequest に正規化されるかtools
# Claude Skill for insight-agent ## 目的 Claude がこの repo を読むときに、設計の芯と変更境界を短時間でつかめるようにするためのガイドです。 ## まず理解すること - この repo は課題発見エンジン - 入力の正規化先は `InsightRequest` - 実行の正規入口は `run()` - 既定出力は `output_schema_v2` - CLI と API は同じ canonical runner を通る ## 推奨読順 1. `README.md` 2. `docs/src/output_schema_v2.json` 3. `insight_core/schemas.py` 4. `insight_core/runner.py` 5. `insight_core/result_formatter.py` 6. `insight_core/pipeline.py` ## どこを直すべきか - 入力の扱い: `insight_core/request_loader.py` - 設定の優先順位: `insi
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------