Menu
Writes and edits the portfolio's pages. Reads a brief, follows the style guide, and emits the HTML into public/.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Interactive skill-map tutorial, a single "book" of parts and chapters that a first-time tester walks end to end. It opens with a live-UI prologue (the tester runs `sm`, opens the browser, and watches the map update as `.md` files are edited), then a menu of further parts (watch your agent light the map up in real time, extend skill-map with plugins/settings/slots, the CLI in depth). The skill is invoked from an empty directory and lays its fixture there directly. State persists in `tutorial-state.json` for pause/resume. Triggers: "tutorial", "sm-tutorial", "tutorial me", "run the tutorial", "ejecuta el tutorial", "test skill-map", "advanced tutorial", "go deeper", "tutorial avanzado".
Validates the portfolio's internal links before publishing. Walks every generated page and reports any link whose target is missing.
Mirrors the portfolio's pages into Notion after publishing, creating one Notion page per site page via the Notion MCP. Use it from /publish, or when the user asks to sync the site to Notion.
Validates the portfolio's internal links before publishing. Walks every generated page and reports any link whose target is missing.
Mirrors the portfolio's pages into Notion after publishing, creating one Notion page per site page via the Notion MCP. Use it from /publish, or when the user asks to sync the site to Notion.
Mirrors the portfolio's pages into Notion after publishing, creating one Notion page per site page via the Notion MCP. Use it from $publish, or when the user asks to sync the site to Notion.
| name | content-editor |
| description | Writes and edits the portfolio's pages. Reads a brief, follows the style guide, and emits the HTML into public/. |
Turns a short brief into a finished portfolio page.
public/projects.html).<!doctype html>, link the stylesheet with <link rel="stylesheet" href="/style.css">, and set a <title>.<h1>, group sections under <h2>, and reuse the shared header, nav, and footer so every page matches.Rules: plain static HTML, no framework, no client JS, one page per file. Every page follows the style guide.