How should tdd be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this skill.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

Crawler Summary

tdd answer-first brief

TDD Skill — Red-Green-Refactor --- skill: tdd trigger: "Use when the user invokes /tdd or asks to do TDD on a feature. Accepts a plan file path or an inline feature description. Guides the developer through Red-Green-Refactor cycles." arguments: - name: input description: "Either a path to a markdown plan file OR an inline description of the feature to implement via TDD (e.g., '/tdd plan.md' or '/tdd add JWT authentication with refresh tokens')" - Capability contract not published. No trust telemetry is available yet. 136 GitHub stars reported by the source. Last updated 4/15/2026.

Freshness

Last checked 4/15/2026

Best For

tdd is best for always, review workflows where OpenClaw compatibility matters.

Not Ideal For

Contract metadata is missing or unavailable for deterministic execution.

Evidence Sources Checked

editorial-content, GITHUB OPENCLEW, runtime-metrics, public facts pack

Card Facts Snapshot Contract Trust

Claim this agent

Agent DossierGitHubSafety: 100/100

tdd

OpenClawself-declared

Public facts

Change events

Artifacts

Freshness

Apr 15, 2026

Verifiededitorial-contentNo verified compatibility signals136 GitHub stars

Capability contract not published. No trust telemetry is available yet. 136 GitHub stars reported by the source. Last updated 4/15/2026.

136 GitHub starsTrust evidence available

Trust score

Unknown

Compatibility

OpenClaw

Freshness

Apr 15, 2026

Vendor

Mfranzon

Artifacts

Benchmarks

Last release

Unpublished

Executive Summary

Key links, install path, and a quick operational read before the deeper crawl record.

Verifiededitorial-content

Summary

Capability contract not published. No trust telemetry is available yet. 136 GitHub stars reported by the source. Last updated 4/15/2026.

View Source

Setup snapshot

git clone https://github.com/mfranzon/tdd.git

1
Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.
2
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Evidence Ledger

Everything public we have scraped or crawled about this agent, grouped by evidence type with provenance.

Verifiededitorial-content

Vendor (1)

Vendor

Mfranzon

profilemedium

Observed Apr 15, 2026Source link Provenance

Compatibility (1)

Protocol compatibility

OpenClaw

contractmedium

Observed Apr 15, 2026Source link Provenance

Adoption (1)

Adoption signal

136 GitHub stars

profilemedium

Observed Apr 15, 2026Source link Provenance

Security (1)

Handshake status

UNKNOWN

trustmedium

Observed unknownSource link Provenance

Integration (1)

Crawlable docs

6 indexed pages on the official domain

search_documentmedium

Observed Apr 15, 2026Source link Provenance

Release & Crawl Timeline

Merged public release, docs, artifact, benchmark, pricing, and trust refresh events.

Self-declaredagent-index

Docs Update

Docs refreshed: Sign in to GitHub · GitHub

search_documentmedium

Fresh crawlable documentation was indexed for the official domain.

Observed Apr 15, 2026

Artifacts Archive

Extracted files, examples, snippets, parameters, dependencies, permissions, and artifact metadata.

Self-declaredGITHUB OPENCLEW

Extracted files

Examples

Snippets

Languages

typescript

Parameters

Docs & README

Full documentation captured from public sources, including the complete README when available.

Self-declaredGITHUB OPENCLEW

Docs source

GITHUB OPENCLEW

Editorial quality

ready

Full README

skill: tdd trigger: "Use when the user invokes /tdd or asks to do TDD on a feature. Accepts a plan file path or an inline feature description. Guides the developer through Red-Green-Refactor cycles." arguments:

name: input description: "Either a path to a markdown plan file OR an inline description of the feature to implement via TDD (e.g., '/tdd plan.md' or '/tdd add JWT authentication with refresh tokens')"

TDD Skill — Red-Green-Refactor

You are guiding the developer through strict Test-Driven Development. You write code directly to the real files — the user can always undo with git. Pause only when the user's input is needed, not at every step.

Phase 1: Setup

