[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75Y60FSF8R2J3FJM84KTCKZ":3,"skill-same:01M75Y60FSF8R2J3FJM84KTCKZ":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75Y60FSF8R2J3FJM84KTCKZ","local-csv-report",null,"Use when the task needs to summarize a local CSV, convert a file into a report, create JSON from local data, analyze local exports without uploading them and remember a recurring local reporting task. Preserves evidence with SkillSpec routes, forbids, dependencies, traces, and token-savings reports","modiqo\u002Fskillspec","modiqo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F172510440?v=4","01M75Y49PC2TMQY8FYFFYR2Y6A","Modiqo","01M75Y49Q47S75MS68C2Q8QVBM",668,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmodiqo\u002Fskillspec\u002Fblob\u002Fmain\u002Fexamples\u002Flocal-csv-report\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: local-csv-report\ndescription: \"Use when the task needs to summarize a local CSV, convert a file into a report, create JSON from local data, analyze local exports without uploading them and remember a recurring local reporting task. Preserves evidence with SkillSpec routes, forbids, dependencies, traces, and token-savings reports\"\n---\n\n# local csv report\n\nUse durable executor to turn a local CSV into durable JSON and text reports with file provenance, dependency checks, privacy guardrails, and optional reuse.\n\nThis skill is a thin loader for the colocated `skill.spec.yml`. The spec is the source of truth for routes, rules, dependencies, imports, resources, recipes, tests, and trace requirements. Do not treat the spec as background prose; treat it as the execution contract for this task.\n\n## Runtime Contract\n\n1. Load `.\u002Fskill.spec.yml` from this skill folder before taking task actions.\n2. When the `skillspec` CLI is available and the spec shape is unfamiliar, run `skillspec sensemake .\u002Fskill.spec.yml --view index` to learn the section roles, counts, query handles, and navigation grammar without dumping the full YAML.\n3. Then create the ordered phase plan and current-route action checklist:\n\n   ```bash\n   skillspec plan .\u002Fskill.spec.yml --input='\u003Cuser task>' --trace-dir \"${PWD}\u002F.skillspec\u002Ftraces\"\n   skillspec act .\u002Fskill.spec.yml --input='\u003Cuser task>' --run \u003Crun_dir> --phase \u003Cphase-id>\n   ```\n\n4. Strip skill invocation prefixes such as `\u002Fmy-skill`, `$my-skill`, or `\u002Fdurable-executor-spec` before passing `--input`.\n5. Preserve the emitted trace `run_dir`.\n6. Read the full phase plan and action checklist before using tools. Treat them as the active execution SOP, not as advice. The `PHASE TOOL BOUNDARY - HARD` section is the permission boundary for the next action.\n7. For each execution phase, run `skillspec act .\u002Fskill.spec.yml --input='\u003Cuser task>' --run \u003Crun_dir> --phase \u003Cphase-id>` before acting, record phase progress in `\u003Crun_dir>\u002Fexecution.jsonl`, then run `skillspec progress show .\u002Fskill.spec.yml --run \u003Crun_dir>` to see completed, current, blocked, and remaining phases.\n8. Pull active details with `skillspec query .\u002Fskill.spec.yml \u003Chandle> --view summary` and relationship edges with `skillspec refs .\u002Fskill.spec.yml \u003Chandle> --view summary`. Prefer precise handles such as `rule:\u003Cid>`, `rule:\u003Cid>.forbid`, `command:\u003Cid>.requires`, and `state:\u003Cid>.next` over reading the whole spec.\n9. Before every substrate\u002Ftool call, apply the phase tool boundary and checklist allow\u002Fdeny questions. Any unlisted tool, data source, execution substrate, provider, adapter, CLI, browser mode, API, or skill requires explicit user permission before use. The selected route and matched rules override lower-level skill defaults and generic tool preferences.\n10. When the CLI is available after a trace exists, run `skillspec trace align .\u002Fskill.spec.yml --decision-trace \u003Crun_dir>` and, when structured action evidence exists, add `--execution-trace \u003Crun_dir>\u002Fexecution.jsonl`. The command writes `\u003Crun_dir>\u002Falignment.json`; report the alignment status, meaning, model layers, evidence gaps, user-facing proof rows, summary, and trace path.\n11. If `skillspec plan`, `skillspec act`, or `skillspec progress` is unavailable, fall back to `skillspec decide`, then manually construct the same ordered phase checklist and progress notes before using tools. If the CLI is unavailable, read `skill.spec.yml` directly and apply the same contract manually. Do not expand this loader into a second source of truth.\n\n## Authoring And Revision Contract\n\nWhen importing, creating, revising, or extending this SkillSpec-backed skill, use the embedded grammar teacher before editing `skill.spec.yml`:\n\n```bash\nskillspec grammar sensemake --view index\nskillspec grammar sensemake --view porting\nskillspec grammar checklist --for import-skill\n```\n\n- Treat the checklist as the review gate for semantic edits: activation, routes, rules, elicitations, imports\u002Fresources, commands\u002Fdeps, procedures, tests, proof, and contract quality.\n- Fill or update a coverage matrix with `prose_span | obligation | skillspec_construct | confidence | status | review_note` before installing or releasing a changed skill.\n- Use `skillspec grammar schema --json` when a harness needs the exact embedded JSON schema.\n- Do not patch YAML by memory when the binary can teach the current grammar. Run the grammar commands again after CLI upgrades or when a spec shape is unfamiliar.\n\n## Durable Handoff Contract\n\nThis skill participates in agent-mediated durable execution. There is no runtime handoff engine: the agent reads the active SkillSpec contracts, carries the handoff packet in context, and preserves the declared evidence.\n\n- If a durable handoff packet is present, preserve its `workspace`, `trace_dir`, `return_to`, `branch_id`, and `execution_policy` fields.\n- If no durable handoff packet is present and the task asks for remembered evidence, future recall, reuse, trace, alignment, or durable execution, route through `durable-executor` first unless the user explicitly requests direct\u002Fno-rote execution.\n- If `durable_context.active` is true, do not route the whole task back to `durable-executor`; use `durable-executor` only as the execution substrate and then return to `return_to`.\n- This skill owns its domain interpretation and validation. `durable-executor` owns workspace, trace, evidence, command substrate, final alignment, token-savings, and recall\u002Fcrystallization closure when it initiated the handoff.\n- Any CLI, shell command, local process, package command, API fallback, or provider command must use the durable execution substrate, normally a rote adapter or `rote exec --`, unless the active spec or user explicitly allows direct execution.\n- On completion, emit a return packet with status, selected route, skill metadata, artifacts, evidence handles, blockers, and trace paths, then hand back to `return_to` for final closure.\n- For parallel work, keep one top-level workspace but use branch-scoped `branch_id`, trace paths, evidence labels, and artifact directories.\n\n## How To Execute The Structure\n\nBefore the first task action, use `skillspec plan` and `skillspec act` to convert the decision output and relevant spec sections into an ordered phase plan plus a current-route OODA checklist:\n\n- `route`: the selected route is the strategy to use. If no route is selected, stop and ask for the missing task shape instead of inventing a fallback.\n- execution plan: if the selected route has `execution_plan`, execute its phases in order before using any tool outside the current phase. A later handoff phase does not license skipping an earlier shell or adapter phase. If a phase declares `jumps`, take the first matching jump condition and continue at the named phase.\n- phase tool boundary: `skillspec act` renders the effective `tool_boundary` inherited from entry, route, and phase. Treat it as hard. If a needed tool or substrate is not listed, stop and ask permission before using it.\n- route handoff: if the selected route has `handoff`, treat it as a hard execution boundary. Follow the handoff target and boundary before using tools from the current skill; `stop_current_skill` means do not continue current-skill execution except to pass the declared context.\n- `matched_rules`: these are active obligations, not explanatory decoration. Use each rule's `reason`, `prefer`, `forbid`, `elicit`, and `after_success` fields to constrain the next action.\n- `forbid`: forbids are hard negative constraints on behavior. They block substitutions even when a convenient tool is available. If a forbidden action seems necessary, stop and ask for explicit user approval or a different route; do not silently do it.\n- user constraints: carry explicit user instructions into the same checklist. The spec adds structure; it does not erase the user's constraints.\n- `elicit`: ask the required question before irreversible work, side effects, installs, auth steps, or broad exploration.\n- `dependencies`: prove readiness for the active route, command, recipe, or code block before using it. Prefer command-scoped checks such as `skillspec deps check .\u002Fskill.spec.yml --command \u003Cid>` when a command id is known.\n- dependency evidence: a missing environment variable only proves that variable is absent; it does not prove that auth, API keys, browser sessions, keychains, vaults, or CLI-native credentials are absent. When auth can live outside env, prove readiness with the declared command, adapter, browser, or dependency check instead of grepping env.\n- `imports` and `resources`: load only the items required by the active route\u002Frule\u002Frecipe\u002Fcode, plus anything marked `always`.\n- `commands`, `recipes`, and `code`: use declared templates and ordered steps as the allowed execution surface. Check their `requires` fields first, preserve outputs as evidence, and do not replace them with unrelated tools unless the active contract allows that substitution.\n- `after_success` and closures: these are completion obligations. Do them before the final response, or report why they remain unproven.\n\nRepeat the checklist before every tool call. If a lower-level skill or generic tool default conflicts with the selected route, follow the selected route. If the next tool is forbidden, stop and report that the SkillSpec blocks it.\n\nIf every allowed route is blocked by missing dependencies, auth, permissions, or a forbid, report the blocker and ask how to proceed. Do not switch to native search, raw shell, browser automation, direct API calls, or installs just because they are available in the harness.\n\n## Quick Commands\n\n```bash\nskillspec sensemake .\u002Fskill.spec.yml --view index\nskillspec plan .\u002Fskill.spec.yml --input='\u003Cuser task>' --trace-dir \"${PWD}\u002F.skillspec\u002Ftraces\"\nskillspec act .\u002Fskill.spec.yml --input='\u003Cuser task>' --run \"${PWD}\u002F.skillspec\u002Ftraces\u002F\u003Crun-id>\" --phase \u003Cphase-id>\nskillspec progress record \"${PWD}\u002F.skillspec\u002Ftraces\u002F\u003Crun-id>\" phase-completed \u003Cphase-id> --evidence-kind rote_response --evidence-ref \u003Cref>\nskillspec progress show .\u002Fskill.spec.yml --run \"${PWD}\u002F.skillspec\u002Ftraces\u002F\u003Crun-id>\"\nskillspec validate .\u002Fskill.spec.yml\nskillspec imports check .\u002Fskill.spec.yml\nskillspec test .\u002Fskill.spec.yml\nskillspec deps check .\u002Fskill.spec.yml\nskillspec query .\u002Fskill.spec.yml rule:\u003Cid> --view summary\nskillspec refs .\u002Fskill.spec.yml rule:\u003Cid> --view summary\nskillspec query .\u002Fskill.spec.yml command:\u003Cid>.requires\nskillspec decide .\u002Fskill.spec.yml --input='\u003Cuser task>' --trace-dir \"${PWD}\u002F.skillspec\u002Ftraces\"\nskillspec explain .\u002Fskill.spec.yml --input='\u003Cuser task>' --trace-dir \"${PWD}\u002F.skillspec\u002Ftraces\"\nskillspec trace align .\u002Fskill.spec.yml --decision-trace \"${PWD}\u002F.skillspec\u002Ftraces\u002F\u003Crun-id>\" --execution-trace \"${PWD}\u002F.skillspec\u002Ftraces\u002F\u003Crun-id>\u002Fexecution.jsonl\"\n```\n\n## Completion Report\n\nWhen reporting completion, always include the selected route, the SkillSpec trace `run_dir`, the persisted `\u003Crun_dir>\u002Falignment.json`, and the compact `skillspec trace align` completion summary. Do not report a bare `unproven`; if alignment is incomplete, use `Alignment: partial` plus specific `Missing proof` rows from the align output. Command proof must name only the command basename, never raw args.\n\nAlways include token usage. If no stats were recorded, write `Token consumption: not recorded` and `Token savings: not recorded`; do not invent savings. When query-reduction stats exist, state the cached response tokens, extracted query-result tokens, saved-token delta, and reduction percentage. When rote workspace stats exist, include measured context-window\u002FAPI tokens and explain that full evidence is outside the prompt in the workspace and can be retrieved by id\u002Ffile instead of reloaded into context.\n\nMinimum final response shape:\n\n- `Result`: answer the user's task directly.\n- `Evidence`: workspace name plus important response ids\u002Ffiles the user can query later.\n- `Alignment summary`: include `Decision replay`, `Phase order`, `Requirements`, one or more `Missing proof` rows, `Forbidden actions`, and `Alignment` exactly as reported by `skillspec trace align`.\n- `Token usage`: include `Token consumption` and `Token savings` exactly as reported by `skillspec trace align`; say `not recorded` when absent.\n- `SkillSpec`: selected route, trace run directory, align status, status meaning, and proof rows that map request\u002Fspec obligations to observed evidence. Never let this replace the Result, Evidence, Alignment summary, or Token usage sections.\n\n## Route Hints\n\n- `remembered_report`: Reuse a saved local report workflow\n- `local_file_report`: Build a report from local files\n- `dependency_preflight`: Check local tools before report generation\n- `crystallized_flow`: Save as a reusable local reporting flow\n- `ask_user`: Ask for missing report details\n","# local csv report\n\nUse durable executor to turn a local CSV into durable JSON and text reports with file provenance, dependency checks, privacy guardrails, and optional reuse.\n\nThis skill is a thin loader for the colocated `skill.spec.yml`. The spec is the source of truth for routes, rules, dependencies, imports, resources, recipes, tests, and trace requirements. Do not treat the spec as background prose; treat it as the execution contract for this task.\n\n## Runtime Contract\n\n1. Load `.\u002Fskill.spec.yml` from this skill folder before taking task actions.\n2. When the `skillspec` CLI is available and the spec shape is unfamiliar, run `skillspec sensemake .\u002Fskill.spec.yml --view index` to learn the section roles, counts, query handles, and navigation grammar without dumping the full YAML.\n3. Then create the ordered phase plan and current-route action checklist:\n\n   ```bash\n   skillspec plan .\u002Fskill.spec.yml --input='\u003Cuser task>' --trace-dir \"${PWD}\u002F.skillspec\u002Ftraces\"\n   skillspec act .\u002Fskill.spec.yml --input='\u003Cuser task>' --run \u003Crun_dir> --phase \u003Cphase-id>\n   ```\n\n4. Strip skill invocation prefixes such as `\u002Fmy-skill`, `$my-skill`, or `\u002Fdurable-executor-spec` before passing `--input`.\n5. Preserve the emitted trace `run_dir`.\n6. Read the full phase plan and action checklist before using tools. Treat them as the active execution SOP, not as advice. The `PHASE TOOL BOUNDARY - HARD` section is the permission boundary for the next action.\n7. For each execution phase, run `skillspec act .\u002Fskill.spec.yml --input='\u003Cuser task>' --run \u003Crun_dir> --phase \u003Cphase-id>` before acting, record phase progress in `\u003Crun_dir>\u002Fexecution.jsonl`, then run `skillspec progress show .\u002Fskill.spec.yml --run \u003Crun_dir>` to see completed, current, blocked, and remaining phases.\n8. Pull active details with `skillspec query .\u002Fskill.spec.yml \u003Chandle> --view summary` and relationship edges with `skillspec refs .\u002Fskill.spec.yml \u003Chandle> --view summary`. Prefer precise handles such as `rule:\u003Cid>`, `rule:\u003Cid>.forbid`, `command:\u003Cid>.requires`, and `state:\u003Cid>.next` over reading the whole spec.\n9. Before every substrate\u002Ftool call, apply the phase tool boundary and checklist allow\u002Fdeny questions. Any unlisted tool, data source, execution substrate, provider, adapter, CLI, browser mode, API, or skill requires explicit user permission before use. The selected route and matched rules override lower-level skill defaults and generic tool preferences.\n10. When the CLI is available after a trace exists, run `skillspec trace align .\u002Fskill.spec.yml --decision-trace \u003Crun_dir>` and, when structured action evidence exists, add `--execution-trace \u003Crun_dir>\u002Fexecution.jsonl`. The command writes `\u003Crun_dir>\u002Falignment.json`; report the alignment status, meaning, model layers, evidence gaps, user-facing proof rows, summary, and trace path.\n11. If `skillspec plan`, `skillspec act`, or `skillspec progress` is unavailable, fall back to `skillspec decide`, then manually construct the same ordered phase checklist and progress notes before using tools. If the CLI is unavailable, read `skill.spec.yml` directly and apply the same contract manually. Do not expand this loader into a second source of truth.\n\n## Authoring And Revision Contract\n\nWhen importing, creating, revising, or extending this SkillSpec-backed skill, use the embedded grammar teacher before editing `skill.spec.yml`:\n\n```bash\nskillspec grammar sensemake --view index\nskillspec grammar sensemake --view porting\nskillspec grammar checklist --for import-skill\n```\n\n- Treat the checklist as the review gate for semantic edits: activation, routes, rules, elicitations, imports\u002Fresources, commands\u002Fdeps, procedures, tests, proof, and contract quality.\n- Fill or update a coverage matrix with `prose_span | obligation | skillspec_construct | confidence | status | review_note` before installing or releasing a changed skill.\n- Use `skillspec grammar schema --json` when a harness needs the exact embedded JSON schema.\n- Do not patch YAML by memory when the binary can teach the current grammar. Run the grammar commands again after CLI upgrades or when a spec shape is unfamiliar.\n\n## Durable Handoff Contract\n\nThis skill participates in agent-mediated durable execution. There is no runtime handoff engine: the agent reads the active SkillSpec contracts, carries the handoff packet in context, and preserves the declared evidence.\n\n- If a durable handoff packet is present, preserve its `workspace`, `trace_dir`, `return_to`, `branch_id`, and `execution_policy` fields.\n- If no durable handoff packet is present and the task asks for remembered evidence, future recall, reuse, trace, alignment, or durable execution, route through `durable-executor` first unless the user explicitly requests direct\u002Fno-rote execution.\n- If `durable_context.active` is true, do not route the whole task back to `durable-executor`; use `durable-executor` only as the execution substrate and then return to `return_to`.\n- This skill owns its domain interpretation and validation. `durable-executor` owns workspace, trace, evidence, command substrate, final alignment, token-savings, and recall\u002Fcrystallization closure when it initiated the handoff.\n- Any CLI, shell command, local process, package command, API fallback, or provider command must use the durable execution substrate, normally a rote adapter or `rote exec --`, unless the active spec or user explicitly allows direct execution.\n- On completion, emit a return packet with status, selected route, skill metadata, artifacts, evidence handles, blockers, and trace paths, then hand back to `return_to` for final closure.\n- For parallel work, keep one top-level workspace but use branch-scoped `branch_id`, trace paths, evidence labels, and artifact directories.\n\n## How To Execute The Structure\n\nBefore the first task action, use `skillspec plan` and `skillspec act` to convert the decision output and relevant spec sections into an ordered phase plan plus a current-route OODA checklist:\n\n- `route`: the selected route is the strategy to use. If no route is selected, stop and ask for the missing task shape instead of inventing a fallback.\n- execution plan: if the selected route has `execution_plan`, execute its phases in order before using any tool outside the current phase. A later handoff phase does not license skipping an earlier shell or adapter phase. If a phase declares `jumps`, take the first matching jump condition and continue at the named phase.\n- phase tool boundary: `skillspec act` renders the effective `tool_boundary` inherited from entry, route, and phase. Treat it as hard. If a needed tool or substrate is not listed, stop and ask permission before using it.\n- route handoff: if the selected route has `handoff`, treat it as a hard execution boundary. Follow the handoff target and boundary before using tools from the current skill; `stop_current_skill` means do not continue current-skill execution except to pass the declared context.\n- `matched_rules`: these are active obligations, not explanatory decoration. Use each rule's `reason`, `prefer`, `forbid`, `elicit`, and `after_success` fields to constrain the next action.\n- `forbid`: forbids are hard negative constraints on behavior. They block substitutions even when a convenient tool is available. If a forbidden action seems necessary, stop and ask for explicit user approval or a different route; do not silently do it.\n- user constraints: carry explicit user instructions into the same checklist. The spec adds structure; it does not erase the user's constraints.\n- `elicit`: ask the required question before irreversible work, side effects, installs, auth steps, or broad exploration.\n- `dependencies`: prove readiness for the active route, command, recipe, or code block before using it. Prefer command-scoped checks such as `skillspec deps check .\u002Fskill.spec.yml --command \u003Cid>` when a command id is known.\n- dependency evidence: a missing environment variable only proves that variable is absent; it does not prove that auth, API keys, browser sessions, keychains, vaults, or CLI-native credentials are absent. When auth can live outside env, prove readiness with the declared command, adapter, browser, or dependency check instead of grepping env.\n- `imports` and `resources`: load only the items required by the active route\u002Frule\u002Frecipe\u002Fcode, plus anything marked `always`.\n- `commands`, `recipes`, and `code`: use declared templates and ordered steps as the allowed execution surface. Check their `requires` fields first, preserve outputs as evidence, and do not replace them with unrelated tools unless the active contract allows that substitution.\n- `after_success` and closures: these are completion obligations. Do them before the final response, or report why they remain unproven.\n\nRepeat the checklist before every tool call. If a lower-level skill or generic tool default conflicts with the selected route, follow the selected route. If the next tool is forbidden, stop and report that the SkillSpec blocks it.\n\nIf every allowed route is blocked by missing dependencies, auth, permissions, or a forbid, report the blocker and ask how to proceed. Do not switch to native search, raw shell, browser automation, direct API calls, or installs just because they are available in the harness.\n\n## Quick Commands\n\n```bash\nskillspec sensemake .\u002Fskill.spec.yml --view index\nskillspec plan .\u002Fskill.spec.yml --input='\u003Cuser task>' --trace-dir \"${PWD}\u002F.skillspec\u002Ftraces\"\nskillspec act .\u002Fskill.spec.yml --input='\u003Cuser task>' --run \"${PWD}\u002F.skillspec\u002Ftraces\u002F\u003Crun-id>\" --phase \u003Cphase-id>\nskillspec progress record \"${PWD}\u002F.skillspec\u002Ftraces\u002F\u003Crun-id>\" phase-completed \u003Cphase-id> --evidence-kind rote_response --evidence-ref \u003Cref>\nskillspec progress show .\u002Fskill.spec.yml --run \"${PWD}\u002F.skillspec\u002Ftraces\u002F\u003Crun-id>\"\nskillspec validate .\u002Fskill.spec.yml\nskillspec imports check .\u002Fskill.spec.yml\nskillspec test .\u002Fskill.spec.yml\nskillspec deps check .\u002Fskill.spec.yml\nskillspec query .\u002Fskill.spec.yml rule:\u003Cid> --view summary\nskillspec refs .\u002Fskill.spec.yml rule:\u003Cid> --view summary\nskillspec query .\u002Fskill.spec.yml command:\u003Cid>.requires\nskillspec decide .\u002Fskill.spec.yml --input='\u003Cuser task>' --trace-dir \"${PWD}\u002F.skillspec\u002Ftraces\"\nskillspec explain .\u002Fskill.spec.yml --input='\u003Cuser task>' --trace-dir \"${PWD}\u002F.skillspec\u002Ftraces\"\nskillspec trace align .\u002Fskill.spec.yml --decision-trace \"${PWD}\u002F.skillspec\u002Ftraces\u002F\u003Crun-id>\" --execution-trace \"${PWD}\u002F.skillspec\u002Ftraces\u002F\u003Crun-id>\u002Fexecution.jsonl\"\n```\n\n## Completion Report\n\nWhen reporting completion, always include the selected route, the SkillSpec trace `run_dir`, the persisted `\u003Crun_dir>\u002Falignment.json`, and the compact `skillspec trace align` completion summary. Do not report a bare `unproven`; if alignment is incomplete, use `Alignment: partial` plus specific `Missing proof` rows from the align output. Command proof must name only the command basename, never raw args.\n\nAlways include token usage. If no stats were recorded, write `Token consumption: not recorded` and `Token savings: not recorded`; do not invent savings. When query-reduction stats exist, state the cached response tokens, extracted query-result tokens, saved-token delta, and reduction percentage. When rote workspace stats exist, include measured context-window\u002FAPI tokens and explain that full evidence is outside the prompt in the workspace and can be retrieved by id\u002Ffile instead of reloaded into context.\n\nMinimum final response shape:\n\n- `Result`: answer the user's task directly.\n- `Evidence`: workspace name plus important response ids\u002Ffiles the user can query later.\n- `Alignment summary`: include `Decision replay`, `Phase order`, `Requirements`, one or more `Missing proof` rows, `Forbidden actions`, and `Alignment` exactly as reported by `skillspec trace align`.\n- `Token usage`: include `Token consumption` and `Token savings` exactly as reported by `skillspec trace align`; say `not recorded` when absent.\n- `SkillSpec`: selected route, trace run directory, align status, status meaning, and proof rows that map request\u002Fspec obligations to observed evidence. Never let this replace the Result, Evidence, Alignment summary, or Token usage sections.\n\n## Route Hints\n\n- `remembered_report`: Reuse a saved local report workflow\n- `local_file_report`: Build a report from local files\n- `dependency_preflight`: Check local tools before report generation\n- `crystallized_flow`: Save as a reusable local reporting flow\n- `ask_user`: Ask for missing report details\n",{"name":5,"description":7},"main","f4d9ab57aa239829aee47b2f563b309067f2d43e","examples\u002Flocal-csv-report",43,"https:\u002F\u002Fgithub.com\u002Fmodiqo\u002Fskillspec","https:\u002F\u002Fskillspec.sh","https:\u002F\u002Fgithub.com\u002Fmodiqo","2026-08-09 16:13:21",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add modiqo\u002Fskillspec --skill local-csv-report",{"tool":38,"command":39},"bunx","bunx skills add modiqo\u002Fskillspec --skill local-csv-report",{"tool":41,"command":42},"pnpm","pnpm dlx skills add modiqo\u002Fskillspec --skill local-csv-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmodiqo\u002Fskillspec\u002Fblob\u002Fmain\u002Fexamples\u002Flocal-csv-report\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"skill.spec.yml","REFERENCE","参考文档",11415,"https:\u002F\u002Fgithub.com\u002Fmodiqo\u002Fskillspec\u002Fblob\u002Fmain\u002Fexamples\u002Flocal-csv-report\u002Fskill.spec.yml",[53,60,66,73,80,87],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M75Y8K6109GPWX0Y054ED9WB","skillspec","Multiplex SkillSpec post-install setup: inspect skill\u002Frepo shape with doctor, map multi-skill and plugin-shaped repositories before fanout import, assess a skill or plugin's security boundary — what it could reach if executed, ranked by risk (critical\u002Fhigh\u002Fmedium\u002Flow), with a clickable-evidence tree — and gate or install it safely before it lands on disk, import existing SKILL.md skills from local folders or public URIs, inspect installed status, install compiled workspaces with entry\u002Fsupport visibility planning, install\u002Fupdate\u002Fenable\u002Fdisable router mode, optionally install\u002Fupdate\u002Fenable\u002Fdisable\u002Fdelete durable-executor, create specs from observed durable execution workspaces, revise SkillSpec YAML, and prove value before install or release. Use for skillspec, \u002Fskillspec, skillspec setup, post install setup, assess skill security, is this skill safe, what can this skill reach, scan a skill or plugin, security analysis of a skill, boundary check, gate a skill or plugin install, check a skill before installing, install this skill safely, pull a skill or plugin, import SKILL.md, import existing skill, port skill, what is the shape of this skill, what is the shape of skill, shape of skill, skill shape and source shape. Use when the task needs to run SkillSpec post-install setup inside the harness prompt, inspect the shape of a skill, skill folder, assess what a skill could reach, or gate a skill or plugin before installing it","https:\u002F\u002Fgithub.com\u002Fmodiqo\u002Fskillspec\u002Fblob\u002Fmain\u002Fskills\u002Fskillspec\u002FSKILL.md",[],[],{"skillNo":61,"name":55,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M75Y8D56NV5SYNR5F5HYBEEG","Multiplex SkillSpec post-install setup: inspect skill\u002Frepo shape with doctor, map multi-skill and plugin-shaped repositories before fanout import, import existing SKILL.md skills from local folders or public URIs, inspect installed status, install compiled workspaces with entry\u002Fsupport visibility planning, install\u002Fupdate\u002Fenable\u002Fdisable router mode, optionally install\u002Fupdate\u002Fenable\u002Fdisable\u002Fdelete durable-executor, create specs from observed durable execution workspaces, revise SkillSpec YAML, and prove value before install or release. Use for skillspec, \u002Fskillspec, skillspec setup, post install setup, import SKILL.md, import existing skill, port skill, what is the shape of this skill, what is the shape of skill, shape of skill, skill shape and source shape. Use when the task needs to run SkillSpec post-install setup inside the harness prompt, inspect the shape of a skill, skill folder","https:\u002F\u002Fgithub.com\u002Fmodiqo\u002Fskillspec\u002Fblob\u002Fmain\u002Fplugins\u002Fskillspec\u002Fskills\u002Fskillspec\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M75Y8AX0V7NP36ES5Y4EJ1JJ","example-browser-skill","Use when the user asks to browse a page.","https:\u002F\u002Fgithub.com\u002Fmodiqo\u002Fskillspec\u002Fblob\u002Fmain\u002Ffixtures\u002Fskills\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M75Y88HBD7JCSB9HR4C9KXE4","wrapped-exec","Install the project toolchain before running the build.","https:\u002F\u002Fgithub.com\u002Fmodiqo\u002Fskillspec\u002Fblob\u002Fmain\u002Ffixtures\u002Feffects\u002Fwrapped-exec\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M75Y86991J3KXNA6MD06JTHE","unmapped-payload","Generate a release checklist from the current milestone.","https:\u002F\u002Fgithub.com\u002Fmodiqo\u002Fskillspec\u002Fblob\u002Fmain\u002Ffixtures\u002Feffects\u002Funmapped-payload\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M75Y83XPS0QBZND6A58V7G8P","secret-reader","Check that AWS credentials are present before running a deployment.","https:\u002F\u002Fgithub.com\u002Fmodiqo\u002Fskillspec\u002Fblob\u002Fmain\u002Ffixtures\u002Feffects\u002Fsecret-reader\u002FSKILL.md",[],[]]