agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/skills-for-copilot-studio/skills/lookup-schema/SKILL.md

lookup-schema

Skill486 starsChanged 8 months agoMITView on GitHub

Look up Copilot Studio YAML schema definitions. Use when the user asks about schema structure, element properties, or how to use a specific YAML kind.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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
  1. Distinctive:

    Look up and explain a Copilot Studio YAML schema definition.

    line 11
  2. Distinctive:

    Run the schema lookup script to find the definition:

    line 15
  3. Distinctive:

    If the definition is not found, search for similar definitions:

    line 20
  4. Very specific:

    If the definition contains $ref references that need resolution, use:

    line 25

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

Lookup Schema Definition

Look up and explain a Copilot Studio YAML schema definition.

Instructions

  1. Run the schema lookup script to find the definition:
    node ${CLAUDE_SKILL_DIR}/../../scripts/schema-lookup.bundle.js lookup $ARGUMENTS
  2. If the definition is not found, search for similar definitions:
    node ${CLAUDE_SKILL_DIR}/../../scripts/schema-lookup.bundle.js search $ARGUMENTS
  3. If the definition contains $ref references that need resolution, use:
    node ${CLAUDE_SKILL_DIR}/../../scripts/schema-lookup.bundle.js resolve $ARGUMENTS
  4. Present the schema definition in a readable format, explaining:
    • What the element does (from the description)
    • Required properties
    • Optional properties and their types
    • Any related definitions that might be useful

Example

User: /lookup-schema SendActivity

Response should include the full schema definition and explain how to use it in YAML.

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.

Check your setup, free