agentleFS
noamgariani11noamgariani11/claude-skills/skills/helm/SKILL.md

helm

Skill0 starsChanged 3 months agoNo licenceView on GitHub

Perpetual CEO/product-engineering operator for ONE project. A founder-minded planner that never stops: researches the product, its users, and the business; keeps a living map of the codebase and architecture; grooms a ranked backlog into senior-engineer-grade task briefs; hands each chunk to the right specialist skills/agents (orchestrate, the *-dude engineers, the *-code-review gates, qa, security-dude, push-dude); reviews what returns; and compounds — improving its own playbook and the other skills as it learns. Runs autonomously under skip-permissions on Sonnet, cycle after cycle, until stopped; state lives on disk (.helm/) so it survives context resets; decides itself and never blocks the user (no AskUserQuestion). Use when: "helm", "run the project", "build forever", "keep building", "autopilot the repo", "ceo mode", "run the loop", "/helm". Args: an optional free-text brief of what the user wants (steers the Vision), plus --resume, --status, --once, and --quality (swap the build-features flywheel for a relentless audit-fix-reverify hardening loop: make the app battle-tested and immaculate, run unattended under /loop).

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 0 are common, 6 are distinctive, and 8 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 8

    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 measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “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.