yyc-cube/yyc3-ai-agent-archive/check

Claude Code and agent skill by yyc-cube/yyc3-ai-agent-archive

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Run CIAgent regression checks after changing an AI agent's code, prompts, or knowledge base in a repo that has agentci_spec.yaml, and interpret the results. Use after editing agent logic, before committing agent changes, or when the user asks whether the agent still works.

Install

npx vskill@latest install yyc-cube/yyc3-ai-agent-archive/check

SKILL.md

The same SKILL.md was published earlier as yyc-cube/yyc3-ai-agent-archive/check.

Run CIAgent checks on this repo's agent

The repo has agentci_spec.yaml (if it does not, use the onboard skill instead). Your job: run the right check for the change that was just made, read the result correctly, and never paper over a failure.

Which command

SituationCommand
Spec or wiring changed, or no API keysciagent test --mock
Agent code / prompt / retrieval changedciagent test --yes --format json
Result differs from last run, or flakiness suspectedciagent test --runs 3 --yes
Knowledge base changedciagent generate-checks --dry-run, review, then apply
The LLM judge's verdicts look wrongciagent judge-audit

Live runs (test without --mock, judge-audit, generate-checks) call model APIs on the user's keys. Mock mode is free. If the user has not already approved live runs in this session, prefer --mock or ask.

Reading results

Exit codes: 0 pass (including flaky-but-passing), 1 correctness failure (with --runs N: failed in every run), 2 infra or config error — fix the setup, not the agent.

With --format json: per-query entries carry layer results (correctness / path / cost) and the answer text; with --runs N a top-level stability block lists flipped queries with flip_source.

Flip sources route the work:

  • agent-variance — the agent's answer changed between runs → fix the agent

(prompt, retrieval, temperature).

  • judge-flake — same answer, the LLM judge changed its verdict → fix the

eval (tighten the rubric or replace with a deterministic check).

  • infra-error — a judge API call failed → retry; fix nothing.
  • mixed — ambiguous; look at the answers yourself.

Rules

  • A correctness failure means the agent lost a fact it used to state. Fix the

agent, or — only if the check itself is factually wrong — fix the check. Never weaken or delete a correct check or baseline to make a run green; report the failure to the user instead.

  • After intentionally changing agent behavior, re-record the affected golden:

delete its baseline file and rerun ciagent bootstrap --runner <runner> --queries <file> --yes for that query, or update the spec's expectations — with the user's confirmation.

  • Report results in one or two sentences: score, what failed and in which

layer, flip sources if any, and the command you ran.

Security

  • Security scanPassed, 90 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
1
Repository forks
2
7-day trend score
8

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/yyc-cube/yyc3-ai-agent-archive/check/badge)](https://verified-skill.com/skills/yyc-cube/yyc3-ai-agent-archive/check)

Something wrong with this skill or its page? Tell us.