一键导入
plugin-audit
Export an authorized Claude Code transcript and extract pico-spatial-agentic-tools skill/MCP usage records into a local support bundle.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Export an authorized Claude Code transcript and extract pico-spatial-agentic-tools skill/MCP usage records into a local support bundle.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when creating or materially updating a PICO Spatial Android/Kotlin app from Figma, screenshot/mockup, PRD, intent, hybrid sources, or a bounded panel patch, and the task requires choosing or preserving container, window model, panel hierarchy, and layout regions. NOT for SDK upgrades, empty-dir bootstrap, legacy Android porting, pure code review/refactor, old-baseline D2C A/B evaluation, or performance diagnosis.
Generic pico-cli usage guide for command discovery, command-family selection, help/version/setup checks, output formats, device targeting, safe defaults, and deciding when to hand off to spatial-emulator-usage, spatial-app-perf-diagnose, spatial-app-onboarding, or lower-level adb escape hatches.
Verify-first environment workflow for environment-dependent PICO Spatial execution. Must run before tasks that actually execute pico-cli, query the pico-spatial-knowledge MCP server, install or update plugin/host integration, or start PICO emulator/device workflows, and whenever the user asks to verify, doctor, health-check, repair, set up, update, or reconnect the PICO Spatial agent environment. Reuse a successful result once per host session unless the environment may have changed. Repair commands require explicit user authorization or a task that clearly asks for setup/update/start behavior. Checks whether pico-cli exists and reports the installed version/channel state, discovers supported commands before using doctor-style checks, and explains host restart requirements.
Helps migrate a traditional Android 2D application to a Spatial platform such as PICO OS, covering architecture preparation, Spatial SDK integration, container migration, UI adaptation, Spatial capabilities, and cross-platform compatibility.
Runs an iterative PICO Spatial SDK feature-development workflow after spatial-app-onboarding handoff. Use for follow-up requirements in an existing Spatial app: inspect AGENTS.md, plan/implement one increment, build, install, launch in the PICO emulator/device, capture screenshots, check success criteria, watch for crashes/logcat, and self-repair until verified or clearly blocked.
Create, bootstrap, scaffold, or quickstart a first working PICO Spatial SDK Android/Kotlin project through `pico-cli project create`, letting the CLI own initial template selection. All generated 2D UI must be built entirely with SpatialUI (`com.pico.spatial.ui.*`) and wrapped in `PicoTheme`; Material/Material3 is forbidden. Use for empty directories, new Spatial apps, first runnable demos, 3D model starter apps, or any request to try/start/initialize a PICO Spatial project quickly.
| name | plugin-audit |
| description | Export an authorized Claude Code transcript and extract pico-spatial-agentic-tools skill/MCP usage records into a local support bundle. |
| license | Apache-2.0 |
| allowed-tools | Bash(pico-cli plugin audit *) Bash(claude --version) Bash(codex --version) Bash(copilot --version) |
Use this skill when the user explicitly wants a local support bundle that includes:
pico-spatial-agentic-tools skill/MCP usage records from that transcript.Do not use the word diagnose as this skill's invocation name. Use plugin-audit.
Before exporting a transcript, tell the user:
session-transcript.jsonl, pico-spatial-agentic-tools-usage.json, and redaction-notes.md before sharing externally.Only run transcript export after the user has authorized it. For this skill invocation, the user's request to audit/export transcript counts as authorization.
Run from the user's project root:
pico-cli plugin audit --transcript --yes
If the user provides a specific Claude Code session id, use:
pico-cli plugin audit --session <session-id> --transcript --yes
Then report the exact output paths for:
session-transcript.jsonlpico-spatial-agentic-tools-usage.jsonpico-spatial-agentic-tools-usage.mdBy default, the command writes a timestamped directory under:
.pico-spatial-agentic-tools/plugin-audit/
Important files:
summary.md: bundle overview and file locationsmanifest.json: privacy flags and output file pathssession-transcript.jsonl: authorized local transcript export with light token-pattern redactionpico-spatial-agentic-tools-usage.json: structured usage records extracted from the transcriptpico-spatial-agentic-tools-usage.md: human-readable usage tableplugin-config.json: plugin metadata and skill listredaction-notes.md: review guidance before sharing