菜单
Use when the user explicitly invokes imsight-project-automation or requests one of its maintained project routines, including an OpenSpec lifecycle in one pass or user-directed testing followed by minimal bug fixes through OpenSpec.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user wants to search, fetch, or bulk-collect academic papers, authors, citations, references, recommendations, or Semantic Scholar datasets through direct curl calls to the Semantic Scholar APIs.
Manual invocation only; Imsight-authored command skill for analyzing, deep-inspecting, designing, creating, refactor-migrating, testing, hardening, or formatting agent skills. Use only when the user explicitly invokes imsight-agent-skill-handling or asks to use this exact skill. Its subcommands are help, analyze, deep-inspect, design, create, refactor-migrate, test, harden, and format. Do not invoke implicitly for generic skill creation, skill audits, skill updates, skill-format work, routing from another skill, generic coding tasks, or ordinary use of a domain skill.
Use when building or maintaining a Karpathy-style LLM knowledge base inside the current project, or when deploying the bundled local web viewer for that wiki. Triggers on requests to scaffold, compile, ingest, research, collect, inventory, project, query, lint, audit, or launch an LLM Wiki.
Use when explicitly invoking imsight-reporting, routing from another Imsight skill, or using Imsight context to produce a daily work log from Git commits, staged or unstaged diffs, nested repositories, research-topic artifacts, build records, specifications, or other project evidence.
Use when explicitly invoking imsight-dev-box-network, routing from another Imsight skill, or using Imsight context to configure, audit, repair, or document dev-box networking, SSH tunnels, proxy access, relay access, exposed ports, remote Playwright browser control, systemd user tunnel services, or host-to-host access. Do not use for generic networking tasks without Imsight context.
Use when explicitly asked to use Imsight project design, Imsight SOP, this exact skill, or an Imsight-authored process to scaffold or revise feature planning, define a feature, design use cases, design interfaces or agent skills, manually refine recorded design decisions, or write an implementation handoff.
| name | imsight-project-automation |
| description | Use when the user explicitly invokes imsight-project-automation or requests one of its maintained project routines, including an OpenSpec lifecycle in one pass or user-directed testing followed by minimal bug fixes through OpenSpec. |
This skill is an entrypoint for focused project-automation routines. Keep SKILL.md small; reusable behavior belongs in subcommand pages.
Use this skill only when explicitly invoked by name or when the request clearly targets a maintained automation routine, such as:
imsight-project-automation or one of its subcommands,Do not activate it implicitly for ordinary development tasks that do not name imsight-project-automation or one of its maintained operations.
help.openspec-one-pass, load commands/openspec-one-pass.md.openspec-test-and-fix, load commands/openspec-test-and-fix.md.If the task does not map cleanly to these steps, use your native planning tool only with the existing subcommands and constraints; report when no maintained routine matches.
$imsight-project-automation use <subcommand> to do <task>.$imsight-project-automation <task prompt> means choose the applicable subcommand from the task.help.help summarizes this skill and lists the subcommands below.When this skill writes skill-owned auxiliary artifacts, choose the output directory in this order:
IMSIGHT_PROJECT_AUTOMATION_OUTPUT_DIR when set; relative values are resolved from the current project directory and absolute values are used as-is.<project-dir>/.imsight-arts/project-automation/.This contract does not relocate OpenSpec changes, implementation edits, or initialized openspec/ trees; those stay in the target workdir required by the selected OpenSpec workflow.
| Subcommand | Use For | Detail |
|---|---|---|
help | Explain this skill and list public subcommands | This entrypoint |
openspec-one-pass | Given one development request, run an OpenSpec lifecycle in one pass: explore, propose, apply, sync, and archive. | commands/openspec-one-pass.md |
openspec-test-and-fix | Run user-provided tests, document unexpected outcomes, make minimal continuation patches, then propose and apply confirmed bug fixes through OpenSpec. | commands/openspec-test-and-fix.md |
SKILL.md.