edit-triggers
Skill486 starsChanged 8 months agoMITView on GitHub
Modify topic triggers — trigger phrases and model description. Use when the user asks to add, remove, or change trigger phrases, or edit a topic's model description.
In this repository30 other files it gives its agents.
- add-actionSkill
- add-adaptive-cardSkill
- add-generative-answersSkill
- add-global-variableSkill
- add-knowledgeSkill
- add-nodeSkill
- add-other-agentsSkill
- analyze-evalsSkill
- chat-directlineSkill
- chat-sdkSkill
- chat-with-agentSkill
- clone-agentSkill
- create-eval-setSkill
- create-evalSkill
- detect-modeSkill
- directline-chatSkill
- edit-actionSkill
- edit-agentSkill
- int-patternsSkill
- int-project-contextSkill
- int-referenceSkill
- list-kindsSkill
- list-topicsSkill
- lookup-schemaSkill
- manage-agentSkill
- new-topicSkill
- run-evalSkill
- run-tests-kitSkill
- test-authSkill
- validateSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
NEVER hardcode an agent name.
- Very specific: line 26
If $ARGUMENTS specifies a topic name, match it.
- Distinctive: line 49
Write a clear, specific sentence describing what the topic does and when it should be used
- Distinctive: line 52
Keep it concise but complete — the orchestrator reads this to decide routing
- Distinctive: line 53
Avoid vague descriptions like "This topic handles requests" — be specific about *which* requests
- Distinctive: line 71
Update it: when the topic's purpose or scope changes
- Very specific: line 83
Remove phrases: Delete entries from triggerQueries
- Distinctive: line 89
Use 5-10 phrases per topic for good recognition
- Distinctive: line 93
Keep phrases short and natural (how users actually type/speak)
≈ “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.
Files
Edit Topic Triggers
Modify how a topic gets triggered: trigger phrases (triggerQueries) and model description (modelDescription).
Instructions
- Auto-discover the agent directory:
NEVER hardcode an agent name.Glob: **/agent.mcs.yml - Find the target topic:
IfGlob: <agent-dir>/topics/*.topic.mcs.yml$ARGUMENTSspecifies a topic name, match it. Otherwise, list all topics and ask which one. - Read the topic file and identify what to change.
- Check the agent's settings.mcs.yml for
GenerativeActionsEnabled. This determines which trigger mechanism matters most. - Make the requested changes using the Edit tool.
Model Description (modelDescription)
The modelDescription is a natural language description at the root of an AdaptiveDialog that tells the generative orchestrator when to route to this topic. When GenerativeActionsEnabled: true, this is the primary way the agent decides which topic to trigger — even more important than trigger phrases.
kind: AdaptiveDialog
modelDescription: This topic helps users order a pizza by collecting their preferred size, toppings, and delivery address.
beginDialog:
kind: OnRecognizedIntent
id: main
...Best Practices for Model Description
- Write a clear, specific sentence describing what the topic does and when it should be used
- Focus on the user's intent: "Use this topic when the user asks for information about our perfumes" rather than "This topic sends a message"
- Include key scenarios the topic covers: "This topic handles billing inquiries, refund requests, and payment issues"
- Keep it concise but complete — the orchestrator reads this to decide routing
- Avoid vague descriptions like "This topic handles requests" — be specific about which requests
Examples from Real Topics
# Good — specific about what the topic does and when to use it
modelDescription: Use this topic when the user asks for help or needs assistance with something. Search the SharePoint knowledge base to find relevant information.
# Good — describes the full flow
modelDescription: This topic takes the user's favorite color, generates a word by concatenating the color with four random digits, and returns the generated word. If the color is white, it also provides information about the wavelength.
# Good — describes the computation
modelDescription: This sample topic performs the sum between the two numbers in inputWhen to Add/Edit Model Description
- Always add a
modelDescriptionto topics withOnRecognizedIntentwhen the agent hasGenerativeActionsEnabled: true - Update it when the topic's purpose or scope changes
- Topics with system triggers (OnError, OnUnknownIntent, OnConversationStart) don't need a
modelDescription— they're triggered automatically
Trigger Phrases (triggerQueries)
Trigger phrases are used for intent recognition. They live inside beginDialog.intent.triggerQueries.
Only topics with OnRecognizedIntent triggers have editable trigger phrases. Other trigger types (OnConversationStart, OnUnknownIntent, etc.) are system-triggered and don't use phrases.
Operations
- Add phrases: Append new entries to
triggerQueries - Remove phrases: Delete entries from
triggerQueries - Replace phrases: Swap old entries for new ones
- Rewrite all: Replace the entire
triggerQueriesarray
Best Practices for Trigger Phrases
- Use 5-10 phrases per topic for good recognition
- Cover synonyms and variations (e.g., "help", "assist", "support", "I need help")
- Include different sentence structures (questions, statements, keywords)
- Avoid overlap — don't use the same phrases in multiple topics
- Keep phrases short and natural (how users actually type/speak)
- Mix formal and informal phrasing
Example Structure
kind: AdaptiveDialog
modelDescription: This topic helps users with greeting and introduction.
beginDialog:
kind: OnRecognizedIntent
id: main
intent:
displayName: Greeting
triggerQueries:
- Hello
- Hi
- Hey
- Good morning
- Good afternoonWhat This Skill Cannot Do
- Cannot change the trigger type (e.g., from OnRecognizedIntent to OnConversationStart) — this requires recreating the topic.
- Cannot add triggers to system topics that don't use OnRecognizedIntent.
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
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.

