Agent skill

lo2cin4bt Acceptance Review

by lo2cin4 in lo2cin4/lo2cin4bt

Runs a pass, revise or block acceptance review on lo2cin4bt work, checking a deliverable against the request, repo contracts, tests, docs and the public GitHub boundary.

Custom licenceAuto-check passedTesting & QA

Install lo2cin4bt Acceptance Review

skills CLI
$ npx skills add lo2cin4/lo2cin4bt --skill lo2cin4bt-acceptance -a claude-code

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

GitHub CLI
$ gh skill install lo2cin4/lo2cin4bt lo2cin4bt-acceptance --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/lo2cin4/lo2cin4bt.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/lo2cin4bt-acceptance .claude/skills/lo2cin4bt-acceptance && 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
lo2cin4bt-acceptance
GitHub stars
288
Token cost
~1.4k tokens
SKILL.md length
573 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
Custom licence

At a glance

Runs a pass, revise or block acceptance review on lo2cin4bt work, checking a deliverable against the request, repo contracts, tests, docs and the public GitHub boundary.

  • Works in 4 steps: Use response_language from the PM packet… → If the user writes in Chinese or asks… → Keep code identifiers, file paths,… → …
  • Before closing a code, config, skill or release change in lo2cin4bt
  • SKILL.md covers Purpose, Use When, Inputs and Workflow, plus 10 more sections
  • Calls uv

What it does

This repo-local skill is run before closing meaningful work on lo2cin4bt, a backtest engine: code, config, agent, skill, Lecture, frontend or release changes. The agent reads the user request and latest corrections, the changed files, current contracts, tests, payloads and reports, plus the runtime architecture note and any other reference files that apply to what was touched. It then applies a checklist, runs validation matched to the risk, and returns pass, revise or block.

The checklist covers following the user's wording, letting the latest correction supersede older instructions, no scope drift, required agents, skills and references existing, no unsupported strategy or config claims, no public performance overclaims, no live trading, broker or production deployment actions, and docs and skills agreeing on paths and names. Structural drift is rejected rather than excused. Replies follow the user's language, using Traditional Chinese for Chinese requests while keeping identifiers and finance abbreviations exact. The review judges deliverable quality only and is not investment advice. The excerpt is truncated.

When your agent uses it

  • Before closing a code, config, skill or release change in lo2cin4bt
  • Checking that README and public docs claims match what the repo can do
  • Confirming nothing crosses the public GitHub boundary or touches forbidden paths

Example prompts

  • “Run the acceptance review on my README changes before I merge.”
  • “Check this release branch for stale docs and unsupported strategy claims.”
  • “Review whether this change followed my latest correction and stayed in scope.”

Requirements

  • A lo2cin4bt checkout with its `skills/lo2cin4bt/references` files

Workflow steps

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

  1. Use response_language from the PM packet when present; otherwise infer it from the latest user message.
  2. If the user writes in Chinese or asks for Chinese, write Traditional Chinese for all non-specialist wording.
  3. Keep code identifiers, file paths, commands, schema keys, agent/skill names, ticker symbols, provider names, and standard finance/quant…
  4. Return response_language in the output packet. When writing repo-local reports, apply the same language policy to the report body.

What it can do on your machine

Read from SKILL.md and the folder at commit d2e0863. 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:

    • uv

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

  • Network

    No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.

    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

lo2cin4bt Acceptance Review loads about 1.4k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 573 words of instructions outside code blocks.

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

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 573 words (~1,374 tokens).

“Provide skill-owned acceptance for user intent, shared Rust architecture, artifacts, frontend contracts, safety, and evidence.”

— opening of SKILL.md by lo2cin4, Custom licence
name
lo2cin4bt-acceptance
version
2.2.1
status
active
category
auditor
use_when
Checking a lo2cin4bt deliverable against user requirements and current contracts., Reviewing architecture drift, stale docs, output boundaries, or public…

Read the full SKILL.md on GitHub

Files

Just SKILL.md in skills/lo2cin4bt-acceptance of lo2cin4/lo2cin4bt.

Open the folder on GitHubat commit d2e0863

Compare with similar skills

lo2cin4bt Acceptance Review 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.

lo2cin4bt Acceptance Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
lo2cin4bt Acceptance Review this skilllo2cin4/lo2cin4bt288—~1.4kAutomated safety check: PassCustom licence
RuView Result Verificationruvnet/RuView97k—~395Automated safety check: PassMIT
Codewhale Verification Laddercodewhale-hq/Codewhale41k—~1.4kAutomated safety check: PassMIT
Reviewwebern/cargo-readme385—~2kAutomated safety check: NotesApache-2.0
TUI Change Verification for Warpwarpdotdev/warp65k1 repos~5.5kAutomated safety check: NotesAGPL-3.0
Dev ReviewFHIR/fhir-codegen154—~5kAutomated safety check: PassMIT

