菜单
Pull and summarize user feedback (👍/👎 on clues) for the Hebrew Codenames co-pilot from the private HF dataset shmulc/codenames-feedback. Use when asked to "check feedback", "any new feedback", "grab feedback", review clue thumbs-up/down, or see what users complained about.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Apply vertical slice architecture to organize code by feature instead of by technical layer. Use when adding a new feature, endpoint, command, query, or use case. Use when deciding whether to create new files or edit existing ones. Use when implementing CQRS, mediator pattern, plugin architecture, event-driven patterns, or auto-discovery registration. Use when the user asks about additive architecture, feature folders, or minimizing edit surface. Also trigger when you notice yourself about to add a new method to an existing controller or service — that is the moment this skill is most needed.
Use when the user wants a hands-free loop where grabbing UI elements in the browser with React Grab feeds tasks to the agent automatically, with no copy-paste or manual handoff. Triggers: "watch react grab", "monitor my grabs", "auto-process react grab", "watch my clipboard for grabs". Not for a one-off paste of a single grab; this is the continuous, always-on loop.
Deploy the Hebrew Codenames co-pilot to its HF Space (shmulc/hebrew-codenames-copilot) by uploading changed files from hf_space/, and report the build stage. Use when asked to "deploy", "push to HF", "ship the Space", or "release the co-pilot".
QA the Hebrew Codenames engine — run the clue-legality regression, the clue-quality benchmark against the feedback set, and optionally verify the live HF Space. Use before committing engine changes, after tuning scoring or legality, or when asked to "run QA", "run the tests", "run the benchmark", or "check the engine still works".
Use this skill for playing, teaching, or moderating the Hebrew version of Codenames (שם-קוד). Triggers include requests to explain rules, generate clues, validate guesses, simulate games, or clarify legal/illegal actions. Especially for generating high-quality Spymaster clues that avoid opponent and assassin words.
| name | codenames-feedback |
| description | Pull and summarize user feedback (👍/👎 on clues) for the Hebrew Codenames co-pilot from the private HF dataset shmulc/codenames-feedback. Use when asked to "check feedback", "any new feedback", "grab feedback", review clue thumbs-up/down, or see what users complained about. |
Live 👍/👎 feedback on clues is written by the deployed Space
(shmulc/hebrew-codenames-copilot) and mirrored to the private HF dataset
shmulc/codenames-feedback (file data/feedback.jsonl). The truth is on HF —
the local feedback/feedback.jsonl is only a seed/mirror, so always query HF.
python .agents/skills/codenames-feedback/scripts/pull_feedback.py
Requires an HF token with read access to the dataset (the stored ~/.cache/huggingface/token
is used automatically; no HF_TOKEN env needed). Uses force_download so you always get the
latest, not a cached snapshot.
ignore/test) are flagged so you can discount them.ts, verdict, clue, count, intended, mode, risk, comment, board {words, roles}, revealed, focus, why.
The full board + focus + revealed cards are stored, so any row is reproducible — feed it back
through the engine (see the codenames-qa skill's bench_feedback.py) to see what the current
engine would do on that exact board.
Downvotes cluster into: illegal clues (shared root — now caught), over-reach (a stretched
extra word), and taste (e.g. a more general clue preferred). See the project memory
(spymaster-scoring-design, codenames-feedback-loop) for the roadmap these drove.