feature: measure the payoff — agent pass rate with vs without the pack, graded by the existing headless harness

Aberta
#373 1 comentário 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
25/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
blender, python

Direção de pesquisa

Start by reading the existing headless grader at tests/smoke/run_example.py and the issue’s listed Blender API examples and CI versions. Then define reproducible evaluation tasks, run them with and without the plugin across versions and trials, and publish results on the landing page and README. Done means the reported pass-rate comparison includes task count, model, and date and can be reproduced from the repo.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

feature marketing priority: high stale testing

Value

This would be the project's biggest differentiator. Nothing in the README, site or ROADMAP measures whether the pack changes agent output. The landing page claims skills cover "the mistakes AI assistants actually make", with no data. A published number turns a content pack into evidence, and answers the skeptical visitor's first question.

Why this repo is unusually well placed

It already has what most eval efforts lack:

  • deterministic headless graders (tests/smoke/run_example.py, exit-code contracts, falsifiers);
  • 4.5, 5.1 and 5.2 Blender CI;
  • a catalog of known-hard API contracts (slotted actions, temp_override, GN interface, VSE .strips, export axes).

Claude Code also ships claude plugin eval (plugin eval suites).

Suggested approach

  1. Write about 20 task prompts with graders. Examples:
    • "keyframe this object's rotation using 5.2 slotted actions"
    • "export to Unreal-ready glTF"
    • "bevel these edges with bmesh and free it"
    • "add a COLOR strip to the VSE on 5.2"
  2. Each run: the agent writes a script, it runs headless against a checker, and you record pass or fail.
  3. Run with and without the plugin, per Blender version, for a named model, N trials each.
  4. Publish a table on the landing page and README, and refresh it on the weekly cron (or manually, for cost).
  5. Use the results to prioritise skill improvements, e.g. the skill trigger-description issue.

Done when

The landing page shows "agent pass rate X% → Y% with the pack (N tasks, model, date)", and it is reproducible from the repo.

Linguagem predominante
Python
Estrelas
17
Forks
3
Merge médio
23h 48min
PRs com merge (30d)
3

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de TMHSDigital/Blender-Developer-Tools

Todas as issues de TMHSDigital/Blender-Developer-Tools

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.