feat(framework): support portable multi-host skill evaluation
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 22/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- javascript
- Área
- testing-qa, tooling
Línea de trabajo
Start with scripts/skill-eval.mjs, where the Claude-only launch, skill staging under .claude/skills/, judge handling and PASS/FAIL reporting live, and with scripts/skill-eval/cases.json and its README for the fixtures. Read the archived multi-host branch only for reference. Done means the default Claude invocation still passes its existing cases, --host=codex works with a deterministic fake-CLI test, and invalid --jobs or --repeat values fail before any host runs. The scope spans several subsystems and needs a design decision first, so it is not a good first task.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Problem
The existing scripts/skill-eval.mjs runner is Claude Code-specific: it launches claude -p and stages skills under .claude/skills/. This prevents contributors using Codex CLI from running the same applicable behavioral evaluation cases through their native host.
The current harness also has no explicit INCOMPLETE outcome: skipped judge checks are marked ok: true, and case results are reported as PASS or FAIL. It parses --jobs and --repeat as numbers without validating positive integer values before launching hosts.
Earlier work in #992 added Codex execution, JSON assertions, filesystem snapshots, and explicit incomplete-result reporting; those unrelated changes were removed to keep #992 focused on Kilo-native generation following maintainer feedback. The historical implementation is preserved under a tag on the contributor's fork.
The need is distinct from #1079 (what constitutes trustworthy skill-behavior evidence) and #1236 (portable contributor AI resources). Without coordinated boundaries, these efforts could duplicate host launchers and skill-discovery test harnesses.
Scope
- Extend the existing runner with
--host=claude|codex, retaining Claude as the default and keeping existing cases compatible. - Introduce a minimal host-adapter boundary for native CLI execution, skill staging and discovery in isolated temporary projects, exit/error capture, and host/version/model metadata where available.
- Keep portable cases and deterministic assertions independent of host adapters; explicitly report unsupported host features rather than silently skipping them.
- Add a deterministic
jsonValidassertion and optional before/after project-tree snapshots to detect unexpected mutations, without following symlinks outside the isolated workspace. - Define
PASS,FAIL, andINCOMPLETEwith distinct failure diagnostics. Skipped optional LLM-judge checks must not make otherwise complete deterministic evaluations incomplete; skipped required evidence must never produce a full PASS. - Validate positive integer
--jobsand--repeatarguments before any host invocation. - Reuse
skill-evalas the preferred behavioral execution infrastructure for the contributor skills investigated in #1236 where applicable; avoid a second independent host-execution or skill-discovery harness unless a concrete limitation is demonstrated. The runner must remain usable withoutaidd-contributor. - Maintain the boundary with #1079: this issue builds execution/assertion facilities, not an evidence protocol, grading methodology, or proof of complete skill compliance.
- Start from current
next; inspect the archived historical implementation (commitccd32e3bd9075cce43be6bea4a7bb1c60a14e6dd) and port selectively, rather than cherry-picking unrelated changes from #992. - Keep model-backed evaluations local and opt-in. Deterministic runner tests may run in CI without authentication or paid-model calls. Design for later Kilo/OpenCode adapters without implementing them in this issue.
Acceptance criteria
- Existing Claude evaluation cases and default invocation remain compatible, with regression tests.
- One applicable evaluation fixture is exercised with both Claude Code and Codex CLI; report the observed host versions, commands, and outcomes (or explicitly document any unavailable runtime validation).
- A deterministic fake-CLI test exercises each host adapter without model credentials and verifies skill staging, invocation, output, and error capture.
- Unsupported host selection and capabilities produce explicit diagnostics; portable assertions do not contain host-specific launch logic.
- Valid JSON passes
jsonValid; malformed JSON fails it in isolated tests. - Snapshot tests detect creation, modification, and deletion while refusing to traverse external symlink targets.
- Tested result classification distinguishes failed assertions, failed host invocation, unavailable required evidence, and omitted optional judge checks.
- Invalid, zero, negative, and non-integer
--jobsor--repeatvalues fail before host execution. - A documented contributor-skill example demonstrates how the #1236 POC could reuse the runner, without requiring an
aidd-contributorinstallation or introducing a parallel harness. - Documentation explicitly separates this runner from the evidence methodology proposed in #1079.
- No mandatory authenticated model-backed CI execution is introduced.
Prior art in this repo
scripts/skill-eval.mjs, lines 37–52: Claude-only runner.scripts/skill-eval.mjs, lines 59–112: existing assertions and optional judge.scripts/skill-eval.mjs, lines 114–164: temporary project setup, skill staging, and result reporting.scripts/skill-eval/README.md, lines 3–30: current usage and prerequisites.scripts/skill-eval/cases.json: existing fixtures.- Historical multi-host implementation, archived tag, original commit
ccd32e3bd9075cce43be6bea4a7bb1c60a14e6dd. - #992 (original contribution); #1079 (behavioral evidence); #1236 (contributor portability); #929 and #978 (broader tool portability/compatibility).
Out of scope
- Implementing an
aidd-contributorplugin or distributing contributor instructions/rules/hooks (investigated by #1236). - Defining or replacing the behavioral evidence protocol and grading semantics of #1079.
- Implementing Kilo Code, OpenCode, or every supported host in the initial change.
- Benchmarking or ranking language models.
- Introducing mandatory authenticated AI-backed CI gates.
- Rewriting production skills, altering canonical plugin formats, or reintroducing unrelated Project Memory, hook, or generation changes from #992.
- Lenguaje dominante
- TypeScript
- Estrellas
- 481
- Forks
- 45
- Merge medio
- 1 d 13 h
- PR fusionados (30 d)
- 91
Preparar el entorno
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de ai-driven-dev/framework
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
ai-driven-dev/framework#1311 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100
ai-driven-dev/framework#1244 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
ai-driven-dev/framework#1197 ·
Los mantenedores suelen responder en 1 día
-
refactor(aidd-context): apply the new skill template to learnPosiblemente ocupada @blafourcade la tomó hace 3 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
ai-driven-dev/framework#1186 · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
ai-driven-dev/framework#1163 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de ai-driven-dev/framework
Issues similares
-
bug impact:low Team: SecuritySolution Team:Defend Workflows v9.6.0
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
elastic/kibana#306401 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
agentes-chat/agentes-chat#927 ·
Los mantenedores suelen responder en 1 día
-
[Bug]: Webapp workspace fails to render in Safari — "Can't find variable: requestIdleCallback"Abiertocomp/desktop P2 type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
NousResearch/hermes-agent#157702 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
e2e-failure ready-to-code
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
redhat-developer/rhdh-plugin-export-overlays#4794 · 1 comentario ·
Los mantenedores suelen responder en 1 día