Run any Skill in Manus with one click

ppds-core

Stars2

Forks0

UpdatedJune 17, 2026 at 20:56

Install, authenticate, and safely operate the Power Platform Developer Suite (PPDS) CLI and MCP server against Microsoft Dataverse — auth profiles, environment selection, the environment-safety model, and error interpretation. Use when the user wants to connect to Dataverse with PPDS, set up `ppds` or `ppds-mcp-server`, manage auth profiles or environments, decide between the PPDS CLI and MCP surfaces, or interpret a PPDS error or exit code. Load this skill first before any other ppds-* skill.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

joshsmithxrm

joshsmithxrm/ppds-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

9 files

SKILL.md

readonly

More from this repository

same repository

release

joshsmithxrm/ppds-skills

Cut a PPDS Skills package release — get the recapture, decide the version bump, clean up prose, update CHANGELOG, tag + GitHub Release. Use when PPDS ships a new stable CLI/MCP that the skills package must track, or to publish any skills-package version bump.

2026-06-172

ppds-data

joshsmithxrm/ppds-skills

Bulk Dataverse data operations with PPDS — schema-driven export/import (CMT-compatible), direct environment-to-environment copy, CSV load, bulk update/delete, truncate, user mapping, and dependency analysis. Use when the user wants to move records between environments, seed reference data, export data to a ZIP, load a CSV into a table, bulk-delete records, or migrate data with lookup and owner remapping. Read ppds-core first for auth and safety rules.

2026-06-172

ppds-metadata

joshsmithxrm/ppds-skills

Browse and author Dataverse schema with PPDS — list entities/tables, inspect attributes/columns and relationships, create or update tables, columns, relationships, alternate keys, and global choices/option sets, compare schemas across environments, and adjust views and forms. Use when the user wants to know what columns or relationships an entity has, create or modify a table or column, manage option sets or keys, diff schema between environments, or edit a view or form definition. Read ppds-core first for auth and safety rules.

2026-06-172

ppds-plugins

joshsmithxrm/ppds-skills

Register, deploy, and debug Dataverse plugins declaratively with PPDS — attribute-driven registration ([PluginStep]/[PluginImage]/[CustomApi]), the extract → diff → deploy loop, assembly management, Custom APIs, service endpoints, and plugin trace log debugging (list/get/timeline). Use when the user wants to register or deploy a plugin assembly, sync plugin steps from code, diagnose a plugin error or performance problem, read plugin trace logs, or manage Custom APIs. Read ppds-core first for auth and safety rules.

2026-06-172

ppds-query

joshsmithxrm/ppds-skills

Query and modify Microsoft Dataverse data with PPDS — SQL (transpiled to FetchXML) with joins, CTEs, aggregates and window functions, raw FetchXML, guarded DML, execution plans, TDS endpoint routing, and query history. Use when the user wants to read, filter, join, aggregate, count, or analyze Dataverse records, run INSERT/UPDATE/DELETE statements, inspect a query plan, convert SQL to FetchXML, or recall a previous query. Read ppds-core first for auth and safety rules.

2026-06-172

ppds-solutions-alm

joshsmithxrm/ppds-skills

Dataverse solution ALM with PPDS — export/import solutions, watch import jobs, inspect components, manage environment variables and connection references, and generate/sync/validate deployment settings files for target environments. Use when the user wants to export or import a solution, move customizations between environments, check why a solution import failed, fix orphaned connection references, set environment variables, or prepare deployment settings for a pipeline. Read ppds-core first for auth and safety rules.

2026-06-172

name	ppds-core
description	Install, authenticate, and safely operate the Power Platform Developer Suite (PPDS) CLI and MCP server against Microsoft Dataverse — auth profiles, environment selection, the environment-safety model, and error interpretation. Use when the user wants to connect to Dataverse with PPDS, set up `ppds` or `ppds-mcp-server`, manage auth profiles or environments, decide between the PPDS CLI and MCP surfaces, or interpret a PPDS error or exit code. Load this skill first before any other ppds-* skill.
license	MIT
metadata	{"ppds_cli_version_tested":"1.2.0","ppds_mcp_version_tested":"1.0.0"}

PPDS Core — connect, select, stay safe

PPDS (Power Platform Developer Suite) is a single .NET global tool giving you a typed CLI, an MCP server, a TUI, and NuGet libraries over Microsoft Dataverse. One install, no Python, no PAC CLI dependency. Docs: https://joshsmithxrm.github.io/ppds-docs/

dotnet tool install -g PPDS.Cli   # CLI: `ppds`   (update: dotnet tool update -g PPDS.Cli)
dotnet tool install -g PPDS.Mcp   # MCP server: `ppds-mcp-server`

Verify: ppds --version. These skills target the 1.2.0 surface (flag tables generated from 1.2.0 stable). If the installed major/minor differs, prefer live --help.

Surface routing (applies to every ppds-* skill)

The CLI is the primary surface for terminal agents. Use the MCP server instead when either holds:

