agentsclimarketplace

Add azuredevops

Skill LeonardSEO/power-platform-skills-codex/plugins/code-apps-preview/skills/add-azuredevops

Unofficial Codex adaptation of Microsoft Power Platform Skills with telemetry hard-disabled and automated upstream sync.

Install
npx -y skills add LeonardSEO/power-platform-skills-codex --skill add-azuredevops

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 13 days oldThe repository was created 13 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.

SKILL.md

3.7 KB, as published. Nobody here has run it

πŸ“‹ Shared Instructions: shared-instructions.md - Cross-cutting concerns.

Add Azure DevOps

Workflow

  1. Check Memory Bank β†’ 2. Add Connector β†’ 3. Apply HttpRequest Fix β†’ 4. Configure β†’ 5. Build β†’ 6. Update Memory Bank

Step 1: Check Memory Bank

Check for memory-bank.md per shared-instructions.md.

Step 2: Add Connector

First, find the connection ID (see connector-reference.md):

Run the /list-connections skill. Find the Azure DevOps connection in the output. If none exists, direct the user to create one using the environment-specific Connections URL β€” construct it from the active environment ID in context (from power.config.json or a prior step): https://make.powerapps.com/environments/<environment-id>/connections β†’ + New connection β†’ search for the connector β†’ Create.

npx power-apps add-data-source -a azuredevops -c <connection-id>

Step 3: Apply HttpRequest Fix (Required)

The generated code has a known issue: the HttpRequest method uses parameters as the parameter name, but the API expects body. Rename parameters to body in these 3 files:

Use the Edit tool to rename parameters to body in each file:

1. src/generated/services/AzureDevOpsService.ts: Find the HttpRequest method. Rename the parameter and its usage:

// BEFORE (generated):
async HttpRequest(parameters: any) {
  const params = { parameters: parameters, ... };

// AFTER (fixed):
async HttpRequest(body: any) {
  const params = { body: body, ... };

2. .power/appschemas/dataSourceInfo.ts: Find the visualstudioteamservices β†’ HttpRequest β†’ parameters section. Rename the property key:

// BEFORE (generated):
HttpRequest: {
  parameters: {
    parameters: { ... }

// AFTER (fixed):
HttpRequest: {
  parameters: {
    body: { ... }

3. .power/schemas/visualstudioteamservices/visualstudioteamservices.Schema.json: Find the /{connectionId}/httprequest β†’ post β†’ parameters array. Change the name field:

// BEFORE (generated):
{ "name": "parameters", "in": "body", ... }

// AFTER (fixed):
{ "name": "body", "in": "body", ... }

Step 4: Configure

Ask the user what Azure DevOps operations they need (query work items, create items, trigger pipelines, etc.).

HttpRequest -- make arbitrary ADO REST API calls:

await AzureDevOpsService.HttpRequest({
  Uri: "https://dev.azure.com/{org}/{project}/_apis/wit/wiql?api-version=7.2",
  Method: "POST",
  Body: JSON.stringify({
    query:
      "SELECT [System.Id], [System.Title] FROM WorkItems WHERE [System.TeamProject] = @project"
  })
});

Docs: Azure DevOps REST API

Use Grep to find specific methods in src/generated/services/AzureDevOpsService.ts (generated files can be very large -- see connector-reference.md).

Step 5: Build

npm run build

Fix TypeScript errors before proceeding. Do NOT deploy yet.

Step 6: Update Memory Bank

Update memory-bank.md with: connector added, HttpRequest fix applied, build status.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.