New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

TDD

by pietheinstrengholt in pietheinstrengholt/rssmonster

Test-driven development. An agent skill from pietheinstrengholt/rssmonster.

MITAuto-check passedTesting & QA

Install TDD

skills CLI
$ npx skills add pietheinstrengholt/rssmonster --skill tdd -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install pietheinstrengholt/rssmonster tdd --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/pietheinstrengholt/rssmonster.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/tdd .claude/skills/tdd && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tdd
GitHub stars
564
Used in
30 other repos
Token cost
~906 tokens
SKILL.md length
533 words
Files
4
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Test-driven development. An agent skill from pietheinstrengholt/rssmonster.

  • The user wants to build features
  • SKILL.md covers What a good test is, Seams: where tests go, Anti-patterns and Rules of the loop
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Fix bugs test-first

What it does

TDD is an agent skill from pietheinstrengholt/rssmonster. Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Its SKILL.md is about 910 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `agents/openai.yaml`, `mocking.md` and `tests.md`).

It sits in Testing & QA, covering Test-driven development. The repository describes itself as: Modern, self-hosted RSS reader with smart folders, powerful search, and a clean three-pane reading experience. Built with Vue and Express. The licence is MIT.

When your agent uses it

  • The user wants to build features
  • Fix bugs test-first
  • Mentions red-green-refactor
  • Wants integration tests

Example prompts

  • “red-green-refactor”
  • “/tdd”

What it can do on your machine

Read from SKILL.md and the folder at commit d2c278d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

TDD loads about 906 tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 533 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~38
When it runs · the whole SKILL.md, loaded when a task matches
~906

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from pietheinstrengholt/rssmonster at commit d2c278d, republished under its MIT licence (© pietheinstrengholt). 533 words, ~906 tokens.

Download SKILL.mdSave it as .claude/skills/tdd/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
tdd
description
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Test-Driven Development

TDD is the red → green loop. This skill is the reference that makes that loop produce tests worth keeping: what a good test is, where tests go, the anti-patterns, and the rules of the loop. Every section applies on every cycle: consult them before and during the loop, not after.

When exploring the codebase, read GLOSSARY.md (if it exists) so test names and interface vocabulary match the project's domain language, and respect ADRs in the area you're touching.

What a good test is

Tests verify behavior through public interfaces, not implementation details. Code can change entirely; tests shouldn't. A good test reads like a specification: "user can checkout with valid cart" tells you exactly what capability exists, and it survives refactors because it doesn't care about internal structure.

See tests.md for examples and mocking.md for mocking guidelines.

Seams: where tests go

A seam is the public boundary you test at: the interface where you observe behavior without reaching inside. Tests live at seams, never against internals.

Test only at pre-agreed seams. Before writing any test, write down the seams under test and confirm them with the user. No test is written at an unconfirmed seam. You can't test everything, so agreeing the seams up front is how testing effort lands on the critical paths and complex logic instead of every edge case.

Ask: "What's the public interface, and which seams should we test?" Give each proposed seam a one-line note on what it catches and what it misses.

When the shape of that interface is itself in question (how deep the module is, where the seam belongs, what the interface should expose), call the Skill tool with "codebase-design" for the vocabulary. It is the shared source of the module, interface, depth, seam, adapter, leverage and locality terms, and it is a reference to consult, not a session to run.

Show full SKILL.md (222 more words)Show less

Anti-patterns

  • Implementation-coupled: mocks internal collaborators, tests private methods, or verifies through a side channel (querying the database instead of using the interface). The tell: the test breaks when you refactor but behavior hasn't changed.
  • Tautological: the assertion recomputes the expected value the way the code does (expect(add(a, b)).toBe(a + b), a snapshot derived by hand the same way, a constant asserted equal to itself), so it passes by construction and can never disagree with the code. Expected values must come from an independent source of truth: a known-good literal, a worked example, the spec.
  • Horizontal slicing: writing all tests first, then all implementation. Bulk tests verify imagined behavior: you test the shape of things rather than user-facing behavior, the tests go insensitive to real changes, and you commit to test structure before understanding the implementation. Work in vertical slices instead: one test → one implementation → repeat, each test a tracer bullet that responds to what the last cycle taught you.

Rules of the loop

  • Red before green. Write the failing test first, then only enough code to pass it. Don't anticipate future tests or add speculative features.
  • One slice at a time. One seam, one test, one minimal implementation per cycle.
  • Refactoring is not part of the loop. It belongs to the review stage (see the code-review skill), not the red → green implementation cycle.

© pietheinstrengholt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files in .agents/skills/tdd of pietheinstrengholt/rssmonster.

  • SKILL.md
  • agents/openai.yaml
  • mocking.md
  • tests.md

Open the folder on GitHubat commit d2c278d

Used in 31 other repositories

We found 36 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 30 other GitHub owners. This page covers the copy in pietheinstrengholt/rssmonster, which our catalogue first saw on October 8, 2026.

Compare with similar skills

TDD next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

