Add a skill-triggering eval set (prompt to expected skill and MCP tool)

未关闭
#55 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
58/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
csharp, github-actions, json
领域
devtools, testing

调研方向

Start by reading validate_plugin.py and the existing CI checks for skill descriptions and MCP tool references. Add evals/skill-triggers.json with at least two prompts per skill, then extend validation to check that referenced skills and tools exist. Done means the eval set passes in CI; document how to run it manually and record the hit rate when skill descriptions change.

由索引模型根据 Issue 内容生成。

描述

good first issue skills testing

Why it matters

Skill descriptions were rewritten as "Use when ..." triggers (closes #42), and CI now checks the wording and that every MCP tool is mentioned by a skill. Nothing checks that a real user prompt loads the right skill or leads to the right tool call.

Suggested approach

  • Add evals/skill-triggers.json with 2 or 3 prompts per skill, for example {"prompt": "my game stutters every few seconds", "skill": "performance-optimization", "tool": "lookup_api"}.
  • Have validate_plugin.py check the file's structure (every skill and tool named exists, every skill has at least one prompt).
  • Document how to run the set manually in Cursor (or with claude plugin eval / another host if one supports Cursor-style skills), and record the hit rate in the PR when descriptions change.

Done when

Every skill has at least two eval prompts and the set is validated in CI.

主要语言
C#
星标
4
派生
0
PR 合并指标
30 天内没有已合并 PR

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

TMHSDigital/Unity-Developer-Tools 的其他 Issue

查看 TMHSDigital/Unity-Developer-Tools 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。