agentleFS
Archive228Archive228/claude-fable-rea-bla/.claude/skills/release-harden/SKILL.md

release-harden

Skill18 starsChanged 2 days agoMITView on GitHub

Harden your own build with BLA right before you ship it, so the protected output goes out instead of the raw build. Use at release time only.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are 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.

  • 2

    Very specific

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

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

    Run npx bla-agents harden .

    line 10
  2. Very specific:

    Run --dry-run first on a real project - it writes nothing and reports what it would do.

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Harden a release with BLA

Harden only your own builds.

  1. Run npx bla-agents harden . from the project root. It finds the build artifacts (dist/, build/, .asar, .wasm, native binaries), hardens them, checks the hardened output still behaves the same, and writes .bla-hardened/ plus bla-harden-summary.json.
  2. Run --dry-run first on a real project - it writes nothing and reports what it would do.
  3. Ship the .bla-hardened/ folder, not the raw build.

Two things worth knowing: bla lint refuses to finish while a one-line license or secret check is still in the source, so rewrite those first; and no client-side scheme is absolute - keep real secrets on the server. qybaihe/bla, MIT - npx bla-agents setup --client claude-code.

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.