jezweb
- 74 skills
- 0 followers
- 1 day ago last updated
- ▌ Setup Dotbackup · jezwebSet up dotbackup for a user — point it at their own Cloudflare R2 bucket, create the encrypted restic repository, store the secrets in their macOS Keychain, and write the config the app reads. Use when a user is installing dotbackup, says "set up my backups", connects dotbackup to Cloudflare, or the app shows the "no config" setup screen. macOS, Phase 1 (backup).
- ▌ Shipwright · jezwebThe operating method for autonomous build-and-ship work. Load it when you're about to build, code, refactor, fix, review, or ship a web app or service, or when running a self-directed work loop, and you want to work the way the rest of the toolkit expects: the loop to run, which sibling skill to invoke, how they chain, and the disciplines that keep the work honest. Not a router (the harness already picks skills) and not a task tracker — the method an agent runs WHILE doing the work. Triggers with 'shipwright', 'how should I work on this', 'start building', 'work loop', 'ship this', 'autonomous dev loop', 'what's the right way to build this'.
- ▌ Walkabout · jezwebAdd a Walkabout to an app — a guided voice tour that walks the real pages with a narration-synced moving spotlight, an ask-the-app AI guide that logs every question, and one-command narrated demo videos. Use when adding onboarding tours, in-app help, or demo/training videos to any app.
- ▌ Magpie SEO · jezwebTrack Google rankings and find competitor keyword gaps with Magpie Pro. Use when the user wants to track their rankings, see where they rank for a keyword, ask "am I ranking", find what keywords competitors rank for, or run a keyword-gap analysis.
- ▌ Magpie Audit · jezwebAudit a website's health with Magpie — overall score, Core Web Vitals, on-page SEO, security headers, robots/sitemap, and WordPress-specific checks. Use when the user wants to audit a site, check if their website is healthy, run an SEO check, understand why a site is slow, or asks "how is my website doing".
- ▌ Dns Audit · jezwebAudit a domain's DNS records — MX, SPF, DKIM, DMARC, CAA, A/AAAA — for correctness and best-practice. Use when onboarding a new domain or when an email-deliverability or SSL issue surfaces.
- ▌ Ssl Cert Renew · jezwebCheck SSL certificate expiry across managed properties; flag anything within 30 days; renew where the renewal is automatable (Let's Encrypt, Cloudflare-managed). Use weekly via cron.
- ▌ Build Plan Pack · jezweb bundleTurn a construction job folder (PDF plan sets, engineering, approvals, specs) into a queryable plan pack — synthesised sheet register, object database with provenance+confidence, takeoff quantities with shown workings, topic wiki, per-sheet renders. Use when asked to "build a plan pack", "index these plans", "do a takeoff", or process a folder of construction drawings for AI querying.
- ▌ Onboard Trade Client · jezwebTurn a trade business's existing files (past plans, quotes, price data) into a calibrated planpack workspace, ending with a trust report that re-quotes their own past jobs blind. Use when onboarding a trades business to planpack, processing a back-catalogue of past jobs, or asked to "set up my business on planpack".
- ▌ Newsletter · jezwebDraft an email newsletter — or brainstorm topics for one — from the business's own recent work and knowledge. Use when the owner says "write the newsletter", "what should this month's newsletter cover", "draft an email to the list about X".
- ▌ Install Gws · jezwebInstall the official Google Workspace CLI (gws) so the agent can drive Gmail, Drive, Docs, Sheets, Calendar, Chat and Admin from the shell. Use when the user wants Google Workspace access on a box, asks to 'install gws' / 'add Google Workspace', or a workflow needs to read mail / write a Doc / update a Sheet. gws is a shell CLI, not an MCP server — the agent calls it through its developer/shell tool.
- ▌ Social Post · jezwebTurn something worth sharing (a win, an announcement, a link, a blog post) into a platform-shaped social post — LinkedIn, X, Facebook, Instagram. Use when the owner says "post this", "share this on X", "write a LinkedIn about Y".
- ▌ Install Officecli · jezwebInstall the OfficeCLI binary (create/read/edit .docx/.xlsx/.pptx with no Microsoft Office) and register it as a Goose MCP server. Use when the user wants Office-document capabilities, asks to 'install officecli' / 'add Word/Excel/PowerPoint support', or a skill/app needs to generate Office files.
- ▌ Scan · jezwebHow the scout scans environment, industry, tools, world. Surfaces patterns that inward-focused roles wouldn't notice. Use when boss asks "what's brewing?" or scout fires on its own initiative.
- ▌ Curate · jezwebGraduate findings into wiki entries. Read findings/ in any building, judge which patterns are sturdy enough to promote, write entries via the wiki MCP. Use when the librarian is doing curation passes or when boss flags accumulated learnings for promotion.
- ▌ Extract · jezwebPull structured knowledge from unstructured sources (emails, web pages, transcripts, files, conversations) into wiki-ready shape. Use when the librarian is asked to "extract what we know about X" or to file something from external systems.
- ▌ Dispatch · jezwebHow boss routes work across the town. The discipline of delegation — when to hand off, who to, with what brief, what to expect back. Use when boss is about to do work itself instead of delegating.
- ▌ Workflows · jezwebHow to run, define, and report on Workflows — the standing jobs the cortex owns. A Workflow is a Goose recipe (the goal) + a trigger.yaml (when it fires + trust). Use when a workflow fires (a matching file lands in inbox/, a schedule, or a webhook job), when the owner says "put my X on a workflow" / "run my workflows", or to pause/change one.
- ▌ Runway Check · jezwebCompute current runway, burn trend, and forecast end-of-runway. Use when boss or bookkeeper is asked for runway, on a scheduled monthly check, or before any fundraising conversation.
- ▌ Track Candidate · jezwebMove a candidate through the hiring pipeline — sourced, contacted, first-call, case-study, offer, hired, passed. Captures notes per stage; never lets a candidate ghost-drift. Use when recruiter advances a candidate or the founder adds a new one.
- ▌ Extract Commitments · jezwebAfter filing a meeting, customer call, investor call, or any conversation entry, scan the body for explicit commitments (I'll ship X by Y, send Z by Friday) and create structured commitment entries in wiki/commitments/. Use whenever a new meeting note lands; also use to retroactively scan an existing entry for missed commitments.
- ▌ Draft Investor Update · jezwebDrafts the monthly investor update — pulls metrics, surfaces wins + struggles, formats per the founder's voice. Use on the 1st of each month, or when boss asks for a draft, or when investor-relations fires a scheduled monthly routine.
- ▌ Summarise Customer Call · jezwebAfter a customer call (transcribed or hand-noted), file a structured summary to wiki/research/ and trigger extract-commitments. Use when founder finishes a call and says "@customer-success file this call" or similar.
- ▌ Kanban · jezweb bundleUse when you want a lightweight, claimable task board that lives in the repo as markdown, for parallel multi-agent work or your own backlog, where a card is a file and the folder it sits in is its status. Covers the folder-board layout, claiming and completing by moving the file, worktree-safe concurrency for a fleet, frontmatter conventions, discoverability one-liners, and an optional zero-dependency local web UI to view and drag cards. Triggers, "kanban", "task board", "track parallel agent work", "claimable work queue", "what's in flight".
- ▌ Imagine · jezwebUse when planning, to think past the immediate request and find the bigger product hiding inside it, what the users and the business will need that nobody's asked for yet. Produces a north-star vision, not a task list. The expansive counterpart to the challenge questions in plan-and-build. Triggers, "imagine", "think big", "what could this become", "where could this go", "what are we missing".
- ▌ Challenge · jezwebUse before committing to a plan or brief, to stress-test it, surface the unstated assumptions, the unknowns, the scope that will change, and the user/business needs the brief doesn't mention. The adversarial counterpart to imagine, and the planning-time counterpart to brains-trust. Triggers, "challenge this", "roast my plan", "poke holes", "what am I missing", "pressure-test", "devil's advocate", "what are my assumptions".
- ▌ Brains Trust · jezwebUse after any non-trivial build, before commit or deploy. Convene two or more frontier models from different families and providers to review the change for Critical/High/Medium/Low findings; fix cross-validated Criticals before commit and Highs before deploy. Also when the same bug won't fix on the first attempt, or for a whole-codebase pass before a release.
- ▌ Stranger Test · jezwebUse before shipping anything agents or newcomers will read cold: a README, a CLAUDE.md or workspace brief, a skill, a playbook, a template repo, onboarding docs, a production prompt or sub-agent contract. Two moves: audit every claim (derived / checkable / judgement), then run a clean-context dress rehearsal where a no-context agent actually uses the docs and reports where it guessed. Catches insider references, drifted counts, broken pointers, and stale facts the author's context papers over.
- ▌ Truth Seeking · jezwebUse whenever you're about to state or write a factual claim, a client or product fact, a KB entry, a number, a date, a piece of history, an answer presented as true. Don't write it from memory; verify it against an authoritative source and cite it, or leave the gap honestly. Plausible-sounding and true are not the same. The factual-content sibling of verify-current.
- ▌ Write Prompts · jezwebUse when writing or revising any prompt, a system prompt, an agent brief, an extraction or classification prompt, a sub-agent contract, or when a prompt-driven feature underperforms. Covers the three parts a prompt needs (goal, contract, knowledge), worked examples over templates, the directive vs goal-oriented style lever, matching model temperament to the task, right-or-null for derived facts, building minimal-first (start small, add one thing at a time, never write big and cut back), and pruning the bloat ratchet.
- ▌ Plan And Build · jezwebHow to plan and approach a non-trivial build or feature with an agent, before writing phases or code. Covers the Phase-0-refactor catch, thinking in contracts, discovering the data structure from real instances before designing it, writing the proof of done first, verifying by inspection, splitting plan from spec, trusting skills over elaborate code, the moving code-vs-agent boundary, and matching a precise brief literally with a sign-off preview before shipping. Load when starting, scoping, or planning any substantial piece of work.
- ▌ Verify Current · jezwebUse before relying on any fast-moving fact you might "know" from training, a model ID or its capabilities, an AI or HTTP API shape, a library or framework version (Vite, Astro, React, an SDK), a Cloudflare binding or wrangler config, or an MCP standard. Also fires when scoping or planning a build (read the current docs of the stack before designing how it works), and when debugging a failure that might just be an outdated CLI, SDK, or package. Your training data is stale on all of these.
- ▌ Verify Visually · jezwebUse before calling any visual or rendered output done, a UI, a layout, a generated image, a rendered document, a chart. Render the real thing and look at the actual result (playwright or Chrome screenshot, computer-use, or the project's own render/export command) before you ship it. Don't report "looks good" on something you never viewed.
- ▌ Agent Delegation · jezwebUse when about to delegate a discrete task to a sub-agent, deciding whether to spawn one at all, how much to specify it, and how to keep its work from bloating the main thread. The one-off-task layer below run-a-role-agent. Triggers, "delegate this", "spawn a sub-agent", "should this be a sub-agent or a script", "fan this out".
- ▌ Run A Role Agent · jezwebUse when setting up an ongoing agent dedicated to a role rather than a one-off task, a webmaster, researcher, bookkeeper, support triager. Covers shaping the persona and its lane, populating a specialist with real reference (not a generic shell), running it with one bounded output per run, putting it on a heartbeat, and the observer disciplines for a role that watches a live human system and may ramp up to running it (observe without consuming the signal; the observer-to-actor trust ladder). For backlog-grinding work that tunes its own procedure, see run-a-self-refining-loop.
- ▌ Orchestrate Agents · jezwebUse when deciding how to arrange agents for a piece of work: one agent or several, which pattern (single loop, pipeline, routing, parallel, orchestrator-workers, evaluator loop, triage funnel), how to match roles to model temperaments, how to bound a model-driven control loop so it's safe to trust instead of hand-coding a deterministic spine, and the mechanics that keep multi-agent work safe and cheap. The layer above agent-delegation (one-off hand-offs) and run-a-role-agent (one ongoing role).
- ▌ Reason Over Images · jezwebUse when asking a model to read, extract from, measure, count, or make judgements about images: technical drawings and plans, photos, scans, documents, screenshots. Covers what vision models do reliably (locate, read, judge) vs unreliably (measure, count precisely), reading printed values with code doing the arithmetic, the two-channel pattern (witnessed extraction vs advisory read), interview-to-discover then schema-to-ship, finding a ruler in the image, and validating across the whole distribution.
- ▌ Write Image Prompts · jezwebUse when prompting an image-generation model: a hero image, icon set, product shot, illustration, OG image, scene, or any generated visual. Covers concrete specifics over quality adjectives, specifying the world not just the subject, describing presence not absence, reference images over style prose, anchoring sets, iterating by editing, and designing for the image's job. The image sibling of write-prompts.
- ▌ Run A Self Refining Loop · jezwebUse when a role has substantial repeated work one session can't finish (enriching hundreds of records, grinding a backlog, sweeping a large catalogue) AND the work keeps teaching you how to do it better. Covers the tick shape, the separate state files, idempotency, queue-learnings-apply-next-tick, and the rules that keep a self-modifying loop safe. The deep end of run-a-role-agent; don't reach for it for one-offs or fixed procedures.
- ▌ Fact Check · jezwebVerify a specific claim by finding multiple authoritative sources that confirm or contradict it. Use when the user asks to fact-check, verify, or check whether something is true.
- ▌ Code Review · jezwebReview code for bugs, security issues, performance problems, and style. Use when the user pastes code, shares a file, or asks "what's wrong with this code?".
- ▌ CSV Analyse · jezweb bundleAnalyse a CSV file in the sandbox — row/column counts, column types, summary statistics for numeric columns, unique value distributions for categorical columns, and missing-value counts. Use when the user asks to explore, summarise, profile, or analyse a CSV file.
- ▌ Document QA · jezwebAnswer questions about an uploaded document (PDF, image, or text file). Use when the user has attached a file and asks something specific about it.
- ▌ Draft Email · jezwebWrite a professional email tailored to a specific recipient, purpose, and tone. Use when the user asks to draft, write, or compose an email.
- ▌ Web Research · jezweb bundleResearch a topic by searching the web, fetching the most relevant pages as markdown, and producing a well-structured summary with citations. Use when the user asks to research, investigate, find information about, or look into a topic.
- ▌ Create Report · jezwebCreate a polished visual report as an HTML artifact with charts, tables, and formatted text. Use when the user asks for a report, dashboard, analysis, or visual summary of data.
- ▌ Meeting Notes · jezwebTurn a meeting audio recording into structured notes — attendees, agenda items discussed, key decisions, action items with owners, and open questions. Save the result as a Markdown file. Use when the user attaches an audio file of a meeting or explicitly asks for meeting notes from audio.
- ▌ Morning Brief · jezwebGenerate a personalised morning briefing covering weather, news, schedule, and saved priorities. Use when the user asks for a morning brief, daily summary, or "what's happening today?".
- ▌ Review Output · jezwebDefault reviewer criteria for the with_review tool. Generic quality bar — accuracy, intent-match, no hallucinations, clarity. Use as the criteria.skill argument when calling with_review without a domain-specific reviewer skill.
- ▌ Route Finding · jezwebSessionEnd hook for routines emitting findings — picks the right channel (inbox_add / notify / approval_queue / space_send / webhook_post) and writes a short run-summary line. Routine-only.
- ▌ Summarise Url · jezwebFetch a URL and produce a structured summary with title, key points, and an action-oriented takeaway. Use when the user shares a link and asks for a summary, TL;DR, or "what's this about?".
- ▌ Compare Options · jezweb bundleEvaluate multiple choices side-by-side based on relevant criteria, then present a comparison the user can act on. Use when the user asks to compare options, choose between alternatives, or weigh up X vs Y.
- ▌ Agent Asks Tasks · jezwebUse to track open questions you owe the user (asks) and time-bounded commitments you owe yourself (tasks). Write OPEN entries when you commit; promote to CLOSED when answered/done. Survives session compaction. Adapted from goanna's asks.md/tasks.md pattern.
- ▌ Librarian Curate · jezwebWeekly cross-agent curation routine — surfaces patterns across agents, promotes stable ones into shared knowledge, writes a weekly digest into Inbox. Routine-only.
- ▌ Score Importance · jezwebCalibrates finding importance (high / medium / low) before inbox_add — used by routines for consistent thresholds. Routine-only.
- ▌ Review Email Tone · jezwebReviewer criteria for outbound email drafts via with_review. Checks tone-recipient match, professionalism, no AI tells, no placeholder leakage. Use as criteria.skill argument when reviewing email drafts before send.
- ▌ Save Research Doc · jezwebSave a piece of research, notes, or content to the user's filesystem as a well-organised markdown document with metadata. Use when the user asks to save, archive, file away, or "keep this for later".
- ▌ Git Diff Summariser · jezweb bundleSummarise a git diff into a short change description, risk assessment, and suggested commit message. Use when the user asks to review changes, draft a commit message from a diff, or wants a high-level overview of what was edited.
- ▌ Review Code Security · jezwebReviewer criteria for AI-generated code via with_review. Checks for security issues (injection, auth bypass, secret leakage), correctness, and project conventions. Use as criteria.skill when generating code that touches data, auth, or external systems.
- ▌ Rewrite For Audience · jezwebRewrite text for a different audience, tone, length, or format while preserving the core meaning. Use when the user asks to rewrite, rephrase, simplify, formalise, or adapt text for a specific audience.
- ▌ Routine Health Check · jezwebDaily meta-routine — watches every other routine for error rates, drift, and runaway cost; surfaces routine_health findings into the Inbox. Routine-only.
- ▌ Remember Conversation · jezwebReview the current conversation and save key facts to long-term memory. Use when the user asks you to remember things from this chat, save important info, or "remember this for next time".
- ▌ Extract Structured Data · jezwebExtract structured data (JSON) from messy text, documents, or web pages. Use when the user asks to extract, parse, structure, or pull data out of unstructured content.
- ▌ Review Summary Faithfulness · jezwebReviewer criteria for AI-generated summaries via with_review. Checks faithfulness to source, no hallucinated facts, appropriate length, key points preserved. Use as criteria.skill when summarising articles, documents, transcripts, or batch-task outputs.
- ▌ Reflect · jezwebEnd-of-day distillation routine — reads recent runs + findings, decides what graduates / dismisses / stays open, writes a one-paragraph day summary. Routine-only.
- ▌ Reverie · jezwebUse when an agent has had N consecutive quiet runs with nothing to do. Pivots to bounded inward consolidation (promote findings, refresh memory, audit asks) anchored in own data — NOT generic news summarisation. Adapted from goanna's reverie cycle. Routine-only; loaded by the routine that detects the quiet condition.
- ▌ Caretaker · jezwebDay-of-week rotating proactive sweep — Mon=connections / Tue=routines / Wed=skills / Thu=memories / Fri=findings / Sat=cross-cutting / Sun=weekly summary. Forces outward scan instead of inward thrash. Routine-only; load this skill into a daily routine that fires AssistantAgent. Adapted from goanna's caretaker.
- ▌ Plan Task · jezwebBreak a goal into a clear sequence of actionable steps with dependencies and estimated effort. Use when the user describes something they want to accomplish and asks for a plan, breakdown, or "how do I...".
- ▌ Roadmap · jezwebPlan and execute entire application builds. Generates phased delivery roadmaps, then executes them autonomously — phase by phase, committing at milestones, deploying, testing, and continuing until done or stuck. Modes: plan (generate roadmap), start (begin executing), resume (continue from where you left off), status (show progress). Triggers: 'roadmap', 'start building', 'resume the build', 'keep going', 'build the whole thing', 'execute the roadmap', 'what phase are we on'.
- ▌ UX Compare · jezweb bundleCompare UX patterns across multiple reference apps using pattern libraries produced by ux-extract. Reads 2+ pattern-library.md files, walks them category by category, identifies where apps converge (strong signal), where they diverge (genuine design choice), what's unique to one app, and what's absent across the set. Produces an opinionated comparison document with recommendations for a new build. No browser needed — pure markdown analysis. Trigger with 'compare UX patterns', 'how do top apps handle X', 'ux comparison', 'pattern comparison across reference apps'.
- ▌ Codex Review · jezweb bundleRun an independent code review using the OpenAI Codex CLI in headless mode. Gets a second opinion from a different model family (the current Codex models) on recent changes, a PR, a commit, or the whole app — covering bugs, regressions, security, data consistency, UX/state bugs, performance risks, and testing gaps. Saves a severity-prioritised report to .jez/reviews/. Triggers: 'codex review', 'review with codex', 'independent code review', 'what does codex think', 'get codex to review'.
- ▌ Deep Research · jezwebDeep research and discovery before building something new. Explores local projects for reusable code, researches competitors, reads forums and reviews, analyses plugin ecosystems, investigates technical options, and produces a comprehensive research brief. Three depths: focused (30 min), wide (1-2 hours), deep (3-6 hours). Triggers: 'research this', 'discovery', 'explore the space', 'what should I build', 'competitive analysis', 'before I start building', 'research before coding'. Not for cited fact-checking research reports (a separate harness does those); this is pre-build product discovery.
- ▌ Elevenlabs Agents · jezweb bundleBuild conversational AI voice agents on the ElevenLabs platform. Configure agent + tools + knowledge base, integrate SDK (React / React Native / Swift / JS / server-side), test, deploy. Use whenever the user mentions ElevenLabs, building a voice agent, an AI phone system, an AI receptionist, conversational AI, or troubleshooting deprecated @11labs packages, webhook errors, CSP violations, localhost allowlist, or tool parsing errors.
- ▌ Aussie Business English · jezwebAustralian business English for professional writing — warm, direct, EN-AU spelling (colour, organise, centre), no filler words. Use whenever the user is writing for an Australian audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to drafting, editing, and tone-checking professional text.