Determine the input type:
- If the input is a file path (ends in .md, .txt, or exists on disk): read the plan file.
- If the input is an inline description (e.g., "add JWT authentication with refresh tokens"): use it directly as the feature specification. Ask clarifying questions with AskUserQuestion only if the description is too vague to decompose into increments (e.g., "build an app"). A single sentence like "add user login with email and password" is enough to start.
Detect the language and test framework from the project. If ambiguous, ask:
- Python → pytest
- TypeScript → vitest
- Go → testing (stdlib) See references/language-configs.md for runner commands and conventions.
Break the feature into small, testable increments. See references/increments.md for decomposition patterns.
Create a task list using TaskCreate — one task per increment.
Present the increment list to the user with AskUserQuestion:
- "Here are the increments I've identified. Want to reorder, add, remove, or modify any before we start?"
- Options: "Looks good, let's start" / "I want to modify the list"

Phase 2: TDD Loop

For each increment, follow Red-Green-Refactor strictly. Mark the current increment as in_progress via TaskUpdate.

RED — Write a Failing Test

Write the failing test directly to the real test file (e.g., tests/test_feature.py, following existing project conventions). Show the test in a fenced code block and briefly explain what behavior it verifies.
Run the test using the appropriate runner (see language-configs.md). Use Bash.
Confirm the test fails. If it passes unexpectedly, stop and flag this:
- "The test passed already — this means either the behavior is already implemented or the test isn't asserting the right thing. Let's investigate before moving on."
Pause with AskUserQuestion:
- "RED: test fails as expected. Review the test above — ready to move to GREEN?"
- Options: "Looks good, write the code" / "I want to change the test first"

GREEN — Write Minimal Code to Pass

Write the minimal production code directly to the real source file to make the failing test pass. Show it in a fenced code block. Write only enough to pass, nothing more.
Run all tests (not just the new one). Use Bash.
If all tests pass, move directly to REFACTOR — no pause needed.
If any test fails, show the failure output and pause:
- "A test failed unexpectedly. Here's the output. Want me to fix it, or do you want to handle it?"
- Options: "Fix it" / "I'll handle it"

REFACTOR — Improve the Code

Review the current code. If refactoring opportunities exist (duplication, naming, extraction, simplification), apply them directly and run all tests to confirm green. Show what you changed in a fenced code block.
If no refactoring is needed, say so and move on — no pause.
If refactoring causes a test failure, revert and pause to discuss.

Mark the increment as completed via TaskUpdate.
Briefly summarize: what test was added, what code was written, what was refactored (if anything).
Move directly to the next increment — go back to RED. No pause between increments.

Phase 3: Wrap-up

After all increments are complete:

Summarize what was built:
- List each increment and its test
- Note the final test count and all-passing status
Suggest any remaining work (edge cases, integration tests, documentation).

Rules

Write directly to real files. No temp files, no asking the user to move code. The user has git for undo.
Pause only when needed: after RED confirms failure (so the user can review the test), and when something goes wrong (unexpected pass, test failure at GREEN, refactoring breakage). Do NOT pause at GREEN success or REFACTOR success.
Run the full test suite at Green and Refactor steps, not just the new test.
Keep tests behavior-focused. Test what the code does, not how it does it.
Simplest case first. Start with the degenerate/edge case, build toward the general case.
One assertion per test when possible. Each test should verify one behavior.
Track progress visually using TaskCreate/TaskUpdate so the user sees where they are.
Follow existing project conventions. Match the test file locations, naming patterns, and style already in the codebase.

Contract & API

Machine endpoints, protocol fit, contract coverage, invocation examples, and guardrails for agent-to-agent use.

MissingGITHUB OPENCLEW

Endpoints

Dossier API Snapshot API Contract API Trust API

Contract coverage

Status

missing

Auth

None

Streaming

Data region

Unspecified

Protocol support

OpenClaw: self-declared

Requires: none

Forbidden: none

Guardrails

Operational confidence: low

No positive guardrails captured.

Invocation examples

curl -s "https://xpersona.co/api/v1/agents/mfranzon-tdd/snapshot"

curl -s "https://xpersona.co/api/v1/agents/mfranzon-tdd/contract"

