Power Platform ALM the Powercademy way — design the delivery process (environments, solution segmentation, publisher, the config boundary, promotion path and approvals), then run promotions with checkpoints that stop before anything irreversible. Routes execution to Microsoft's Dataverse solution skills, native pipelines and pac CLI rather than rebuilding them. A production import is always a red checkpoint.
8 on GitHubby Howdang Rashidv0.1.1MITupdated today
/
Plugin alm from marketplace powercademy-skills in Powercademy/powercademy-skills. Commands read from the repo's manifest — today.
What it installs
Skills (2)
design-alm-process
Design the delivery process for a Power Platform solution - environment strategy, solution segmentation, publisher and naming, promotion path, environment-variable and connection-reference handling, and who approves what - producing a written ALM process the team can actually follow. Trigger wheneve
promote-solution
Run a Power Platform solution promotion end to end with checkpoints - pre-flight the source and target, export the right solution as managed, move it, import, then verify with evidence - stopping before anything irreversible. Trigger whenever the user says "deploy this solution", "promote to test",
Powercademy's living conventions for Power Platform delivery — Dataverse schema judgement (statecode over custom status, solution and publisher discipline, dependency packaging), the Power Automate and PCF lessons that cost hours once (editing live flows, child-flow contracts, whether PCF is the right tool, the premium-licensing trap), applied before and alongside any build, model-driven app UX (every command button has an icon that says what it does, modal focused-task dialogs), the tool-selection ladder (purpose-built tools, then SDK / Web API / CLI, browser automation only where nothing else reaches), plus the writing-skills house standard for authoring skills that work in both runtimes. Each rule carries its reasoning; the lists grow with every corrected mistake.
Make the canvas app decisions that generation can't — is canvas even the right shape, delegation and data strategy, screen and navigation architecture, conventions — then hand a decided build plan to Microsoft's canvas authoring tooling. Checkpoints at real data volumes, because a 50-row test proves nothing. Methodology, not mechanics.
Takes a machine from nothing to fully equipped for end-to-end Power Platform development, then keeps it healthy. setup-workstation asks which workloads you'll build, installs the SDKs, CLIs, Microsoft's plugins and MCP servers with one approval, and writes an IT request for anything needing admin rights; check-setup diagnoses and repairs auth profiles, tenants, outdated tools and plugin drift. Both read one versioned toolchain manifest that a weekly upstream watch keeps current.
Security default for organizations: seated outermost, it keeps the organization's classic hooks, prompt content, settings, tool policy and pinned environment out of reach of the plugins a person installs, and adds no policy of its own; one managed option, allowManagedModsOnly, limits mods to the organization's.
Transform Claude into an Azure expert. This plugin integrates the Azure MCP server and specialized Azure skills to move beyond generic advice. It enables Claude to perform real-world tasks: listing resources, validating deployments, diagnosing infrastructure issues, and optimizing costs across 50+ Azure services.
Build, manage, and deploy Wix sites and apps. Includes CLI development skills and Wix MCP server for site management, eCommerce, CMS, dashboard extensions, and more.
Build, launch, grade, and schedule Claude Managed Agents (CMA) in your own Anthropic account — a plugin re-implementation of Anthropic's launch-your-agent reference skill (Apache-2.0; independent, not a fork). Every session starts with a goal (./my-agent/goal.json, opt-in SessionStart hook, driven by /cs-goal); loop_compiler.py compiles it into a bounded grade->iterate loop (max_iterations 1..20), a recurring cron scheduled-deployment loop, or a single-pass interview->stage->launch workflow. 6 skills: orchestrator (context: fork goal router) + interview + stage-launch + grade-iterate + run-without-you + wrap-up. 18 stdlib-only deterministic scaffolders (no network/API calls; live launches emitted as BYOK curl that never prints the key), 4 agents, 8 commands, hooks, 5 references, 4 assets. Validators enforce CMA limits. Distinct from engineering/agent-harness (generic domain loop) and write-a-skill (authors Claude Code skills, not CMAs).
DevOps, cloud, and deployment specialists - Kubernetes, Terraform, AWS, Azure, GCP, and SRE
VoltAgent/awesome-claude-code-subagents 26,513
Maintain alm?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.