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

Ouverte
#373 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Active
Stack technique
blender, python

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Python
Étoiles
17
Forks
3
Merge moyen
23 h 48 min
PR mergées (30 j)
3

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de TMHSDigital/Blender-Developer-Tools

Toutes les issues de TMHSDigital/Blender-Developer-Tools

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.