←Leaderboard/Testing/old-coder
Last commit on August 18, 2026·Created on July 27, 2026

AmazingAng/old-coder

“A rigorous framework for designing and reviewing HTTP/JSON API surfaces”
Combined rank
#433
across all skills
In Testing
#5
category rank
Stars
745
+0.9% in last 7d
Forks
58
+3.6% in last 7d
Watchers
5
0.0% in last 7d
Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
TL;DR

This skill provides a structured approach to defining and auditing the critical components of HTTP/JSON APIs. It guides the evaluation of endpoints, request and response shapes, and essential operational constraints like idempotency and rate limiting.

It is designed for developers and agents who need to ensure that API changes, OpenAPI specifications, or route diffs do not break consumers while maintaining standards for authentication and versioning.

WHO IT'S FOR
AI agent / automation builders
implement evidence-first development loops for agents
Backend / infrastructure engineers
design and review HTTP/JSON API surfaces
Technical leads / architects
establish high-assurance coding standards for AI
QA / test automation engineers
integrate mutation testing into AI pipelines
Repository contents

2 skill files

Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.

Use this skill collection

Follow the documented setup, then try a first task.

Setup

Install old-coder with npx

Installs: The old-coder skill only.

  1. Run this terminal command to install old-coder from the repository.

    npx skills add https://github.com/amazingang/old-coder --skill old-coder
README.md ↗ · Checked Sep 29, 2026

Give it something to do.

Suggested first task

Draft an executable specification for a small change

Uses old-coder

  • Repository or worktree path
  • Description of the requested behavior
  • Known expected outputs, edge cases, and error cases
  • Any restrictions on isolation, dependencies, or tooling changes
Use the old-coder skill for [repository or worktree path]. Draft only the executable SPEC for this small change: [requested behavior]. Include concrete inputs and expected outputs, edge cases, error cases, the proposed isolation mechanism, and any setup or tooling changes. Stop before modifying implementation files so I can approve or reject the SPEC.
skills/old-coder/SKILL.md ↗ · Checked Sep 29, 2026