list-kinds
Skill486 starsChanged 8 months agoMITView on GitHub
List all available kind discriminator values from the Copilot Studio YAML schema. Use when the user asks what kinds/types are available.
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
- edit-triggersSkill
- int-patternsSkill
- int-project-contextSkill
- int-referenceSkill
- 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
3 rules. About 0 are common, 2 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Run the schema lookup script to get all kinds:
- Very specific: line 19
If $ARGUMENTS contains a filter keyword, filter the output to show only matching kinds.
- Distinctive: line 31
Important: Always use the script output as the source of truth.
≈ “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
List Available Kind Values
List all available kind discriminator values from the schema, dynamically.
Instructions
- Run the schema lookup script to get all kinds:
node ${CLAUDE_SKILL_DIR}/../../scripts/schema-lookup.bundle.js kinds - If
$ARGUMENTScontains a filter keyword, filter the output to show only matching kinds. - Categorize the results for easier reading:
- Triggers — kinds starting with "On" (e.g., OnRecognizedIntent, OnConversationStart)
- Actions — node actions (e.g., SendActivity, Question, SetVariable)
- Dialogs — dialog types (e.g., AdaptiveDialog, TaskDialog, AgentDialog)
- Cards — card templates (e.g., AdaptiveCardTemplate, HeroCardTemplate)
- Knowledge Sources — knowledge kinds (e.g., KnowledgeSourceConfiguration)
- Inputs — input kinds (e.g., AutomaticTaskInput, ManualTaskInput)
- Present the categorized list to the user.
Important: Always use the script output as the source of truth. Do NOT hardcode kind values.
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.