Agent skill

Happier Release Validation

by happier-dev in happier-dev/happier

Run target-owned manual deep release certification from an explicit Happier checkout without dispatching a release.

MITAuto-check passed

Install Happier Release Validation

skills CLI
$ npx skills add happier-dev/happier --skill happier-release-validation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install happier-dev/happier happier-release-validation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/happier-dev/happier.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/happier-release-validation .claude/skills/happier-release-validation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
happier-release-validation
GitHub stars
1.9k
Token cost
~896 tokens
SKILL.md length
417 words
Files
1
Skills in repo
28
Repo updated
First seen
Licence
MIT

At a glance

Run target-owned manual deep release certification from an explicit Happier checkout without dispatching a release.

  • Works in 5 steps: Record the release source SHA and every… → Read docs/compatibility.md, map only… → Use the non-mutating deep profile in… → …
  • SKILL.md covers Start from the target contract, Manual certification and Boundaries
  • Calls node

What it does

Happier Release Validation is an agent skill from happier-dev/happier. Run target-owned manual deep release certification from an explicit Happier checkout without dispatching a release.

Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Web, Desktop & Mobile client and orchestrator for Codex, Claude Code, OpenCode, Pi, Cursor, Grok, Antigravity, Kimi, Augment Code, Qwen, fully end-to-end encrypted. The licence is MIT.

Example prompts

  • “/happier-release-validation”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Record the release source SHA and every independently versioned component
  2. Read docs/compatibility.md, map only reachable old/new directions, and
  3. Use the non-mutating deep profile in tests-dispatch.yml for complete
  4. For every manual scenario, preserve practical evidence: source/baseline
  5. Report passed, failed, skipped, and blocked checks to the maintainer. A

What it can do on your machine

Read from SKILL.md and the folder at commit 493820f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Happier Release Validation loads about 896 tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 417 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~36
When it runs · the whole SKILL.md, loaded when a task matches
~896

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from happier-dev/happier at commit 493820f, republished under its MIT licence (© happier-dev). 417 words, ~896 tokens.

