Menu
SkillsMP has collected 30 skills from craigm26/founder-skills. Open a skill to review its source and details.
Copy this prompt into the AI assistant you're using.
Help me install Agent Skills from this repository: https://github.com/craigm26/founder-skills
First review the source, SKILL.md files, and companion files. List the available Skills so I can choose. Then install the complete directories for my chosen Skills into the current project and confirm the required files are present.Showing 30 of 30 collected skills.
Domain reference for the Anthropic primitives the founder-skills plugins orchestrate, as used in THIS repo (not a textbook): the Workflow({scriptPath,args}) opt-in pattern and its injected-globals runtime, batched AskUserQuestion with the (Recommended) option…
The founder-skills non-negotiables with their rationale: planner-never-writes-implementation-code routing, no-oversell / source-traceability (every claim traces to an official Anthropic URL verified that session), the sanitization hard gate for anything…
Run the recurring re-verification sweep that catches drift in founder-skills: hardcoded model IDs (Opus 4.8 / Sonnet 4.6 / Haiku 4.5 / Fable 5) and the multi-file bump procedure when Anthropic ships new models, beta API surfaces cited in v0.2.0 content (task…
Entry-point map of the founder-skills repo: layout, the four skill groups, the two-session history, quality tiers (golden four vs off-style), the open-defect ledger pointer, and a router table telling you which fs- sibling skill to load for which job. Load…
Map and maintain the founder-skills <-> PlatAtlas integration surface: the fable-org-audit endpoint map (with its known drift against the live worker), the market-validation market-map sink (nodes.json + flows.json into workflow-atlas, shape-valid but…
The structural contract of a founder-skills plugin: directory layout, plugin.json schema and version semantics (0.1.0 vs 0.2.0), marketplace.json dual registration (local ./plugins vs git-subdir cross-list), relative-path and <skill-dir> conventions, and…
Ship founder-skills safely on a live-publishing master with no CI: run the executable pre-push gate (both pytest suites, node glob test, JSON parse, sanitization grep, optional URL sweep), bump plugin versions, handle installed-cache desync, and coordinate…
The written house style for founder-skills SKILL.md and README.md files — the style the repo practiced but never wrote down, extracted from the golden four (market-validation, build-options, ecosystem-planning, fable-org-audit): frontmatter rules,…
Use when a change is architecturally significant and spans three or more repos — to thread a hard-won lesson through an entire ecosystem with a single approvable plan. Triggers on: "bake X into the whole ecosystem", "incorporate lessons across repos", "design…
Use when you need to verify that a customer organization on your platform is healthy and getting full value — a live integration audit that probes real API signals across eight dimensions, not a code review. Triggers on: "audit this org", "is <org> healthy",…
Use when designing a long-running agent loop, evaluation harness, or multi-session memory system with Fable 5 — covers self-correction loops, verifier sub-agents, and the memory progression pattern.
Use when designing and implementing a new software feature from scratch — triggers the Fable-plan → implement → review pipeline.
Use when declaring or checking the token budget / model tier for this session. Triggers on: "set effort", "how much budget do we have", "low on tokens", "use opus", "use sonnet", "constrained this week", or any explicit model-tier selection. Can also be…
Generate an implementation-ready Product Requirements Document for a feature: self-clarify the open questions (no user interview), then write a structured PRD — goals, one-session tasks with verifiable acceptance criteria, numbered functional requirements,…
Convert a PRD markdown file (typically `/tasks/prd-<feature>.md` from the `prd` skill) into `prd.json` — an ordered, dependency-sorted execution plan where every acceptance criterion is a boolean check an agent can pass or fail without a human. Use when the…
Decide WHAT to build after a market is validated: generate divergent build options, score them with an independent judge panel into a weighted decision matrix, adversarially stress-test the top, recommend one (with kill criteria), render a Tufte decision…
Validate whether there is a real market for a product idea, end to end: scope questions → a multi-angle web-research workflow with mandatory live-URL verification → a cited evidence pack → a Tufte HTML deck + PDF + PPTX → a build/integrate brief and an…
How changes to founder-skills are classified, gated, and reviewed: the operator-approved spec -> checkbox plan -> commits-matching-plan-verbatim pipeline, plus the five standing rules (direct-push-to-master with a mandatory local pre-push gate, no GitHub…
The founder-skills defect chronicle: every known failure in this repo as symptom -> root cause -> evidence -> status, so no maintainer re-fights a settled battle or re-discovers a known trap. Use when a test fails, a command from a README doesn't work, an…
The decision-gated executable campaign that proved and hardened the flagship founder chain (market-validation → build-options → prd → tasks). Phases 0-3 executed 2026-07-02 (template rescue, proving runs, prd/tasks rewrite, site truth-up) — the skill remains…
The research agenda for founder-skills: four open problems where this repo could advance the state of the art, with why current skill catalogs fail, what asset this repo already holds, the first three concrete steps IN THIS REPO, and a falsifiable milestone…
Edit the founder-skills public surfaces — the Pages site (docs/index.html), the per-plugin READMEs, and the sibling catalog site — without breaking the single-file dark-editorial design system, the fixed README template, benefit-led copy rules, the mandatory…
Recreate the founder-skills working environment from scratch and run or extend its three test suites: the venv procedure (the host Python is PEP-668 externally managed, so the README's test commands fail verbatim), the Node glob-form-only rule for the JS…
End-to-end workflow for adding a new skill/plugin to founder-skills: scripts/add-skill.sh anatomy step-by-step, its verified hazards (manifest-schema-only validation, the rm -rf symlink swap of ~/.claude/skills/<name>, the maybe-absent ~/claude-code-plugins…
Run a recurring re-verification sweep that catches drift in a published Claude Code skill marketplace: hardcoded model IDs and the multi-file bump procedure when Anthropic ships new models, beta API surfaces cited in skill text, cited doc-URL liveness,…
Ship a Claude Code skill marketplace safely when your default branch is live-publishing: run a local pre-push gate (test suites, manifest JSON parse, sanitization grep, gitignore-swallow check, optional live-URL sweep), bump plugin versions with content, and…
A written house style for Claude Code skill-marketplace SKILL.md and README.md files — frontmatter rules, trigger-rich descriptions, Phase/Step body skeletons, recurring honesty and Tests sections, a six-section plugin README template, and a conformance…
Use when you need a deep, honest audit of a repository with a prioritized improvement plan — before a refactor, before onboarding a new contributor, or before committing to a codebase.
Ideate and critique data visualizations using Edward Tufte's principles from "The Visual Display of Quantitative Information." Use this skill when: (1) Designing new data visualizations or charts (2) Critiquing or improving existing visualizations (3)…
Use at the beginning of any new session — before any work begins — to establish effort tier, session goal, and skill routing. Triggers on: "start a session", "let's begin", "new session", "kick off", "where do we start", or whenever a fresh context needs…