dv-metadata Skill
Dataverse schema authoring via the Python SDK and Web API — tables, columns, relationships, forms, and views. Use when the user wants to define or evolve the data model — add a column, create a table, set up a lookup, customize a form, or build a view. Published by microsoft in Dataverse-skills.
What is dv-metadata Skill?
Dataverse schema authoring via the Python SDK and Web API — tables, columns, relationships, forms, and views. Use when the user wants to define or evolve the data model — add a column, create a table, set up a lookup, customize a form, or build a view. Published by microsoft in Dataverse-skills. 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.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Data analysis
- Data analysis use cases
Technical details
- Install or run with Copy skill directory
When to use dv-metadata Skill
- Use it for data analysis.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/Dataverse-skills
- Skill file: .github/plugins/dataverse/skills/dv-metadata/SKILL.md
What it does
Dataverse schema authoring via the Python SDK and Web API — tables, columns, relationships, forms, and views. Use when the user wants to define or evolve the data model — add a column, create a table, set up a lookup, customize a form, or build a view.
Skill instructions
Skill: Metadata — Making Changes Before the first metadata change in a session: 1. Confirm the target environment with the user — see the Multi-Environment Rule in dv-overview. 2. Confirm the solution — ask "What solution should these components go into?" If SOLUTIONNAME is in .env, confirm it. If no solution exists yet, you MUST ask the user for the solution name and publisher prefix before creating anything. The publisher prefix is permanent — it cannot be changed after components are created with it. STOP and ask the user: "What solution name and publisher prefix should I use? The prefix (e.g., contoso, lit, soc) is permanent on every table and column." Then query existing publishers and show them — the user may want to reuse one: python Publisher discovery + solution creation — use SDK (never raw Web API). See dv-solution for the full publisher discovery flow. pages = client.records.get("publisher", filter="customizationprefix ne 'none' and uniquename ne 'MicrosoftCorporation'", se
Explore related resources
Frequently asked questions
What is dv-metadata?
dv-metadata is a open-source AI agent skill with Copy skill directory. Dataverse schema authoring via the Python SDK and Web API — tables, columns, relationships, forms, and views.
Who is dv-metadata best for?
dv-metadata is best for reusing agent instructions, scripts, and references, data analysis workflows.
How do I install dv-metadata?
Install or run dv-metadata using Copy skill directory. Check dv-metadata for the latest setup command.
Is dv-metadata actively maintained?
dv-metadata may need a closer maintenance check before production use.
Auto-fetched from GitHub.
