Add more field definitions to an existing fields.yaml. Source new fields from user input or from a web-search subagent suggesting common fields in the domain.
59
68%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./plugins/ultra-research/skills/research-add-fields/SKILL.md/ultra-research:research-add-fields
Manual-only via disable-model-invocation: true. Run between /ultra-research:research and /ultra-research:research-deep to enrich the schema the deep-research subagents will populate.
Phase 2b of 5 (optional). Edits fields.yaml in place. When finished, Step 4 uses AskUserQuestion to route the user into the next phase (re-run this skill, /ultra-research:research-add-items, or /ultra-research:research-deep) with (Recommended) annotations based on coverage of the two YAML files.
Glob */fields.yaml in the current working directory and read it. If multiple match, ask which.
Use AskUserQuestion with two options:
⛔ Dispatch-only. If the user picks B (web search), the orchestrator MUST NOT call WebSearch, WebFetch, or mcp__exa_websearch__* directly. Instead, launch one web-search-agent subagent (background, via the harness's Agent/Task tool) with a prompt asking it to propose common fields used in this domain (e.g. for "AI coding tools", fields like context_window, benchmark_scores, pricing_tiers). The orchestrator's job is dispatch + read the subagent's structured return, nothing else.
category it belongs to (offer existing categories from fields.yaml plus "create new") and which detail_level (brief, moderate, detailed)fields.yaml under the chosen category, preserving existing entriesAfter saving, Read the updated fields.yaml and the sibling outline.yaml. Apply the thinness rubric:
| Check | Trigger for (Recommended) |
|---|---|
fields.yaml total fields | Still < 6 fields, OR only one field_categories entry, OR no field with detail_level: detailed → recommend Add more fields (run this skill again) |
outline.yaml items count | < 8 items, OR no category field used → recommend Add more items |
If neither file is thin, recommend Start deep research instead.
Use AskUserQuestion with header: "Next step" and these options (append (Recommended) to the label when the rubric flags it):
/ultra-research:research-add-items/ultra-research:research-add-fields again/ultra-research:research-deepIn the question body, briefly state why each recommendation was made. Invoke the picked skill immediately via the Skill tool.
{topic}/fields.yaml updated in place, with the appended fields echoed back to the user.
48bf6a4
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.