tamdogood
UserA repository for skills that are essential to my daily work
Categories
Indexed Skills (20)
lead-research
Discovery-scale research harness. A cheap scout maps the topic, the Lead designs topic-specific parallel researcher assignments from the scout's map (drawing on a source-class tactics library — academic, repos, production patterns, web, experts), then verifies claims against sources and writes a decision-oriented report. Use when brainstorming a project or feature, choosing a technology, or asked to "research X", "state of the art", "deep research". For narrow slice-level fact checks inside the build loop, /lead handles those inline.
lead
Use when the user asks to run or continue the autonomous build factory: turn a goal into a spec-approved GitHub issue plan, freeze acceptance checks, dispatch parallel builder jobs, review completed jobs, answer blockers, and finish a run with a single PR. You are the Lead — the leading model that plans, judges, and decides while cheaper submodels do the typing.
build-scenario-tests
Inspect an unfamiliar repository, turn a focused Markdown behavior scenario into a deterministic test in the repository's native test stack, run it, and preserve traceability between intent and code. Use when asked to add scenario tests, compile acceptance criteria or Given/When/Then Markdown into executable tests, reproduce a user-visible regression, or convert a narrow workflow specification into stable web, API, CLI, desktop, or mobile interaction coverage. Do not use for broad exploratory journeys or agent-judged smoke tests.
run-smoke-tests
Inspect an unfamiliar repository, interpret a broad Markdown user journey at runtime, operate the real product through its supported web, API, CLI, desktop, or mobile surface, and produce an auditable pass, fail, or blocked judgment with screenshots, logs, recordings, and a step timeline when available. Use when asked to run smoke tests, validate an end-to-end user journey, dogfood a product, test a release candidate, or execute a non-deterministic workflow that may include authentication or human checkpoints. Do not use as a substitute for deterministic unit, integration, or scenario tests.
create-marketing-kit
Create truthful, human-centered marketing campaigns for an app or product, including positioning, channel copy, original artwork, editable layouts, README banners, and selective website integration. Use when asked to make launch materials, promotional artwork, social assets, campaign kits, ads, or marketing content from an existing product; to adapt a visual reference without copying it; or to add approved campaign art to product surfaces. Do not invent claims, fake UI, publish, deploy, or replace product proof without explicit evidence and authorization.
create-skill
Create or update a complete repository skill from a user's idea, including the workflow instructions, references, scripts or assets, agent metadata, skill-card artwork, cinematic banner artwork, README links, discovery metadata, and validation. Use when the user asks to create a new skill, add a skill to this collection, turn a workflow into a reusable skill, or make a skill's documentation and artwork consistent with the repository.
map-the-landscape
Map the big picture around a topic or software repository by identifying its boundaries, layers, actors, components, relationships, flows, history, fault lines, and open questions, then explain how the pieces fit together and where to look next. Use when a user asks to understand a whole field, domain, technology, ecosystem, industry, codebase, architecture, unfamiliar repo, or phrases such as "give me the big picture", "map the landscape", "how does this all fit together?", "help me get oriented", or "what am I missing?"
make-playbook
Indie maker playbook for bootstrapped apps inspired by Pieter Levels' MAKE: The Indie Maker Blueprint. Use when a user is starting or sizing an app idea, choosing what to build next, building a minimal product, preparing a launch, diagnosing stalled growth, deciding pricing or monetization, automating operations, maintaining a per-app MAKE.md tracker, or evaluating whether to sell a product.
async-learning-teacher
Transform saved links, papers, articles, posts, videos, and reference collections into approachable AI teaching artifacts for later study. Use when a user wants to queue learning material, create a readable explanation from a source, teach a paper or post step by step, or run an interactive tutor that validates understanding over multiple sessions.
orwell-writing
Use when an agent is asked to draft, rewrite, edit, review, polish, copyedit, simplify, humanize, or create written prose, including creative writing, essays, posts, scripts, speeches, emails, documentation, product copy, and other style-sensitive text. Apply George Orwell's six rules and ASD-STE100 Simplified Technical English as a plain-English discipline while preserving the user's intended meaning, audience, tone, and explicit constraints.
session-profiler
Profile and debug Hermes sessions from their JSONL transcripts. Find a session and its subagents, build a queryable event table, summarize the work as a hierarchical table of contents, break down wall time, inference, tools, tokens, and estimated cost per agent, identify errors and improvement opportunities, and export a shareable Perfetto trace. Use when a user wants to inspect what a Hermes session did, debug agent or subagent activity, understand session cost or latency, create a session timeline, generate a trace, or learn how to improve the next agent run.
validate-market
Run an honest market-fit and viability audit of any project or idea and produce a decision doc, not code. Use when someone asks "is this viable as a business", "audit the market fit", "make the case and compare to competitors", "should I apply to YC or bootstrap", or wants to validate a project, product, or market before investing more time. Gathers verifiable traction data first, researches the competitive field, gets an independent cold read, writes a doc with pre-committed pass/middle/kill criteria and a concrete week-1 assignment, then hardens it with an adversarial review loop.
write-blog
Write and ship a blog post for your project that reads like a human wrote it and pulls SEO traffic to your site. Use when a contributor wants to draft, edit, or publish a blog post, add a post to the site, write about the project for search/traction, or make an existing draft sound less like AI. Enforces the house voice (no em dashes), picks a non-cannibalizing angle, uses ASD-STE100 Simplified Technical English for technical prose, wires the post into your site, and runs the humanizer pass before shipping.
code-standards
Apply a disciplined engineering workflow to any code change. Use whenever implementing a feature, fixing a bug, or refactoring — before writing code, not after. Walks orient → baseline → smallest change → test → verify → self-review, and enforces language-agnostic hard gates (don't mass-reformat, keep the linter and type-checker clean, keep the build and tests green, make interface changes additive, protect security invariants).
validate-market
Run an honest market-fit and viability audit of any project or idea and produce a decision doc, not code. Use when someone asks "is this viable as a business", "audit the market fit", "make the case and compare to competitors", "should I apply to YC or bootstrap", or wants to validate a project, product, or market before investing more time. Gathers verifiable traction data first, researches the competitive field, gets an independent cold read, writes a doc with pre-committed pass/middle/kill criteria and a concrete week-1 assignment, then hardens it with an adversarial review loop.
write-blog
Write and ship a blog post for the Parler Protocol website (web/) that reads like a human wrote it and pulls SEO traffic to the repo and hub. Use when a contributor wants to draft, edit, or publish a blog post, add a post to the site, write about Parler Protocol for search/traction, or make an existing draft sound less like AI. Enforces the house voice (no em dashes), picks a non-cannibalizing angle, wires the post into Next.js, and runs the humanizer pass before shipping.
parler-review
Review a diff, branch, or PR in the Parler Protocol repo against the project review contract (docs/code-review-guidelines.md). Use when asked to review changes, audit a branch, check a PR, or self-review before landing. Produces verified, severity-ranked findings — no style noise, no unverified criticals.
architect-research
Discovery-scale research harness: a cheap scout researcher maps the topic, the orchestrator designs topic-specific parallel researcher assignments from the scout report (drawing on a source-class tactics library — academic, repos, production patterns, web, experts), then verifies claims against sources and synthesizes a decision-oriented report. Use when brainstorming a project or feature, choosing a technology, or asked to "research X", "what's the state of the art", "deep research". For narrow slice-level fact checks inside the build loop, /architect handles those inline.
architect
Use when the user asks to architect, run or continue the autonomous software factory, turn a goal into a spec-approved GitHub issue plan, dispatch builder jobs, judge completed jobs, diagnose blockers, or finish a factory run.
code-standards
Apply Parler Protocol's engineering contract to a code change. Use whenever implementing a feature, fixing a bug, or refactoring in this repo — before writing code, not after. Walks orient → baseline → smallest change → test → verify → self-review, and enforces the hard gates (never cargo fmt, clippy -D warnings, make ci green, additive wire changes only, security invariants).
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.