curl -s "https://xpersona.co/api/v1/agents/mfranzon-tdd/trust"

Reliability & Benchmarks

Trust and runtime signals, benchmark suites, failure patterns, and practical risk constraints.

Missingruntime-metrics

Trust signals

Handshake

UNKNOWN

Confidence

unknown

Attempts 30d

unknown

Fallback rate

unknown

Runtime metrics

Observed P50

unknown

Observed P95

unknown

Rate limit

unknown

Estimated cost

unknown

Do not use if

Contract metadata is missing or unavailable for deterministic execution.

No benchmark suites or observed failure patterns are available.

Media & Demo

Every public screenshot, visual asset, demo link, and owner-provided destination tied to this agent.

Missingno-media

No screenshots, media assets, or demo links are available.

Related Agents

Neighboring agents from the same protocol and source ecosystem for comparison and shortlist building.

Self-declaredprotocol-neighbors

GITHUB_REPOSactivepieces

Rank

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

Traction

No public download signal

Freshness

Updated 2d ago

OPENCLAW

GITHUB_REPOScherry-studio

Rank

AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs

Traction

No public download signal

Freshness

Updated 5d ago

MCPOPENCLAW

GITHUB_REPOSAionUi

Rank

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

Traction

No public download signal

Freshness

Updated 6d ago

MCPOPENCLAW

GITHUB_REPOSCopilotKit

Rank

The Frontend for Agents & Generative UI. React + Angular

Traction

No public download signal

Freshness

Updated 23d ago

OPENCLAW

Machine Appendix

Contract JSON

{
  "contractStatus": "missing",
  "authModes": [],
  "requires": [],
  "forbidden": [],
  "supportsMcp": false,
  "supportsA2a": false,
  "supportsStreaming": false,
  "inputSchemaRef": null,
  "outputSchemaRef": null,
  "dataRegion": null,
  "contractUpdatedAt": null,
  "sourceUpdatedAt": null,
  "freshnessSeconds": null
}

Invocation Guide

{
  "preferredApi": {
    "snapshotUrl": "https://xpersona.co/api/v1/agents/mfranzon-tdd/snapshot",
    "contractUrl": "https://xpersona.co/api/v1/agents/mfranzon-tdd/contract",
    "trustUrl": "https://xpersona.co/api/v1/agents/mfranzon-tdd/trust"
  },
  "curlExamples": [
    "curl -s \"https://xpersona.co/api/v1/agents/mfranzon-tdd/snapshot\"",
    "curl -s \"https://xpersona.co/api/v1/agents/mfranzon-tdd/contract\"",
    "curl -s \"https://xpersona.co/api/v1/agents/mfranzon-tdd/trust\""
  ],
  "jsonRequestTemplate": {
    "query": "summarize this repo",
    "constraints": {
      "maxLatencyMs": 2000,
      "protocolPreference": [
        "OPENCLEW"
      ]
    }
  },
  "jsonResponseTemplate": {
    "ok": true,
    "result": {
      "summary": "...",
      "confidence": 0.9
    },
    "meta": {
      "source": "GITHUB_OPENCLEW",
      "generatedAt": "2026-04-17T00:31:42.079Z"
    }
  },
  "retryPolicy": {
    "maxAttempts": 3,
    "backoffMs": [
      500,
      1500,
      3500
    ],
    "retryableConditions": [
      "HTTP_429",
      "HTTP_503",
      "NETWORK_TIMEOUT"
    ]
  }
}

Trust JSON

{
  "status": "unavailable",
  "handshakeStatus": "UNKNOWN",
  "verificationFreshnessHours": null,
  "reputationScore": null,
  "p95LatencyMs": null,
  "successRate30d": null,
  "fallbackRate": null,
  "attempts30d": null,
  "trustUpdatedAt": null,
  "trustConfidence": "unknown",
  "sourceUpdatedAt": null,
  "freshnessSeconds": null
}

Capability Matrix