The host has no shell (an MCP-only client), or
You want protocol-level session safety the shell cannot give you — --read-only (all DML rejected for the session) and --allowed-env (environment switching locked to an allowlist). Setup: references/mcp-server.md.

Where an MCP tool mirrors a CLI command this package names it, e.g. ppds env list ↔ ppds_env_list. The released server (1.0.0) exposes 41 tools — the authoritative list is references/mcp-tools.md. The CLI surface is wider; anything without an MCP tool routes to the CLI.

Authentication profiles

Profiles are stored per-machine and shared by CLI, MCP server, and TUI. All methods and exact flags: references/cli-auth.md.

ppds auth create --name dev                    # interactive browser (default)
ppds auth create --name dev --deviceCode      # headless / SSH / containers
ppds auth create --name ci --applicationId <app-id> --clientSecret <secret> --tenant <tenant-id>

Also supported: certificate file/store (--certificateDiskPath / --certificateThumbprint), --managedIdentity, and workload identity federation (--githubFederated, --azureDevOpsFederated).

Manage: ppds auth list, ppds auth select --index <n> (or --name <n>), ppds auth who, ppds auth update, ppds auth delete, ppds auth clear.

Environment selection

A profile has one selected environment; commands accept per-call overrides. Exact flags: references/cli-env.md.

ppds env list --filter contoso          # discover (name/URL/ID, partial ok)
ppds env select --environment <url-or-name>
ppds env who                            # identity + selected environment

Per-call override on most commands: --environment <url> (alias -env) and --profile <name> (-p). ppds org ... is an alias for ppds env ....

The safety model — hard rules

These rules are not style; agents must follow them.

Know your target before any mutation. Run ppds env who (CLI) or ppds_auth_who (MCP) and state the environment to the user before the first write of a session. Environments have a configured EnvironmentConfig.Type: Production, Sandbox, Development, Test, Trial, or Unknown. Production gets blocked-by-default DML that requires confirmation with a preview; treat Unknown with the same suspicion.
Multi-environment confirmation. When a session has touched more than one environment, or a command carries an explicit --environment override, restate the exact target (URL, not nickname) and get the user's confirmation before executing any mutation. Cross-environment DML defaults to read-only (cross_env_dml_policy: ReadOnly); a Production target always prompts even when the policy is Allow.
Preview before you execute. Most PPDS mutation surfaces have a --dry-run preview: use it, show the user the result, then execute. ppds query sql --dry-run (DML plan), ppds plugins deploy --dry-run, ppds plugintraces delete --dry-run, and friends. Only add --confirm / --force after a human has seen the preview. Where no --dry-run exists — notably ppds data import, ppds data copy, ppds solutions import — import into a sandbox first and lean on the rule 1–2 confirmation gates; for data moves, ppds data analyze --schema <schema.xml> previews dependencies.
MCP sessions get pinned. Launch ppds-mcp-server with --read-only for analysis sessions, and --allowed-env <url> (repeatable) when switching must be possible. No --allowed-env flags means ppds_env_select is disabled — that is a feature, not a bug.
Never bypass a refusal. Exit code 9 (Forbidden), exit code 11 (ConfirmationRequired), Query.DmlBlocked, Safety.ShakedownActive — these are answers, not obstacles. Surface them to the user.

Reading PPDS output

stdout is data, stderr is status. Pipe-safe by design. Parse stdout; show stderr to humans.
Machine-readable: add -f json (--output-format Json); CSV is -f csv.
Quiet/verbose: -q warnings+errors only; -v debug; --debug trace.
Non-zero exits carry a structured JSON error envelope on stderr with an error.code like Connection.Throttled. Exit codes 0–11 and per-code agent actions: references/error-codes.md.

Common mistakes (do not invent these)

Wrong	Correct
`ppds env select <name>` (positional)	`ppds env select --environment <name>` — the flag is required
`ppds auth select 1`	`ppds auth select --index 1`
`ppds auth login` / `ppds login`	`ppds auth create` (first time) or `ppds auth select` (existing)
`ppds env switch`	`ppds env select --environment <name>`
`--format json` / `--json`	`-f json` / `--output-format Json`
`pac auth create` patterns (e.g. `--url`)	PPDS is not PAC CLI — check references/cli-auth.md

Where to go next

Need	Skill
SQL / FetchXML queries, DML, explain, history	ppds-query
Plugin registration, deployment, trace debugging	ppds-plugins
Solutions, import jobs, env vars, connection refs	ppds-solutions-alm
Tables, columns, relationships, keys, choices, views, forms	ppds-metadata
Bulk data export/import/copy/load/delete	ppds-data
Web resources pull/push/publish	ppds-webresources
Users, roles, diagnostics	references/cli-users.md, references/cli-roles.md, references/cli-logs.md
Model-driven apps, data sources/providers, flows	no dedicated skill yet — `ppds model-driven-app`, `ppds data-sources`, `ppds data-providers`, `ppds flows`, or `ppds api request`
Anything else (raw Web API escape hatch)	`ppds api request` — prefer a typed command when one exists