Similar skills

  • Proves a RuView result is real by running a deterministic SHA-256 proof and a witness bundle, and by checking reports for untagged or unreproducible accuracy claims.

    97k GitHub stars~395 tokensUpdated today
    Testing & QAAuto-check passed
  • Codewhale Verification Ladder

    codewhale-hq/Codewhale

    Climbs a focused-to-broad set of verification rungs, from formatting checks to budget scripts CI enforces, so a Codewhale change is called done only with quoted command output behind it.

    41k GitHub stars~1.4k tokensUpdated today
    Testing & QAAuto-check passed
  • Review

    webern/cargo-readme

    Reviews a GitHub pull request for correctness, architecture, security, backward compatibility, and test coverage.

    385 GitHub stars~2k tokensUpdated 12 days ago
    Testing & QAAuto-check: notes
  • Runs Warp's terminal UI for real, drives it with keystrokes and reads the rendered screen back to confirm that a change looks and behaves as intended.

    65k GitHub starsUsed in 1 repo~5.5k tokens
    Testing & QAAuto-check: notes
  • Dev Review

    FHIR/fhir-codegen

    Performs a two-track code-quality and QA review in the roles of a staff-level Engineering Lead and QA Lead, then synthesizes both critiques into a single analysis.md.

    154 GitHub stars~5k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • cmux Testing Rules

    disler/learning-cmux-with-agents

    Testing rules for the cmux Swift codebase: Swift Testing as the default framework, a two-commit regression policy, and tests that check runtime behavior, not source text.

    115 GitHub stars~1.2k tokensUpdated 3 mo ago
    Testing & QAAuto-check passed

More from lo2cin4/lo2cin4bt

  • Guides an agent through installing, configuring and running local backtests in the lo2cin4bt repo, then explaining the results and fixing setup problems.

    288 GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check passed
  • lo2cin4bt Backtesting

    lo2cin4/lo2cin4bt

    Runs and troubleshoots local lo2cin4bt backtests: strategy runs, Parameter Matrix, WFA, rolling validation, frontend startup, payload refresh and generated artifacts.

    288 GitHub stars~1.8k tokensUpdated 2 mo ago
    Auto-check passed
  • Explains a completed lo2cin4bt backtest run's metrics, equity curve, drawdowns, and costs from canonical artifacts only, without giving trading advice.

    288 GitHub stars~3k tokensUpdated 2 mo ago
    Auto-check passed
  • Lo2cin4bt Pm

    lo2cin4/lo2cin4bt

    Repo-local PM routing skill for lo2cin4bt. An agent skill from lo2cin4/lo2cin4bt.

    288 GitHub stars~2.2k tokensUpdated 2 mo ago
    Auto-check passed
  • Repo-local strategy builder skill for lo2cin4bt. An agent skill from lo2cin4/lo2cin4bt.

    288 GitHub stars~2.2k tokensUpdated 2 mo ago
    Auto-check passed
  • Teaches the lo2cin4bt backtesting product from the repository's own docs and code, in the learner's language, ending each answer with one next step.

    288 GitHub stars~1.8k tokensUpdated 2 mo ago
    Auto-check passed

Works with

Questions about lo2cin4bt Acceptance Review

What does lo2cin4bt Acceptance Review do?

Runs a pass, revise or block acceptance review on lo2cin4bt work, checking a deliverable against the request, repo contracts, tests, docs and the public GitHub boundary. This repo-local skill is run before closing meaningful work on lo2cin4bt, a backtest engine: code, config, agent, skill, Lecture, frontend or release changes. The agent reads the user request and latest corrections, the changed files, current contracts, tests, payloads and reports, plus the runtime architecture note and any other reference files that apply to what was touched.

When should I use lo2cin4bt Acceptance Review?

lo2cin4bt Acceptance Review fits situations like: before closing a code, config, skill or release change in lo2cin4bt; checking that README and public docs claims match what the repo can do; confirming nothing crosses the public GitHub boundary or touches forbidden paths.

How do I install lo2cin4bt Acceptance Review in Claude Code?

Run `npx skills add lo2cin4/lo2cin4bt --skill lo2cin4bt-acceptance -a claude-code`. Or copy the skill folder (skills/lo2cin4bt-acceptance in lo2cin4/lo2cin4bt) into .claude/skills/lo2cin4bt-acceptance in your project. Claude Code loads it when a task matches its description.

How do I install lo2cin4bt Acceptance Review in Codex?

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

Can I use lo2cin4bt Acceptance Review 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 lo2cin4/lo2cin4bt --skill lo2cin4bt-acceptance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lo2cin4bt-acceptance, .gemini/skills/lo2cin4bt-acceptance, .github/skills/lo2cin4bt-acceptance and .opencode/skills/lo2cin4bt-acceptance in your project.

What does lo2cin4bt Acceptance Review need to run?

Going by SKILL.md and its folder, lo2cin4bt Acceptance Review needs the command-line tools its instructions call (uv). Our summary lists: A lo2cin4bt checkout with its `skills/lo2cin4bt/references` files.

Does lo2cin4bt Acceptance Review access the network?

SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is lo2cin4bt Acceptance Review 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 lo2cin4bt Acceptance Review use?

lo2cin4bt Acceptance Review has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does lo2cin4bt Acceptance Review use?

About 1.4k tokens (SKILL.md is roughly 5.5k 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 lo2cin4bt Acceptance Review?

Skills that share tags, products or a category with lo2cin4bt Acceptance Review: RuView Result Verification (ruvnet/RuView, 97k stars), Codewhale Verification Ladder (codewhale-hq/Codewhale, 41k stars), Review (webern/cargo-readme, 385 stars) and TUI Change Verification for Warp (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains lo2cin4bt Acceptance Review?

lo2cin4 (a GitHub user) maintains it in lo2cin4/lo2cin4bt, which has 288 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on August 1, 2026.

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