tjboudreaux
- 59 skills
- 0 followers
- 8 hours ago last updated
- ▌ Humanizer · tjboudreauxRemove signs of AI-generated writing from text. Use when the user says "humanize", "make this sound human", "remove AI patterns", "less AI", "sounds too AI", "clean up AI writing", "make natural", "de-AI", or when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's "Signs of AI writing" guide. Detects and fixes 24 patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
- ▌ Svg Generator · tjboudreaux bundleGenerate SVG images using the Quiver AI API. Use when the user needs to create SVGs from text descriptions (logos, icons, illustrations, calligraphy, diagrams) or convert raster images (PNG, JPG, WebP) to SVG vector format. Triggers include "generate an SVG", "create a vector image", "make an SVG logo", "convert to SVG", "vectorize this image", or any AI-powered SVG creation task.
- ▌ Tools Mermaid · tjboudreauxMermaid diagram syntax for flowcharts, sequence diagrams, ER diagrams, state machines, and other visualizations that render in GitHub/GitLab markdown.
- ▌ Meta Superpowers · tjboudreauxStartup protocol for every task—discover applicable skills, run them, announce usage, and follow required workflows (brainstorming, TodoWrite checklists, etc.).
- ▌ Tools Debugging Root Cause · tjboudreauxSystematic debugging playbook for tracing failures backward through the call chain, adding instrumentation, and fixing bugs at their origin.
- ▌ Investor Relations · tjboudreauxThis skill should be used when the user asks about "investor update", "board deck", "board meeting", "investor communication", "monthly update", "quarterly update", "investor email", "bad news investors", "pivot communication", "crisis communication investors", "investor ask", "warm intro", "VC relationship", "fundraising timeline", or discusses managing ongoing relationships with existing or prospective investors. Provides frameworks for effective investor communication and relationship management.
- ▌ Fundraising Narrative · tjboudreauxThis skill should be used when the user asks about "pitch deck", "fundraising story", "investor pitch", "VC narrative", "pitch narrative", "fundraising deck", "pitch structure", "Sequoia format", "why now slide", "market size slide", "TAM SAM SOM", "earned secret", "value hypothesis", "product-market fit", "founder-market fit", or discusses how to tell their company story to investors. Provides first-principles guidance for crafting compelling VC fundraising narratives.
- ▌ Ra1 Fix · tjboudreaux bundleReady Agent 1 gears up your repo (the Loadout) — remediate agent-readiness gaps by applying safe configuration scaffolds, drafting documentation for review, and listing GitHub settings to change. Use when the user asks to fix readiness, remediate readiness findings, raise the readiness level, apply readiness fixes, or scaffold missing config (linters, CI, issue/PR templates, dependabot, devcontainer, .env.example). Applies changes to a local branch only, verifies every write, and never pushes without confirmation.
- ▌ Ra1 Report · tjboudreaux bundleReady Agent 1 scans your repo for agent-readiness — a deterministic, cited score (Level 1–4, with Level 5 Autonomous reserved, across 9 pillars) plus advisory guidance and evidence explanations. Use when the user asks to assess agent readiness, score a repo, check whether a codebase is ready for AI agents, run Ready Agent 1, generate a readiness report, or find out a repo's readiness level. Runs a local pure-stdlib engine; the score is reproducible, T2 GitHub checks are offline by default, and the agent only adds non-gating advisory.
- ▌ Ra1 Interview · tjboudreaux bundleResolve the unanswered questions in a Ready Agent 1 readiness report by interviewing the developer, then record the answers as engine inputs and re-score. Use when a readiness report lists unanswered questions or gaps, when `ra1 gaps` returns any gap, when a criterion is `unknown` because the scan could not classify the project or reach a data source, or when the user asks to answer, pin, or configure what the readiness scan could not infer.
- ▌ Awesome Readme · tjboudreaux bundleCreate, audit, revise, and standardize project README files by inspecting repository evidence, asking only for material missing context, and applying audience-appropriate structure and technical-writing checks. Use for README.md work in public open-source or proprietary team repositories, including requests to write, rewrite, refresh, improve, review, or make a README awesome.
- ▌ Bug Hunt · tjboudreaux bundleAdversarial multi-agent bug hunting pipeline. Use when the user says "hunt for bugs", "adversarial bug review", "bug hunt pipeline", "find and verify bugs", or wants a thorough multi-phase bug analysis with verification. Runs three context-isolated agents (Hunter, Skeptic, Arbiter) to find bugs, challenge them, and deliver verified results.
- ▌ Bug Finder · tjboudreauxAggressive bug scanning with severity scoring. Use when the user says "find bugs", "scan for bugs", "bug scan", "code bug check", or wants a thorough single-pass bug analysis without adversarial verification. Searches codebase for all potential bugs and scores them by impact.
- ▌ Bug Review · tjboudreauxAdversarial bug verification using Skeptic and Arbiter agents. Use when the user says "review these bugs", "verify bug report", "challenge bugs", "skeptic review", or has an existing bug report they want adversarially verified. Takes a bug list and runs two-phase challenge-then-arbitrate verification.
- ▌ Tools P4 Basics · tjboudreauxFundamental Perforce operations including sync, edit, add, delete, submit, revert, and file state management.
- ▌ Tools P4 Resolve · tjboudreauxPerforce conflict resolution including merge strategies, 3-way merge, resolve workflows, and handling binary conflicts.
- ▌ Tools P4 Shelving · tjboudreauxPerforce shelving for code review, sharing work-in-progress, backup, and collaboration workflows.
- ▌ Tools P4 Changelist · tjboudreauxPerforce changelist management including creating, editing, moving files between changelists, and pending change workflows.
- ▌ Wiki Writing · tjboudreauxWrite and curate Hermes LLM Wiki pages: page types, required frontmatter, taxonomy tags, cross-linking, attribution, synthesis/dedup/contradiction protocol, and index/log propagation rules.
- ▌ Wiki Commands · tjboudreauxOperate Hermes LLM Wikis from the CLI or in-session: create, list, switch, search, open, lint, archive, link to kanban, and manage monitors, plugins, and skills.
- ▌ Wiki Ingestion · tjboudreauxIngest sources into a Hermes LLM Wiki: classify articles/papers/transcripts, manage the raw inbox, snapshot sources append-only, and handle oversized or unknown files.
- ▌ Wiki Media Ingestion · tjboudreaux bundleIngest media sources into a Hermes LLM Wiki: PDFs, images, audio, video, YouTube links, and social posts — derived artifacts, provenance manifests, two-tier storage, and per-modality protocols.
- ▌ Tools Gh Search · tjboudreauxUnified GitHub search across code, commits, issues, PRs, and repos using the gh CLI. Find patterns, track bugs, evaluate dependencies, and monitor changes.
- ▌ Tools Git Advanced · tjboudreauxAdvanced git operations including rebase, cherry-pick, bisect, reflog, stash, and history manipulation for complex workflows.
- ▌ Tools Github Actions · tjboudreauxGitHub Actions workflow authoring for CI/CD pipelines, job configuration, matrix builds, secrets, and common automation patterns.
- ▌ Tools Github Workflow · tjboudreauxFull GitHub workflow orchestration via CLI - branch management, commit quality, issue triage, PR lifecycle, and worktree operations on macOS and Windows.
- ▌ Tools Github Integration · tjboudreauxOrchestrates the integration of multiple Git worktrees or branches into a single ephemeral preview branch. Automated strategy for merging, conflict detection, and verification of parallel development streams. ONLY applicable for projects using Git/GitHub.
- ▌ Tools Visual Retro · tjboudreauxFacilitate retrospectives and experiment readouts using ASCII grids, timelines, and heatmaps for rapid comprehension.
- ▌ Tools Visual Workflows · tjboudreauxCommunicate multi-step workflows using consistent ASCII flowcharts and timelines that paste cleanly into PRs, issues, and chats.
- ▌ Tools Visual Ascii Arch · tjboudreauxExpress product, service, or data architectures through layered ASCII diagrams suitable for terminals, PRs, and ADRs.
- ▌ Tools Visual Cheatsheets · tjboudreauxBuild portable ASCII command panels summarizing CLI workflows (e.g., GitHub CLI, deployment scripts) for quick reference.
- ▌ Tools Visual State Machines · tjboudreauxModel user journeys, retention loops, or process states with ASCII state machines and storyboards.
- ▌ Product Launch Ops · tjboudreauxRun disciplined go-to-market experiments that compound insight, de-risk launches, and accelerate product-market fit.
- ▌ Product Growth Loops · tjboudreauxDesign compounding acquisition, engagement, and retention loops tailored to consumer product or game ecosystems.
- ▌ Product Monetization · tjboudreauxCraft adaptable, user-first revenue systems spanning subscriptions, in-app economies, marketplaces, and token models.
- ▌ Product Strategy To Ops · tjboudreauxConvert product strategy artifacts (opportunity briefs, launch playbooks, growth models) into actionable bd issues with dependencies.
- ▌ Product Behavior Signals · tjboudreauxConvert mixed-method research and live telemetry into actionable user insight loops that guide product bets.
- ▌ Product Value Proposition · tjboudreauxRapidly craft, prototype, and validate differentiated value propositions before committing engineering cycles.
- ▌ Product Opportunity Mapping · tjboudreauxSystematically scan cultural, platform, and behavioral shifts to find high-leverage consumer opportunities before committing to builds.
- ▌ Skill Marketing · tjboudreaux bundleAudits publishability, optimizes listing surfaces, distributes agent skills across supported public registries and marketplaces, and tracks adoption metrics. Use when asked to market a skill, publish to skills.sh or LobeHub, prepare Claude plugin or curated-list submissions, optimize SKILL.md metadata, or track skill installs. Also use when looking for skill ASO, marketplace submission, or skill directory discovery. For product or SaaS marketing directories, see directory-submissions; for product launch campaigns, see launch.
- ▌ Eng Tdd · tjboudreauxEnforces disciplined RED-GREEN-REFACTOR cycle—write failing test first, watch it fail, write minimal code to pass, then refactor.
- ▌ Eng Performance · tjboudreauxGuard latency, memory, battery, bandwidth, and gas/compute budgets by measuring before and after every change.
- ▌ Eng Spec Driven · tjboudreauxSpec-driven development workflow for planning before coding with Factory
- ▌ Eng User Impact · tjboudreauxAnchor every engineering decision in user value, measurable outcomes, accessibility, and cross-platform experience coherence.
- ▌ Eng Verification · tjboudreauxMandatory checklist before claiming work is complete—run the evidence-producing command, inspect output, and only then state a result.
- ▌ Eng Observability · tjboudreauxDesign every change with traceability, diagnostics, and fast incident triage in mind across mobile, web, and web3 stacks.
- ▌ Eng Quality Handoff · tjboudreauxDeliver changes with clear communication, reviewer-ready context, and follow-up accountability.
- ▌ Eng Security Safety · tjboudreauxApply proactive threat modeling, least-privilege design, and safety guardrails before delivering any code or infrastructure change.
- ▌ Eng Holistic Systems · tjboudreauxModel the end-to-end system, constraints, and failure modes before touching code; use whenever a change spans multiple layers or unclear requirements.
- ▌ Eng Iterative Delivery · tjboudreauxDecompose work into safe, observable increments with feature flags, rollbacks, and communication baked in.
- ▌ Eng Rigorous Validation · tjboudreauxEnforce reproducible testing, automated verification, and evidence-driven sign-off before merging any change.
- ▌ Eng Testing Anti Patterns · tjboudreauxUse when writing or modifying tests, adding mocks, or considering test-only hooks—prevents common mistakes like testing mocks, polluting production with test helpers, and mocking without understanding dependencies.
- ▌ Tools 1password CLI · tjboudreaux bundleComprehensive 1Password CLI (op) skill for secrets management, vault operations, environment injection, shell plugins, service accounts, and CI/CD integration. Use when working with credentials, API keys, environment variables, secure document storage, or automating secrets in development workflows.
- ▌ Thinking Red Team · tjboudreauxFor authorized security review of code, auth, or APIs you control, model the attacker, map the attack surface, and report only findings with a reproducible exploit path and verified mitigation.
- ▌ Thinking Socratic · tjboudreauxWhen a request is vague, assumption-laden, or "obvious," ask the few load-bearing questions that expose hidden requirements before building or committing.
- ▌ Thinking Cynefin · tjboudreauxWhen the right response mode is unclear, classify the cause-effect domain first; decompose disorder.
- ▌ Thinking Systems · tjboudreauxWhen behavior is emergent across components—fixes elsewhere break, loops/delays dominate—map boundary, stocks/flows, feedback, archetypes, then rank leverage.
- ▌ Thinking Ooda · tjboudreauxUse under time pressure when the situation is still changing and you must act before certainty — cycle Observe→Orient→Decide→Act on ~70% confidence, then re-observe.
- ▌ Thinking Triz · tjboudreauxWhen two design requirements seem mutually exclusive, name the contradiction, separate conflicting states, then invent a concrete no-compromise resolution.