メニュー
Review the current session and propose new skills that could be created. Use when the user says "propose skills", "what skills could help", "find skill opportunities", "learn-skill", or after a long session to identify reusable patterns worth codifying into skills.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Add a new persistent self-hosted service on sietch, exposed on the tailnet as <name>.sole-pierce.ts.net via Tailscale Services. Use when the user asks to host, self-host, deploy, or expose a new service (web app, API, MCP server, media tool) on sietch or "my server". Covers the nix module, agenix secrets, the tailscale admin-console steps, and verification.
Check and update digest pins for third-party docker images used by selfhost services on sietch. Use when the user asks to update, bump, or check container images, image pins, or docker digests for self-hosted services.
Desktop inspection and control for the local NixOS + niri Wayland session. Use when an agent needs to see or drive the desktop - take screenshots of windows/outputs (including hidden workspaces), inspect windows/workspaces via niri, focus or launch apps (with or without stealing focus), click/type/scroll into GUI apps, run app tasks in the background on the agent workspace, or recover a confused desktop (overview open, focus lost). Route browser work to agent-browser/CDP and terminal work to tmux; use this skill's acu tool for everything the compositor and pixels must solve.
Control a dedicated Helium browser profile through agent-browser and Chrome DevTools Protocol. Use when an agent needs to drive the user's Helium browser locally or through an SSH-forwarded CDP endpoint, inspect browser state, open pages in a visible browser, collaborate on local or remote dev-server debugging, take screenshots, read snapshots, manage tabs, or validate browser behavior in the Helium profile.
Ask Codex CLI (gpt-5.5) to run local app verification that needs browser automation, desktop control, screenshots, app launching, or independent runtime inspection. This is how gpt-5.5 is invoked for computer-use work, and the preferred route for browser verification on this machine. Use when the user asks to test a flow, verify UI behavior, inspect a running app, capture screenshots, or report confirmation and feedback about implemented behavior.
Ask Codex CLI (gpt-5.5) to implement scoped code changes in the current repository, then have the current agent inspect the resulting diff and verification. This is how gpt-5.5 is invoked for implementation work. Use when the user asks to delegate implementation to Codex or gpt-5.5, when the model-selection rubric routes the work to gpt-5.5, or when a bounded task would benefit from another coding agent producing a patch.
SOC 職業分類に基づく
| name | learn-skill |
| description | Review the current session and propose new skills that could be created. Use when the user says "propose skills", "what skills could help", "find skill opportunities", "learn-skill", or after a long session to identify reusable patterns worth codifying into skills. |
| context | fork |
Review this session and identify patterns that would benefit from being codified as reusable skills.
Look for:
For each candidate skill, determine:
.claude/skills/) or user-level (~/.claude/skills/)
Skip patterns that:
/learn for those)Present each proposal in this format:
## <skill-name>
**Description:** <frontmatter description — what it does and when to trigger>
**Contains:** <brief list: instructions only, or scripts/references/assets needed>
**Placement:** <user-level | project-level> — <one-line rationale>
**Rationale:** <why this is worth a skill — what pain it prevents>
After presenting proposals, ask the user which (if any) they want to create, then hand off to /skill-creator with the relevant context.
$ARGUMENTS