Claude Skills by Ulef1005

The benchbook visual language — palette, type, mark, layout and copy rules. Use whenever building or changing anything visible: the wiki site, README assets, social cards, diagrams, slides.

Process a source — a file, a URL, a video, or dictation in chat — into structured wiki pages. Use when the user says 'ingest [file/url]', 'process this', 'let's ingest [subject]', or drops a file in raw/ and wants it turned into wiki pages. Also triggers when the user pastes a URL, PDF path, or image path directly. Orchestrates the full INGEST workflow: detect input, extract content, propose domain, load domain rules, discuss takeaways, run domain dispatch, then update index, overview and log...

Run a full LINT check on the wiki. Use when the user says 'lint the wiki', 'run lint', or '/lint'. Runs the mechanical checker, adds the judgement checks on top, writes a dated report, and syncs todo.md. Report-only for wiki content — never edits page bodies or frontmatter. Offers opt-in archival for stale raw files and log overflow, and never moves anything without confirmation.

Load and orient to an existing wiki project. Use when the user says \"let's work on [project]\", 'open project [name]', 'continue [project]', 'pick up where we left off on X', or wants to resume an active or planned project. Reads the page and presents status, recent log entries and open questions so the user can immediately decide what to do next. Use whenever the user references a project by name and wants to do something with it — even without saying 'open'.

Stress-test an existing project's plan through a one-question-at-a-time interview before anything gets built. Use when the user says 'review this project', 'stress-test [project]', 'interview me about [project]', \"let's think through [project]\", 'poke holes in this plan', or wants to challenge a plan rather than just orient to it (that's wiki-project-open). Pairs with the plan approval gate — this is the skill that uses the moment where the plan exists and nothing has been built.

Create a new project page in the wiki. Use when the user says 'start a project', 'let's track a new project', 'create project [name]', 'new wiki project', 'I want to begin tracking X', or expresses intent to start, plan or track something new — even if they don't say 'wiki'. Asks for the name and goal, creates the page with all required sections and a GATED plan stub, updates the index, and appends to the log. Never begins implementation work.

Close the current wiki work session: verify what changed, log new pages, run verification gates, commit and push. Use when the user says 'close the session', \"we're done\", 'wrap up', \"that's all for today\", 'end session', or signals they're finished. Run this at the end of any session that produced changes.

Capture a book recommendation into the wiki as a ranked to-read candidate. Use when the user pastes a link or screenshot text recommending a book, or says 'add this book', 'someone recommended X', 'add X to my to-read', 'should I read X', 'have I read X', or 'do I already have X'. Always checks the existing library across every shelf first — a recommendation for something already read or abandoned is reported as a collision, not filed as new. Fetches a real blurb and writes the candidate page...

Turn a recipe from anywhere — a link, a photo, a cookbook page, or dictation in chat — into a validated Cooklang file plus its wiki companion page. Use when the user says 'add this recipe', 'capture this recipe', 'save this recipe', pastes a recipe URL, or dictates one. Confirms category and dietary status, checks for an existing recipe with the same slug, writes the .cook and .md pair, validates the Cooklang, and derives the structured fields. Never invents quantities.

Capture a game into the wiki — a recommendation, a purchase, or one you just started. Use when the user says 'add this game', 'someone recommended [game]', 'I bought [game]', 'add [game] to my backlog', 'do I own [game]', 'have I played [game]', or pastes a store link. Checks ownership across every status first — bundles and sales mean you own more than you think — then files the game page with the required fields for its status.

Capture why you stopped playing a game, while you still remember. Use when the user says 'I dropped [game]', \"I'm done with [game]\", 'stopped playing [game]', 'shelving [game]', 'bounced off [game]', or otherwise signals they've stopped. Distinguishes dropped from shelved, captures the hour count and the specific reason, and records whether anything would bring them back.

Create an install/deploy runbook for a new self-hosted service. Use when the user says 'create a deploy runbook for X', 'write an install runbook for X', 'we need to deploy X', 'runbook for [service]', or is about to plan a new self-hosted service. Scaffolds the full page — prerequisites, stack files, admin account, service-specific phases — plus a pre-filled Fleet Integration phase, so the boring integration steps never get re-derived, re-typed, or silently skipped.

Research a topic across multiple sources, synthesise what's actually being said, then optionally file the result as a wiki source page. Use when the user says 'research [topic]', 'what's new with [topic]', 'what are people saying about [topic]', 'look up recent discussion on [topic]', or wants fresh external research captured into the wiki. Presents takeaways first, then asks whether to ingest — as a source-only page or a full INGEST with entity pages.