Skip to content
TrustedSkillsbeta
Back to all skills

Tdd London Chicago

Checked
proffesor-for-testing·vlatest·testing·MIT

This skill generates test data sets focused on London and Chicago scenarios for testing applications and systems.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add proffesor-for-testing/agentic-qe --skill tdd-london-chicago -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

proffesor-for-testing

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned proffesor-for-testing/agentic-qe at 124d8c735e.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
124d8c735e
Manifest
assets/skills/tdd-london-chicago/SKILL.md
Scanned
9 files, 2,197 lines
Copies in repo
3 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill, "Tdd London Chicago," provides guidance and a framework for implementing Test-Driven Development (TDD) using two distinct approaches: the Chicago ("Classicist") and London ("Mockist") schools of thought. It helps AI agents select an appropriate testing style based on the code being developed – favoring real objects and state verification in Chicago, and mocks and interaction verification in London. The skill also suggests agent coordination for test generation, implementation, and refactoring.

When to use it

  • When starting a new feature using a test-first approach.
  • During refactoring of existing code where increased test coverage is desired.
  • To guide teams learning or reinforcing TDD practices.
  • When deciding between mocking external dependencies versus testing with real objects.

Key capabilities

  • Style Selection: Guides the AI agent in choosing between Chicago (state-based) and London (interaction-based) TDD styles based on code type.
  • TDD Cycle Guidance: Provides a structured approach to the Red-Green-Refactor cycle.
  • School Comparison: Offers a comparison of the Chicago and London approaches, highlighting their differences in collaborators, verification methods, isolation levels, refactoring ease, and design feedback.
  • Agent Coordination: Suggests using specific agent tools (qe-test-generator, qe-test-implementer, qe-test-refactorer) to automate different phases of the TDD process.

Example prompts

  • "I'm starting a new feature for calculating shipping costs. Should I use Chicago or London style?"
  • "Implement the 'Red' phase for testing this function."
  • "Refactor this code while ensuring all tests remain green."

Tips & gotchas

  • The skill emphasizes that tests should drive design, not just verify it.
  • Always ensure tests fail initially to confirm they are actually testing something.
  • Write the minimal amount of code necessary to pass each test – avoid adding unnecessary features during the "Green" phase.