Loading…
Verify delivery outcomes on the real product, capture inspected evidence, and deliver an acceptance report with the lh CLI: published to LobeHub when signed in, or rendered as a local offline report when not. Use for product acceptance, manual verification, evidence collection, or publishing an existing report, with or without a supplied plan. Reuse valid evidence; run new verification through bounded, lower-cost agent contexts when available.
acceptance is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 58/100. # Acceptance (Builder Self-Evidence) You are the **builder** for a delivery. A separate review step judges it against a **plan** — checks you author, or a verif. This catalog entry is the indexed repository lobehub/acceptance. The command is the string recorded from the source. It is not proof of a one-click install in every client. An MCP server exposes callable tools to a client. An agent skill is an instruction package. This entry is an agent skill record. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. Review the repository push date and repository status before adding acceptance to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.
npx skills add lobehub/acceptance --skill acceptanceThe command is the string recorded from the source. It is not proof of a one-click install in every client.
Review the upstream source before running this command.
Scan coverage: Install metadata and the indexed document body.
Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.
# Acceptance (Builder Self-Evidence) You are the **builder** for a delivery. A separate review step judges it against a **plan** — checks you author, or a verify plan handed to thi