Download SKILL.mdSave it as .claude/skills/happier-release-validation/SKILL.md (or your agent's skills folder).
name
happier-release-validation
description
Run target-owned manual deep release certification from an explicit Happier checkout without dispatching a release.

Happier Release Validation

This is the repository-owned entrypoint for the public release contract's manual-only deep profile. It does not publish, promote, deploy, submit stores, or create a release operation.

Start from the target contract

From the explicit release checkout, inspect the target-owned profile and its executable suite inventory:

bash
node scripts/pipeline/run.mjs release-contract
node scripts/pipeline/run.mjs release-validate --profile deep --dry-run

deep is not part of normal release dispatch. This skill is its manual entrypoint; the registry does not pretend that semantic compatibility or human QA can be decided by a script.

For general release preparation or approval, first use the installed private maintainer authority:

bash
hmaint release bootstrap --repo <absolute checkout> --json

Read and follow the returned private skill for general release preparation or approval. This repository skill remains the target-owned deep-certification entrypoint only.

If hmaint is unavailable, stop and obtain the approved maintainer-tool installation; do not substitute a copied release workflow or arbitrary shell commands.

Manual certification

  1. Record the release source SHA and every independently versioned component changed by that source. Resolve supported stable/preview baselines to immutable tags/artifacts; a rolling tag is discovery only.
  2. Read docs/compatibility.md, map only reachable old/new directions, and perform the target-owned suite commands for affected automatic-capable surfaces. Record unrun or unavailable proof as such.
  3. Use the non-mutating deep profile in tests-dispatch.yml for complete in-repository source certification. Run credentialed live-provider scenarios separately through their explicit provider-contract entrypoint when the affected surface requires them. Native/store publication is release work, not certification, and must not be invoked from this skill. Keep editorial judgement, release-note wording, and subjective compatibility assessment human-reviewed; do not encode them as prose/style tests.
  4. For every manual scenario, preserve practical evidence: source/baseline identity, command or observed user flow, result, and recovery/failure state. Use an existing release record when one exists; do not create a parallel ledger, lifecycle state, or certification authority.
  5. Report passed, failed, skipped, and blocked checks to the maintainer. A manual certification is evidence for human approval, never the approval itself.
Show full SKILL.md (104 more words)Show less

Boundaries

  • Use the canonical scripts/pipeline/release-validation/validate-release.mjs path through scripts/pipeline/run.mjs; do not copy its suite selection into this skill.
  • Manual deep certification validates the release source and the existing loaded stack. It does not create or install local release archives; publication automation owns the outputs it publishes.
  • Run only discriminating compatibility vectors or live flows for affected, reachable directions. Do not manufacture a component or platform matrix.
  • Keep certification evidence in the existing release record or final handoff. Do not create per-run plan, tracking, ledger, lane, or workspace machinery.
  • Do not write release notes, tags, GitHub releases, credentials, deploy branches, or store submissions from this skill.

© happier-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/happier-release-validation of happier-dev/happier.

Open the folder on GitHubat commit 493820f

Compare with similar skills

Happier Release Validation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Happier Release Validation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Happier Release Validation this skillhappier-dev/happier1.9k—~896Automated safety check: PassMIT
Auditing Tls Certificate Transparency Logsmukul975/Anthropic-Cybersecurity-Skills34k—~4kAutomated safety check: PassApache-2.0
MCPA Certification Tutorrohitg00/ai-engineering-from-scratch65k—~3.5kAutomated safety check: PassMIT
Claude Certification Tutorrohitg00/ai-engineering-from-scratch65k—~3kAutomated safety check: PassMIT
Accredible Certificates AutomationComposioHQ/awesome-claude-skills77k3 repos~790Automated safety check: PassNone
Analyzing Certificate Transparency For Phishingmukul975/Anthropic-Cybersecurity-Skills34k—~3.5kAutomated safety check: PassApache-2.0

Similar skills

  • Auditing Tls Certificate Transparency Logs

    mukul975/Anthropic-Cybersecurity-Skills

    Monitors Certificate Transparency (CT) logs to detect unauthorized certificate issuance, discover subdomains via CT data, and alert on suspicious certificate activity for owned domains.

    34k GitHub stars~4k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • MCPA Certification Tutor

    rohitg00/ai-engineering-from-scratch

    Turns a GitHub course repository into an interactive tutor for the MCP Associate certification, making the learner explain and defend each step.

    65k GitHub stars~3.5k tokensUpdated yesterday
    EducationAuto-check passed
  • Claude Certification Tutor

    rohitg00/ai-engineering-from-scratch

    Guides a learner through one of four independent Claude certification tracks with onboarding, lessons, practice labs, mock exams and remediation.

    65k GitHub stars~3k tokensUpdated yesterday
    EducationAuto-check passed
  • Accredible Certificates Automation

    ComposioHQ/awesome-claude-skills

    Automate Accredible Certificates tasks via Rube MCP (Composio).

    77k GitHub starsUsed in 3 repos~790 tokens
    Productivity & AutomationAuto-check passed
  • Analyzing Certificate Transparency For Phishing

    mukul975/Anthropic-Cybersecurity-Skills

    Monitor Certificate Transparency logs using crt.sh and Certstream to detect phishing domains, lookalike certificates, and unauthorized certificate issuance targeting your organization.

    34k GitHub stars~3.5k tokensUpdated 1 mo ago
    SecurityAuto-check passed
  • Performing Ssl Certificate Lifecycle Management

    mukul975/Anthropic-Cybersecurity-Skills

    Automates the full SSL/TLS certificate lifecycle, including generating Certificate Signing Requests, issuing, deploying, monitoring, renewing, and revoking X.509 certificates, using Python and ACME…

    34k GitHub stars~867 tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

More from happier-dev/happier

All 28 skills in this repo
  • Happier Review

    happier-dev/happier

    Conduct evidence-backed Happier code, plan-completeness, session, worktree, feature, commit, branch, PR, codebase, and release-readiness reviews with affected-corridor analysis, high-confidence…

    1.9k GitHub stars~4.5k tokensUpdated today
    Auto-check passed
  • Happier CI Stabilize

    happier-dev/happier

    Stabilize failing, flaky, slow, or repeatedly rerun Happier CI and nightlies by collecting all reachable failures from one exact attempt, correcting canonical causes in one batch, simplifying…

    1.9k GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Happier Commit Worktree

    happier-dev/happier

    Reconnoiter, classify, validate, group, and commit a large or continuously changing Happier worktree as coherent, human-understandable commits while preserving concurrent work and excluding…

    1.9k GitHub stars~3.9k tokensUpdated today
    Auto-check passed
  • Happier Release

    happier-dev/happier

    Resolve Happier's private release authority and run an exact-SHA release or nightly through cheap admission, verified CI evidence, resumable immutable candidates, and terminal publication proof.

    1.9k GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Happier Diagnose

    happier-dev/happier

    Diagnose and explain a Happier runtime, session, daemon, provider (Claude/Codex/OpenCode), authentication, or connectivity incident from logs, structured diagnostics, runtime state, and source…

    1.9k GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Happier Implement

    happier-dev/happier

    Implement, change, build, fix, refactor, migrate, or apply accepted review findings in the Happier repositories with canonical-owner discovery, scope-preserving solution economy, TDD, efficient…

    1.9k GitHub stars~4.2k tokensUpdated today
    Auto-check passed

Questions about Happier Release Validation

What does Happier Release Validation do?

Run target-owned manual deep release certification from an explicit Happier checkout without dispatching a release. Happier Release Validation is an agent skill from happier-dev/happier. Run target-owned manual deep release certification from an explicit Happier checkout without dispatching a release.

How do I install Happier Release Validation in Claude Code?

Run `npx skills add happier-dev/happier --skill happier-release-validation -a claude-code`. Or copy the skill folder (.agents/skills/happier-release-validation in happier-dev/happier) into .claude/skills/happier-release-validation in your project. Claude Code loads it when a task matches its description.

How do I install Happier Release Validation in Codex?

Run `npx skills add happier-dev/happier --skill happier-release-validation -a codex`. Or copy the skill folder (.agents/skills/happier-release-validation in happier-dev/happier) into .agents/skills/happier-release-validation in your project. Codex loads it when a task matches its description.

Can I use Happier Release Validation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add happier-dev/happier --skill happier-release-validation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/happier-release-validation, .gemini/skills/happier-release-validation, .github/skills/happier-release-validation and .opencode/skills/happier-release-validation in your project.

What does Happier Release Validation need to run?

Going by SKILL.md and its folder, Happier Release Validation needs the command-line tools its instructions call (node).

Does Happier Release Validation access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Happier Release Validation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Happier Release Validation use?

Happier Release Validation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Happier Release Validation use?

About 896 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Happier Release Validation?

Skills that share tags, products or a category with Happier Release Validation: Auditing Tls Certificate Transparency Logs (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), MCPA Certification Tutor (rohitg00/ai-engineering-from-scratch, 65k stars), Claude Certification Tutor (rohitg00/ai-engineering-from-scratch, 65k stars) and Accredible Certificates Automation (ComposioHQ/awesome-claude-skills, 77k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Happier Release Validation?

happier-dev (a GitHub organization) maintains it in happier-dev/happier, which has 1,876 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 7, 2026.

Source: happier-dev/happier on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.