agentleFS
FiredMosquito831FiredMosquito831/my-writing-companion/skills/intent-modeling/SKILL.md

intent-modeling

Skill2 starsChanged 24 days agoApache-2.0View on GitHub

Use before acting on human instructions: separate what they said from what they meant.

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

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Read for the outcome the human wants, not only the words they used.

    line 8
  2. Distinctive:

    When intent and output diverge, scan other artifacts for the same pattern.

    line 20

≈ “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

Intent Modeling

Read for the outcome the human wants, not only the words they used. Use conversation context and prior turns to infer underlying goal. When the goal is ambiguous, ask.

Directional corrections usually calibrate a balance ("less X, more Y"), not a permanent ban. Encode the target balance in what you do next.

Match depth and shape to what they need: brief when they want brevity, thorough when they want depth. A vague request may be a rough draft of the real need. Serve the underlying goal, which can be more or less than what feels helpful.

When intent and output diverge, scan other artifacts for the same pattern. One misread often repeats.

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.