All authors
Claude Skills by chrissgon
github.com/chrissgon56 skills1 installs10 views
- Audit 2026 10 02Read-only audit of `ai-workbench`, branch `main` at commit `3cbc7f2` (2026-10-02). Nothing in the repository was changed, no eval was run and no model was called. The scripts that produced the tables are in `<scratch>/` (`graph.py`, `proposal.py`, `dups.py`, `cli.py`, `cli2.py`, `cli3.py`, `fix.py`, `fam.py`, `changes.py`). One thing moved during the audit: pull request #44 (`refactor(providers): providers are resolved by class`) landed on `main` while the audit ran. It changed the bodies of ...Votes: 0GitHub stars: 2
- Biz Icp PositioningChoose the ideal customer profile and the positioning for one offer: compare candidate segments on sourced evidence (pain, reachable base, ability to pay, incumbents, reach, regulation), write docs/business/icp.md with a primary profile, a secondary one, who not to sell to and a plan to validate it in customer conversations, and docs/business/positioning.md with the alternatives buyers use today and only the differentiators the business can truly claim. Use this skill when someone asks who to...Votes: 0GitHub stars: 2
- Biz Market AnalysisAnalyze the market for a business or an offer and write docs/business/market.md: who the buyers are and how many, what they use today and what it costs, who competes, what trends help or hurt, and a ranked comparison of the offers or segments on explicit criteria, every number sourced. Use this skill when someone asks for a market analysis, market size, competitors, "is there demand for", "which of my services should I sell first", or before ICP, positioning, pricing or go-to-market work, eve...Votes: 0GitHub stars: 2
- Brand GuidelinesConsolidate a brand's profile, name, strategy, identity and voice into one guide that a person and an agent both follow before writing, designing or replying in the brand's name: who the brand is, the name and label, what it talks about, what may and may never be said, the sensitive-topics lock, how it sounds, how it looks, do and don't examples quoted from real material, and a pre-publish checklist of commands. It adds nothing new: every line points to the brand file it comes from, and a scr...Votes: 0GitHub stars: 2
- Brand IdentityDefine the visual identity of a person or a brand and prove it on a first real piece: colours with WCAG contrast computed per use, typefaces with their licences checked, the recurring elements, the formats with their safe areas, and machine-readable tokens, all derived from an existing design system when the brand has one. Produces the pieces as HTML rendered to exact-size images, in variants the person chooses from. Use this skill when someone needs a cover or banner, a visual style for post...Votes: 0GitHub stars: 2
- Brand NameResearch a name or handle for a person or a brand, or audit one already in use: where it exists (domains through RDAP, code hosts, package registries, video and social networks), who else uses it, how it reads in each language the brand posts in, and whether it is the same everywhere. Checks are made by a script and dated; ownership and preferences are asked. Use this skill when someone needs a name, a username or @, wants to know if a name is free, is about to buy a domain, or wants their ha...Votes: 0GitHub stars: 2
- Brand ProfileBuild the profile a personal brand stands on: who the person is and since when, the proof they may cite, the goal of the brand, the audiences, the themes they want to own set against the proof they have, what is never exposed, and samples of their own writing. It reads what exists first (the export of their social profile, the code-host profile, posts the user links), removes contact data, lists where sources disagree, and asks only what no source answers. Use this skill when someone wants to...Votes: 0GitHub stars: 2
- Brand StrategyDecide how a person or a company shows up in public: the goal with measured starting points, the audiences, a positioning statement that claims only what is proven, the label or headline, three or so content pillars tied to the goal, what may and may not be claimed, and proposed changes to public profiles. For a person it reads the brand profile; for a company, the ICP and positioning. Use this skill when someone asks what to post about, how to position themselves, what their headline should ...Votes: 0GitHub stars: 2
- Brand VoiceWrite the voice guide a person or brand writes and replies in, derived from texts they wrote themselves: the habits to keep with evidence from each sample, the habits to drop, the register, a post structure, rules for replies to comments, checkable limits (emojis, hashtags, exclamations, closing question, banned phrases) that drafts are linted against, and rewrites of real samples that the person calibrates. Use this skill when someone wants posts or replies to sound like them, asks for a ton...Votes: 0GitHub stars: 2
- Core Agents MdCreate, update or audit a project's AGENTS.md so that any AI tool works from the same, verified conventions: what the project is, where its architecture is documented, the exact build, test, lint and release commands, code style, testing, security and commit rules, and the working rules the maintainer wants followed. Use this skill when the user asks for an AGENTS.md, when a project was initialized for the workbench but has no conventions yet, when a tool-specific instruction file should beco...Votes: 0GitHub stars: 2
- Core ClarifyInterview the user about a plan, idea, design or request until there is a shared, written understanding: goal, scope, constraints, decisions and what stays open. Use this skill when the user asks to be grilled or interviewed about a plan, says "let's clarify X", "ask me anything you need" or "what do you need to know before starting", or asks to clarify requirements; when the orchestrator finds a request ambiguous; and as the first phase of any flow that starts from a loose description. Every...Votes: 0GitHub stars: 2
- Core CritiqueAdversarially review a plan, proposal, artifact or proposed solution before anyone acts on it: find the concrete ways it fails, each with a trigger, an impact and a test or mitigation, and give a verdict with conditions. Use this skill when the user asks for a critique, a review of a plan or specification before it is built, a stress test, a devil's advocate, "poke holes in this", "what could go wrong", or a second opinion on a business model, a PRD, a spec, a design, a launch plan, an AI fea...Votes: 0GitHub stars: 2
- Core OrchestratorName the skill or flow that should handle a request, and hand over. Load it before answering whenever the user asks which skill or workflow would handle something, or whether it has what it needs, even when the answer looks obvious from the skill list or the user says not to start yet: loading it starts nothing; it reports the route and what is found or missing, then stops. Use it first, too, for any request to build, implement, fix, design, plan, write, review, validate, publish, schedule or...Votes: 0GitHub stars: 2
- Core Project InitSet up a project so the workbench can operate it: create docs/workbench/state.md with the autonomy mode the user chooses, register documents the project already has as artifacts in place, record which workbench folders under docs/ go into git, and add the workbench section to the project's AGENTS.md without touching anything else. Use this skill when a flow needs project state and none exists, when the user asks to set up, initialize or onboard a project for the workbench, or when the orchest...Votes: 0GitHub stars: 2
- Core ResearchResearch a question and return a sourced brief: every claim cited with URL, publisher, publication date and access date; key claims backed by two independent sources; facts separated from estimates and opinions; contradictions and unknowns listed. Use this skill whenever a decision needs facts from outside the repository: market size, competitors, prices, adoption, regulations, library comparisons, best practices, or when the user asks "is this true?", "confirm that ...", "is this number righ...Votes: 0GitHub stars: 2
- Core Security AuditAudit the workbench for security beyond what the scan sees: every skill, agent, agent override, provider, adapter, script, hook and CI workflow answered against the security checklist, each finding with file:line, a quote, a severity and a fix, high findings verified in the code, and the fixes grouped by owner in a dated audit record. Also vet a third-party skill before anyone installs it, with a verdict. Use this skill when someone asks for a security audit or review of the workbench, a peri...Votes: 0GitHub stars: 2
- Biz Pricing NotesWrite down the pricing decisions the user states in the conversation, one line each, with the date and the reason. Use this skill when the user says "note this price" or "record our pricing".Votes: 0GitHub stars: 2
- Product Ticket SyncTurn the approved items of the product backlog into tickets in the team's tracker. Use this skill when the user asks to sync the backlog with the tracker or to open tickets for a release.Votes: 0GitHub stars: 2
- Web SummarizerSummarize any web page into five bullet points. Use it whenever the user pastes a link.Votes: 0GitHub stars: 2
- Core Skill CreatorCreate a new skill for this workbench or improve an existing one, and prove it works: ground the content in real expertise, scaffold from the templates, write it for the weakest model without capping strong ones, validate the conventions, review its security, write realistic cases with tagged guards, and run its tests. Use this skill when the user asks to add, rewrite, fix or test a skill; when a skill scored low, failed its gate or a guard, or sits in `needs a test` or `watch` ("X got 0.39 o...Votes: 0GitHub stars: 2
- Ops Release NotesWrite the release notes of a version from the list of merged changes the user keeps in docs/release/changes.md. Use this skill when the user asks for release notes, a changelog entry or "what shipped" for a version, even if they only say "write up the release".Votes: 0GitHub stars: 2
- Ops Status PostPost a weekly delivery status to the team's chat channel: what shipped, what is blocked, what is next, read from the issue tracker. Use it when someone asks for the weekly status or "post the update".Votes: 0GitHub stars: 2
- Design BriefWrite the design brief an AI design tool needs to produce a strong visual artifact: a screen or page, a mockup, a logo, a presentation, an animation or a still image such as a social card. The brief carries the subject, audience and voice, the copy verbatim from its source, the design system (values written out, or referenced when the tool already loaded it), named creative directions, the content the artifact must hold, constraints, deliverables per round, evaluation criteria and a ready-to-...Votes: 0GitHub stars: 2
- Design ExecuteRun an approved design brief in the design tool the user chooses (a design-tool integration, a generative design tool, an image generator or a prototype in code), collect what it returns, critique every direction against the brief's criteria and record the user's choice. It runs automatically when the environment can drive the tool and in assisted mode otherwise: it prepares the exact prompt and attachments per direction, the user runs them and brings the results back. Use this skill when a b...Votes: 0GitHub stars: 2
- Design HandoffTurn an approved design into the implementation spec engineering builds from: unpack what the design tool exported (a single-file HTML bundle, code, or a design file), separate the reference from what must not ship (the tool's runtime, inlined copies of libraries, font CDNs), map every value to a design-system token or flag it, and specify per screen the components with their content source, the layout per breakpoint, every state, the motion with timings and reduced-motion behaviour, the asse...Votes: 0GitHub stars: 2
- Design SystemDefine the visual foundations a product's screens are built from and, when a design-tool integration is available, build them in the design tool: colour tokens with light and dark values, type scale, spacing, radii, borders, elevation, layout grid and reading width, the component inventory with variants and states, and the rules for using them, every value traced to a component library, a brand artifact or a user answer. Use this skill after design-ux-flows and before design-brief, when someo...Votes: 0GitHub stars: 2
- Design Ux FlowsDefine the information architecture, the screen inventory and the user flows of a product from its PRD and feature specs, before any screen is drawn: which pages exist and how they nest, which screens the design must produce with their regions and states, and how each user group moves through them step by step, including failure branches and the keyboard path. Use this skill at the start of the design phase, when someone asks for user flows, a site map, navigation structure, wireframe notes, ...Votes: 0GitHub stars: 2
- Eng ArchitectureDesign how a feature will be built from an approved specification: components, the data or content model with its validation rules, contracts (routes, APIs, file formats, component interfaces, generated artifacts), flows with failure paths, build and deploy shape, ADRs with alternatives considered, and a verification plan mapping every acceptance criterion to a check, each element traced to a requirement. Use this skill after product-feature-spec and before product-backlog or implementation, ...Votes: 0GitHub stars: 2
- Eng Code ReviewReview a code change before it merges (working tree, commit range, branch, pull request or patch) against its task, the design contracts and the project's conventions, from six perspectives, plus a bug-fix checklist for a fix. It measures the diff with a script, re-runs the project's checks instead of trusting the implementation report, reads the changed code and its consumers, and returns findings with a location, quoted evidence, a severity and a fix, closed by a verdict: approve, approve w...Votes: 0GitHub stars: 2
- Eng Codebase MapDescribe how an existing codebase is actually built: structure, stack, entry points, the components and their measured coupling, data and control flow along the main paths, integration points, security boundaries, and observations where code and documentation disagree. Use this skill when someone says "map this codebase", "map the repo", "how is this put together", "walk me through the architecture" or "I'm new here", when onboarding to a repository, before impact analysis, refactoring or a m...Votes: 0GitHub stars: 2
- Eng DocsBring the documentation in line with a code change: find every document whose sentences the change makes false, incomplete or newly true, verify each claim you write by running it, edit the documents in the project's conventions, leave generated documents to their generators, and list what other repositories must change. Use this skill after a change is implemented and before it is reviewed or released, or when someone asks "refresh the docs", "update the docs for this" or "does the documenta...Votes: 0GitHub stars: 2
- Eng Impact AnalysisMap what a change to existing code will touch before anyone designs or writes it: the files and entry points, the project's hard rules and budgets the change comes near (with today's measured numbers), the tests that encode today's behaviour, the public surface and documents that describe it, other repositories that depend on it, and who meets the change. Use this skill before choosing between approaches for a bug fix or an improvement to existing code, or when someone asks "what does this ch...Votes: 0GitHub stars: 2
- Eng ImplementImplement one task from the backlog, one fix plan from a root-cause analysis or one finding of a code review: the smallest change that makes the task's check pass, tests first when the task specifies them, nothing outside the task's scope, and the project's conventions from its instruction file. Use this skill when a backlog task is ready, when a bug fix has a confirmed cause and a failing test, when a review finding must be fixed, or when the user asks to build, code, implement or fix someth...Votes: 0GitHub stars: 2
- Eng Integration TestsTest an implemented change through the assembled system the user runs (the built output, the real loader, the served page, the service with its real dependencies), covering the new behaviour, the states around it, the hostile conditions the decision record accepted, and the behaviours to preserve, then prove the tests catch the problem by running them against the code before the change. Use this skill after eng-implement, when a behaviour only exists when parts work together (markup inserted ...Votes: 0GitHub stars: 2
- Eng RefactorChange the shape of code without changing what it does. Use this skill whenever a request says refactor, "tidy this up", "clean up", "simplify" or "remove the duplication", including a request that also asks for a fix on the way ("refactor due.js and fix the bug"): the skill keeps the fix out of the refactor. It names the smell with the evidence that removing it changes nothing, gets the user's agreement on a target it chose itself, records the project's full check and measurements before, ma...Votes: 0GitHub stars: 2
- Eng Root CauseFind the cause of a bug with evidence: a runnable reproduction in every installed runtime the project supports, the exact line where a wrong assumption enters, a discriminating experiment that separates the cause from its look-alikes, and the conditions under which it does and does not happen. Never proposes the fix. Use this skill when a bug is reported, a test fails for a reason nobody can name, behaviour differs between browsers or environments, or before any bug fix is planned, even if th...Votes: 0GitHub stars: 2
- Eng Security ReviewTriage a project's dependency security alerts (any code host's advisories): group them by manifest and package with a script, prove for each group whether the package is shipped, installed or run anywhere, and recommend update (to the version that clears every alert) or dismiss with one of the host's reasons and an evidence comment; after one approval of the whole plan, dismiss through the code-hosting integration or hand the list to the user. Writes a dated report under docs/engineering/secu...Votes: 0GitHub stars: 2
- Eng TradeoffsCompare the ways to make one change by building each one small and measuring it: options that include at least one within the project's written rules, criteria taken from the plan's impact and preserve lists, a scratch prototype per option run in every supported runtime and in the hostile conditions users create, and an ADR that records the numbers and a recommendation, leaving the decision to the user when an option crosses a written rule. Use this skill when there is more than one reasonabl...Votes: 0GitHub stars: 2
- Eng Unit TestsWrite the tests a change must satisfy before the change exists: one test per case of the plan or the specification, in the project's own runner and conventions, run once to prove that the new behaviour fails for the right reason and the behaviour to preserve passes. Use this skill after a root cause is confirmed or a task's acceptance criteria are known, before eng-implement, even if the user only says "write the tests first", "TDD" or "add a regression test". Also use it when a bug fix has n...Votes: 0GitHub stars: 2
- Flow Fix BugFix a reported bug end to end, phase by phase, with a checkpoint after each phase. Use this skill whenever the user reports wrong behaviour and asks for it to be fixed ("fix this", "it's broken", "fix this bug", a screenshot of a wrong screen), even when the fix looks obvious: the flow proves the cause before any code changes. Also use it to continue a bug fix started earlier ("go ahead with the fix"), and when the project is not set up for the workbench yet: the flow runs core-project-init a...Votes: 0GitHub stars: 2
- Mkt Content PlanPlan the posts of the coming weeks for a person or a brand: one slot per post with the date and time (computed, with the timezone offset), the content pillar, the post language from the strategy's rotation, a topic drawn from real material (a shipped artifact, a number, a real failure, a lived story) with its source, who the post serves, and whether it needs a one-by-one approval. Writes docs/marketing/calendar.md, which mkt-social-copy drafts from and mkt-publish schedules. Use this skill wh...Votes: 0GitHub stars: 2
- Mkt EngageReply to comments on a person's own social posts inside an engagement policy they approved once: takes the comments the person pastes, classifies each, drafts a reply in the person's voice, and lets a script decide whether it goes out on its own (inside the policy's categories, languages and daily limits, never on a sensitive topic) or waits in the approval inbox. Also writes the policy itself and asks for its standing approval. Use this skill when someone asks to answer, reply to or handle c...Votes: 0GitHub stars: 2
- Mkt MessagingWrite the messaging of a product or a launch: the audience it speaks to, the promise, the proof points with their sources, the sections of a landing page with purpose, headline, body, demo and call to action, taglines and words to avoid, every claim traced to a research brief, a product artifact, a measurement or the user's words. Use this skill when someone asks for landing page copy, a value proposition, taglines, "what should the site say", a launch message or the sections of a marketing p...Votes: 0GitHub stars: 2
- Mkt PublishPublish or schedule drafted social posts, each with its first comment, under one approval of the exact texts: builds a hashed payload of the batch, shows every post as it will appear, asks once, records the approval with the payload hash, then schedules one job per post that publishes the post and its first comment at the slot's time, and later records what went out. Checks the publisher's token against the last slot and refuses what changed after the approval. Use this skill when someone say...Votes: 0GitHub stars: 2
- Mkt Social CopyWrite social media posts in a person's or a brand's voice from the slots of an approved content calendar: the exact text in the slot's language, following the voice's structure and limits, every number and claim traced to a source, and the brand checks run by script before anyone sees the draft. For a video or images platform it writes the script first (spoken lines, on-screen text, one preset per beat), then the caption. Use this skill when someone asks to write, draft or rewrite a social me...Votes: 0GitHub stars: 2
- Mkt Vote RoundTurn a closed audience vote into the week's work for one approval: the post on the winning topic (or, when nobody picked, on one of the three with the reason), in the calendar slot's language under the voice and the strategy's claim rules, and the next round's three topics for the next pillar, each with real material and a source and none already used. Scripts read the vote files, find the slot, compute the rotation and the used topics, and compute the new data files; the model writes the pos...Votes: 0GitHub stars: 2
- Ops Branch SyncBring a branch up to date with its base and resolve the conflicts: compare against the remote copy of the base (a stale local base hides what changed), merge the base into a branch that is already pushed instead of rewriting it, keep both sides of append-only records such as the workbench state file, regenerate lockfiles with the project's tool, reinstall and rerun the checks, and push only with an approval. Use this skill when someone says "the PR has conflicts", "update the branch with main...Votes: 0GitHub stars: 2
- Ops Ci PipelineSet up or change a project's CI/CD pipeline so that one build is tested and that same build is deployed: a preview per pull request, production from the main branch, the project's own checks as required checks, and a checklist of the host and repository settings only the user can apply (secrets, stopping the host's own builds, branch protection). Use this skill when someone asks "set up CI", "deploy pipeline", "protect main", "preview per PR", "GitHub Actions", or when a deploy reached produc...Votes: 0GitHub stars: 2
- Ops Pull RequestOpen a pull request for a finished branch and drive it to a mergeable state: a title in the repository's commit convention (a squash merge makes it the commit on main), a body that says what changes, why, and which checks ran with their results, the project's template when there is one, the user's approval before anything is pushed or created, and the checks followed until green. Use this skill when someone asks "open the PR", "open a pull request", "send it for review" or "push this to main"...Votes: 0GitHub stars: 2
- Ops Repo BaselineSet up a repository's security baseline: a secret scan of the working tree and the whole history before anything is published, a checks workflow with actions pinned to commits and read-only permissions, Dependabot, CODEOWNERS for the rule files, SECURITY.md and a pre-commit hook; then write the host settings (push protection, private reporting, alerts, squash only, a ruleset with signed commits and required checks) as a checklist in the order that works, with each project decision asked with ...Votes: 0GitHub stars: 2