TDD compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
TDD this skillpietheinstrengholt/rssmonster56430 repos~906Automated safety check: PassMIT
TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph11211 repos~2.4kAutomated safety check: PassNone
TDDsanity-io/sanity6.4k20 repos~1kAutomated safety check: PassMIT
Test Driven Developmentfarm-fe/farm5.6k51 repos~2.5kAutomated safety check: PassMIT
Tapd Story PipelineTencentBlueKing/bk-bcs841—~2.6kAutomated safety check: PassCustom licence
Absolute Initmaddhruv/absolute2181 repos~3kAutomated safety check: PassMIT

Similar skills

  • TDD Workflow

    hellangleZ/burn-in-cceverywhere-ralph

    A skill your agent uses when writing new features, fixing bugs, or refactoring code.

    112 GitHub starsUsed in 11 repos~2.4k tokens
    Testing & QAAuto-check passed

  • TDD

    sanity-io/sanity

    Official

    Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.

    6.4k GitHub starsUsed in 20 repos~1k tokens
    Testing & QAAuto-check passed

  • Test Driven Development

    farm-fe/farm

    A skill your agent uses when implementing any feature or bugfix, before writing implementation code

    5.6k GitHub starsUsed in 51 repos~2.5k tokens
    Testing & QAAuto-check passed

  • Tapd Story Pipeline

    TencentBlueKing/bk-bcs

    单需求实现流水线——把一个 TAPD 需求从零推进到代码提交。自动串联技术澄清、 开发计划、任务拆分、TDD 实现、架构/安全校验、代码提交六个阶段。

    841 GitHub stars~2.6k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Absolute Init

    maddhruv/absolute

    One-time setup for absolute: interview how you want it to behave (output style, autonomy, TDD strictness, spec dir, families) + detect the stack once, then write .absolute.config.json (project…

    218 GitHub starsUsed in 1 repo~3k tokens
    Testing & QAAuto-check passed

  • Auto GitHub Contributor

    nexu-io/auto-github-contributor

    Interactively pick a quick-win contribution in any GitHub repo — either a labeled issue ("good first issue", "help wanted", docs) or a repo-scan candidate (typo, missing tests, i18n gap, actionable…

    137 GitHub stars~2.5k tokensUpdated 5 mo ago
    Testing & QAAuto-check: notes

More from pietheinstrengholt/rssmonster

  • Codebase Design

    pietheinstrengholt/rssmonster

    Shared vocabulary for designing deep modules. An agent skill from pietheinstrengholt/rssmonster.

    564 GitHub starsUsed in 36 repos~1.5k tokens
    Auto-check passed

  • Grilling

    pietheinstrengholt/rssmonster

    Grill the user relentlessly about a plan, decision, or idea.

    564 GitHub starsUsed in 31 repos~510 tokens
    Auto-check passed

  • Improve Codebase Architecture

    pietheinstrengholt/rssmonster

    Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

    564 GitHub starsUsed in 33 repos~1.5k tokens
    Auto-check passed

  • Close The Loop

    pietheinstrengholt/rssmonster

    A skill your agent uses when a feature has already gone through multiple implementation and review cycles and the work is starting to loop.

    564 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

  • Rssmonster Browser

    pietheinstrengholt/rssmonster

    Use Codex browser capabilities to inspect and validate the RSSMonster UI in a real browser.

    564 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed

  • Final Review

    pietheinstrengholt/rssmonster

    Perform a rigorous final review of an implementation before considering it ready to merge or ship.

    564 GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about TDD

What does TDD do?

Test-driven development. An agent skill from pietheinstrengholt/rssmonster. TDD is an agent skill from pietheinstrengholt/rssmonster. Test-driven development.

When should I use TDD?

TDD fits situations like: the user wants to build features; fix bugs test-first; mentions red-green-refactor; wants integration tests.

How do I install TDD in Claude Code?

Run `npx skills add pietheinstrengholt/rssmonster --skill tdd -a claude-code`. Or copy the skill folder (.agents/skills/tdd in pietheinstrengholt/rssmonster) into .claude/skills/tdd in your project. Claude Code loads it when a task matches its description.

How do I install TDD in Codex?

Run `npx skills add pietheinstrengholt/rssmonster --skill tdd -a codex`. Or copy the skill folder (.agents/skills/tdd in pietheinstrengholt/rssmonster) into .agents/skills/tdd in your project. Codex loads it when a task matches its description.

Can I use TDD in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pietheinstrengholt/rssmonster --skill tdd -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tdd, .gemini/skills/tdd, .github/skills/tdd and .opencode/skills/tdd in your project.

What does TDD need to run?

SKILL.md names no scripts, command-line tools or credentials: TDD is instructions for the agent only.

Does TDD access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is TDD safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does TDD use?

TDD is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does TDD use?

About 906 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to TDD?

Skills that share tags, products or a category with TDD: TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars), TDD (sanity-io/sanity, 6.4k stars), Test Driven Development (farm-fe/farm, 5.6k stars) and Tapd Story Pipeline (TencentBlueKing/bk-bcs, 841 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains TDD?

pietheinstrengholt (a GitHub user) maintains it in pietheinstrengholt/rssmonster, which has 564 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 7, 2026.

Source: pietheinstrengholt/rssmonster on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.