agentleFS
Sign inStart free
anotherbenanotherben/claude-harness/skills/but-why/SKILL.md

but-why

Skill7 starsChanged 5 months agoNo licenceView on GitHub

Relentless curiosity-driven questioning skill that drills down to root causes and concrete facts. Use this skill when you need to deeply understand something before acting — debugging, planning, requirements gathering, architecture decisions, investigating unknowns, or any situation where surface-level understanding isn't enough. Triggers when the user says things like "dig into this", "I need to really understand", "get to the bottom of", "why does this happen", "drill down", or when you sense the problem is poorly understood and jumping to action would be premature. Also useful when a user's request is vague and you need to extract the real requirement hiding underneath. If in doubt about whether you understand something well enough — use this skill.

The file

Show its rules and text

We split this skill into the rules it gives an agent

23 rules. About 0 are common, 23 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈23

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “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.

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.

Check your setup, free