agentleFS
Sign inStart free
200iqlabs200iqlabs/shared-skills/skills/research-add-fields/SKILL.md

research-add-fields

Skill4 starsChanged 12 days agoApache-2.0View on GitHub

Add field definitions to existing research outline.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask user to choose:

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Research Add Fields - Supplement Research Fields

Trigger

/research-add-fields

Workflow

Step 1: Auto-locate Fields File

Find */fields.yaml file in current working directory, auto-read existing fields definitions.

Step 2: Get Supplement Source

Ask user to choose:

  • A. User direct input: User provides field names and descriptions
  • B. Web Search: Launch agent to search common fields in this domain

Step 3: Display and Confirm

  • Display suggested new fields list
  • User confirms which fields to add
  • User specifies field category and detail_level

Step 4: Save Update

Append confirmed fields to fields.yaml, save file.

Output

Updated {topic}/fields.yaml file (in-place modification, requires user confirmation)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free