{
  "rows": [
    {
      "key": "OPENCLEW",
      "type": "protocol",
      "support": "unknown",
      "confidenceSource": "profile",
      "notes": "Listed on profile"
    },
    {
      "key": "always",
      "type": "capability",
      "support": "supported",
      "confidenceSource": "profile",
      "notes": "Declared in agent profile metadata"
    },
    {
      "key": "review",
      "type": "capability",
      "support": "supported",
      "confidenceSource": "profile",
      "notes": "Declared in agent profile metadata"
    }
  ],
  "flattenedTokens": "protocol:OPENCLEW|unknown|profile capability:always|supported|profile capability:review|supported|profile"
}

Facts JSON

[
  {
    "factKey": "docs_crawl",
    "category": "integration",
    "label": "Crawlable docs",
    "value": "6 indexed pages on the official domain",
    "href": "https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fopenclaw%2Fskills%2Ftree%2Fmain%2Fskills%2Fasleep123%2Fcaldav-calendar",
    "sourceUrl": "https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fopenclaw%2Fskills%2Ftree%2Fmain%2Fskills%2Fasleep123%2Fcaldav-calendar",
    "sourceType": "search_document",
    "confidence": "medium",
    "observedAt": "2026-04-15T05:03:46.393Z",
    "isPublic": true
  },
  {
    "factKey": "vendor",
    "category": "vendor",
    "label": "Vendor",
    "value": "Mfranzon",
    "href": "https://github.com/mfranzon/tdd",
    "sourceUrl": "https://github.com/mfranzon/tdd",
    "sourceType": "profile",
    "confidence": "medium",
    "observedAt": "2026-04-15T00:19:29.333Z",
    "isPublic": true
  },
  {
    "factKey": "protocols",
    "category": "compatibility",
    "label": "Protocol compatibility",
    "value": "OpenClaw",
    "href": "https://xpersona.co/api/v1/agents/mfranzon-tdd/contract",
    "sourceUrl": "https://xpersona.co/api/v1/agents/mfranzon-tdd/contract",
    "sourceType": "contract",
    "confidence": "medium",
    "observedAt": "2026-04-15T00:19:29.333Z",
    "isPublic": true
  },
  {
    "factKey": "traction",
    "category": "adoption",
    "label": "Adoption signal",
    "value": "136 GitHub stars",
    "href": "https://github.com/mfranzon/tdd",
    "sourceUrl": "https://github.com/mfranzon/tdd",
    "sourceType": "profile",
    "confidence": "medium",
    "observedAt": "2026-04-15T00:19:29.333Z",
    "isPublic": true
  },
  {
    "factKey": "handshake_status",
    "category": "security",
    "label": "Handshake status",
    "value": "UNKNOWN",
    "href": "https://xpersona.co/api/v1/agents/mfranzon-tdd/trust",
    "sourceUrl": "https://xpersona.co/api/v1/agents/mfranzon-tdd/trust",
    "sourceType": "trust",
    "confidence": "medium",
    "observedAt": null,
    "isPublic": true
  }
]

Change Events JSON

[
  {
    "eventType": "docs_update",
    "title": "Docs refreshed: Sign in to GitHub · GitHub",
    "description": "Fresh crawlable documentation was indexed for the official domain.",
    "href": "https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fopenclaw%2Fskills%2Ftree%2Fmain%2Fskills%2Fasleep123%2Fcaldav-calendar",
    "sourceUrl": "https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fopenclaw%2Fskills%2Ftree%2Fmain%2Fskills%2Fasleep123%2Fcaldav-calendar",
    "sourceType": "search_document",
    "confidence": "medium",
    "observedAt": "2026-04-15T05:03:46.393Z",
    "isPublic": true
  }
]

tdd answer-first brief

Executive Summary

Evidence Ledger

Release & Crawl Timeline

Artifacts Archive

Docs & README

TDD Skill — Red-Green-Refactor

Phase 1: Setup

Phase 2: TDD Loop

RED — Write a Failing Test

GREEN — Write Minimal Code to Pass

REFACTOR — Improve the Code

NEXT

Phase 3: Wrap-up

Rules

Contract & API

Reliability & Benchmarks

Media & Demo

Related Agents