Menu
Curate whistlegraph.org and make authenticated, narrowly scoped frontend changes through the Whistlegraph Desk Git workflow.
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
Orchestrate Aesthetic Computer illustrations across OpenAI, fal.ai, and future backends. Use when a user says illy, asks to generate or edit campaign art, covers, panels, storyboards, visual variants, compare image providers, or configure a marketing/pop media pipeline.
Orchestrate Aesthetic Computer illustrations across OpenAI, fal.ai, Codex built-in image generation, and future backends. Use when a user says illy, asks to generate or edit campaign art, covers, panels, storyboards, visual variants, or wants to compare image providers or configure a marketing/pop media pipeline.
Turn an Aesthetic Computer essay into a published spoken-word "reading" (podcast episode) in @jeffrey's ElevenLabs voice — narrate, score a lo-fi bed, make a caption video, and publish to Buzzsprout (which fans out to Spotify/Apple/YouTube). Use when @jeffrey says "make a reading of <essay>", "turn this essay into a podcast", "publish <month> as a reading", or references the AC Readings podcast.
Download a whistlegraph TikTok and read its musicality (tempo, key, whistled-melody note sequence) as the front of the /pop track pipeline. Use when @jeffrey says "grab this whistlegraph", "analyze this tiktok's audio", "turn this whistlegraph into a pop track", or pastes a tiktok.com/@whistlegraph link.
| name | whistlegraph |
| description | Curate whistlegraph.org and make authenticated, narrowly scoped frontend changes through the Whistlegraph Desk Git workflow. |
Use the whistlegraph_* MCP tools whenever the user asks to inspect, edit, commit,
publish, deploy, or roll forward the Whistlegraph frontend. Do not substitute raw
shell Git commands for the publishing tools.
The user must run Codex from an aesthetic-computer checkout whose origin can
push to the Tangled knot. Authentication comes from the shared Aesthetic Computer
session in ~/.ac-token; if it is absent or expired, tell the user to run
ac-login and retry.
whistlegraph_whoami and confirm the server grants maintainer access.whistlegraph_begin_change with a short summary. This creates an isolated
worktree from the current origin/main; it never uses or alters the user's
working tree.whistlegraph_list_frontend, whistlegraph_read_frontend, and
whistlegraph_diff_change.whistlegraph_replace_frontend or
whistlegraph_write_frontend. The server is intentionally limited to
system/public/whistlegraph.org/**.whistlegraph_validate_change. Resolve every reported error before
publishing.whistlegraph_publish_change unless the user already explicitly asked
to publish.main only if the original base is still current, and asks the
Auth0-protected Desk endpoint to deploy that exact SHA.If main moved, begin a fresh change and reapply the desired edit. Never force
push, reset shared history, bypass validation, edit outside the allowlist, or ask
for deployment secrets.
Archive metadata edits remain available in the web Desk at https://whistlegraph.org/desk. This first MCP release focuses on frontend files and the Git/deployment path.