We split this skill into the rules it gives an agent

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

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈6

  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:

   Use when a workflow consistently revolves around a single chat message or prompt response, especially for quick one-turn interactions, …

   line 4
2. Distinctive:

   Treat the request as a one-message exchange unless the user asks for follow-up.

   line 7
3. Distinctive:

   Keep context compact and avoid introducing unnecessary multi-turn structure.

   line 8
4. Distinctive:

   Prefer direct, concise responses that solve the user’s immediate message.

   line 9
5. Distinctive:

   If the message is ambiguous, ask one clarifying question before expanding the workflow.

   line 10
6. Distinctive:

   Keep the interaction lightweight.

   line 14

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