agentsclimarketplace

Azure devops

Skill ranbot-ai/awesome-skills/skills/azure-devops

You have access to an environment variable, `AZURE_DEVOPS_TOKEN`, which allows you to interact withFrom its SKILL.md

Install
npx -y skills add ranbot-ai/awesome-skills --skill azure-devops

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

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 6 stars6 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.

SKILL.md

3.0 KB, 662 tokens by cl100k_base, as published. Nobody here has run it

You have access to an environment variable, AZURE_DEVOPS_TOKEN, which allows you to interact with the Azure DevOps API.

<IMPORTANT> You can use `curl` with the `AZURE_DEVOPS_TOKEN` to interact with Azure DevOps's API. ALWAYS use the Azure DevOps API for operations instead of a web browser. </IMPORTANT>

If you encounter authentication issues when pushing to Azure DevOps (such as password prompts or permission errors), the old token may have expired. In such case, update the remote URL to include the current token: git remote set-url origin https://${AZURE_DEVOPS_TOKEN}@dev.azure.com/organization/project/_git/repository

Here are some instructions for pushing, but ONLY do this if the user asks you to:

  • NEVER push directly to the main or master branch
  • Git config (username and email) is pre-set. Do not modify.
  • You may already be on a branch starting with openhands-workspace. Create a new branch with a better name before pushing.
  • Once you've created your own branch or a pull request, continue to update it. Do NOT create a new one unless you are explicitly asked to. Update the PR title and description as necessary, but don't change the branch name.
  • Use the main branch as the base branch, unless the user requests otherwise
  • After opening or updating a pull request, send the user a short message with a link to the pull request.
  • Do NOT mark a pull request as ready to review unless the user explicitly says so
  • Do all of the above in as few steps as possible. E.g. you could push changes with one step by running the following bash commands:
git remote -v && git branch # to find the current org, repo and branch
git checkout -b create-widget && git add . && git commit -m "Create widget" && git push -u origin create-widget

Azure DevOps API Usage

When working with Azure DevOps API, you need to use Basic authentication with your Personal Access Token (PAT). The username is ignored (empty string), and the password is the PAT.

Here's how to authenticate with curl:

# Convert PAT to base64
AUTH=$(echo -n ":$AZURE_DEVOPS_TOKEN" | base64)

# Make API call
curl -H "Authorization: Basic $AUTH" -H "Content-Type: application/json" https://dev.azure.com/{organization}/{project}/_apis/git/repositories?api-version=7.1

Common API endpoints:

  • List repositories: https://dev.azure.com/{organization}/{project}/_apis/git/repositories?api-version=7.1
  • Get repository details: https://dev.azure.com/{organization}/{project}/_apis/git/repositories/{repositoryId}?api-version=7.1
  • List pull requests: https://dev.azure.com/{organization}/{project}/_apis/git/pullrequests?api-version=7.1
  • Create pull request: https://dev.azure.com/{organization}/{project}/_apis/git/repositories/{repositoryId}/pullrequests?api-version=7.1 (POST)

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,871. 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.