agentleFS
zedarvateszedarvates/botte-secrete/skills/decision_ladder/SKILL.md

decision-ladder

Skill2 starsChanged 3 months agoMITView on GitHub

Ponytail-inspired YAGNI enforcement — climb the decision ladder before writing any code. stdlib → regex → existing module → new code.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Add to workflow-check as a pre-code hook.

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Decision Ladder

Ponytail-inspired YAGNI enforcement for botte-secrete. Before writing ANY code, climb this ladder. Each rung that passes saves the cost of every rung above it.

The Ladder

  1. stdlib — Is this already in Python's standard library? (os, pathlib, json, re, ast, sqlite3, http, etc.)
  2. regex_oneliner — Can a regex, string method, or one-liner do it? No function needed.
  3. existing_module — Does an existing botte skill already handle this? Reuse > rebuild.
  4. new_code — No simpler alternative exists. Write the minimal implementation.

Usage

from skills.decision_ladder.ladder import climb, audit_task_list

# Single task
result = climb("extract function names from a Python file")
# → LadderResult(rung="stdlib", solution="ast module (ast.parse/walk)", saved_lines=15)

# Audit a task list
report = audit_task_list([
    "parse JSON config",
    "design auth middleware",
    "count word frequency in text",
    "strip HTML tags from string",
    "implement custom OR-Tools solver",
])
# → avoidable_pct: 80%, lines_saved: 85

Integration

Add to workflow-check as a pre-code hook. See hook.py.

Metrics

Tracks:

  • % of tasks that could be avoided (stdlib, regex, existing module)
  • Estimated lines saved per task
  • Confidence score per suggestion

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.