Edit Triggers Skill
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. Published by microsoft in skills-for-copilot-studio.
Decision snapshot
Is this a fit?
Developers using skills-for-copilot-studio, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Can write or update data, Write actions, Filesystem access
Copy skill directory
2 months ago · MIT license
Confirm write permissions and scope before use. Access note: Local files.
What is Edit Triggers Skill?
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. Published by microsoft in skills-for-copilot-studio. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using skills-for-copilot-studio
Declared skill metadata
- Source file: skills/edit-triggers/SKILL.md
Allowed tools declared by source
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
- Local files
Requirements and access
Security and permissions
Review permissions before connecting any MCP server to an agent. Pay special attention to whether it can read local files, write data, call external services, or perform destructive actions.
When to use Edit Triggers Skill
- Use it for developers using skills-for-copilot-studio.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/skills-for-copilot-studio
- Skill file: skills/edit-triggers/SKILL.md
What it does
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.
Skill instructions
Edit Topic Triggers Modify how a topic gets triggered: trigger phrases (triggerQueries) and model description (modelDescription). Instructions 1. Auto-discover the agent directory: Glob: /agent.mcs.yml NEVER hardcode an agent name. 2. Find the target topic: Glob: <agent-dir/topics/.topic.mcs.yml If $ARGUMENTS specifies a topic name, match it. Otherwise, list all topics and ask which one. 3. Read the topic file and identify what to change. 4. Check the agent's settings.mcs.yml for GenerativeActionsEnabled. This determines which trigger mechanism matters most. 5. 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. yaml kind: AdaptiveDialog modelDescription: T
Verified compatibility and discovery
Frequently asked questions
What is Edit Triggers?
Edit Triggers is a open-source AI agent skill with Copy skill directory. 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.
Who is Edit Triggers best for?
Edit Triggers is best for reusing agent instructions, scripts, and references.
How do I install Edit Triggers?
Install or run Edit Triggers using Copy skill directory. Check Edit Triggers for the latest setup command.
Is Edit Triggers actively maintained?
Edit Triggers may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
