New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

A2ui Remediate Problem

by a2ui-project in a2ui-project/a2ui

Remediates a specific recommendation from an A2UI compliance report issue, or resolves any general GitHub issue, by inspecting context, implementing minimal targeted fixes, verifying tests, creating…

Apache-2.0Auto-check passedDevelopment

Install A2ui Remediate Problem

skills CLI
$ npx skills add a2ui-project/a2ui --skill a2ui-remediate-problem -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install a2ui-project/a2ui a2ui-remediate-problem --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/a2ui-project/a2ui.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/a2ui-remediate-problem .claude/skills/a2ui-remediate-problem && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
a2ui-remediate-problem
GitHub stars
17k
Token cost
~1.5k tokens
SKILL.md length
678 words
Files
4 (incl. scripts, references)
Skills in repo
20
Repo updated
First seen
Licence
Apache-2.0

At a glance

Remediates a specific recommendation from an A2UI compliance report issue, or resolves any general GitHub issue, by inspecting context, implementing minimal targeted fixes, verifying tests, creating…

  • Works in 5 steps: Identify & Read Issue Context → Formulate & Apply Remediation → Choose Destination & Create Workspace /… → …
  • Remediate an A2UI compliance audit finding
  • SKILL.md covers Workflow and References
  • Runs Python scripts from its folder; calls gh and git

What it does

A2ui Remediate Problem is an agent skill from a2ui-project/a2ui. Remediates a specific recommendation from an A2UI compliance report issue, or resolves any general GitHub issue, by inspecting context, implementing minimal targeted fixes, verifying tests, creating a branch, and opening a developer-signed Pull Request. Use when asked to fix or remediate an A2UI compliance audit finding, recommendation, or repository issue.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/pr-description-template.md`, `scripts/extract_recommendation.py` and `scripts/test_extract_recommendation.py`).

It sits in Development, covering Pull requests and Audit readiness. It works with GitHub. The licence is Apache-2.0.

When your agent uses it

  • Remediate an A2UI compliance audit finding
  • Repository issue

Example prompts

  • “Use the a2ui-remediate-problem skill to remediate a specific recommendation from an A2UI compliance report issue, or resolves any general GitHub…”
  • “/a2ui-remediate-problem”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Identify & Read Issue Context
  2. Formulate & Apply Remediation
  3. Choose Destination & Create Workspace / Branch
  4. Commit Changes
  5. Create Pull Request & Notify Issue (Optional / Upon Request)

What it can do on your machine

Read from SKILL.md and the folder at commit ae466ff. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • gh
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

A2ui Remediate Problem loads about 1.5k tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 96 tokens; SKILL.md has 678 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~96
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from a2ui-project/a2ui at commit ae466ff, republished under its Apache-2.0 licence (© a2ui-project). 678 words, ~1,534 tokens.

Download SKILL.mdSave it as .claude/skills/a2ui-remediate-problem/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
a2ui-remediate-problem
description
Remediates a specific recommendation from an A2UI compliance report issue, or resolves any general GitHub issue, by inspecting context, implementing minimal targeted fixes, verifying tests, creating a branch, and opening a developer-signed Pull Request. Use when asked to fix or remediate an A2UI compliance audit finding, recommendation, or repository issue.

A2UI Issue & Compliance Remediation Skill

This skill guides an AI coding agent or engineer on how to remediate a specific recommendation from an A2UI compliance report or resolve any general repository issue and submit a clean, developer-signed Pull Request.

Workflow

Follow these steps to remediate an issue:

Step 1: Identify & Read Issue Context

  1. Determine the Target Issue:

    • If the user provided an issue number or URL in their request, extract ISSUE_NUMBER.
    • If no issue was specified, ask the user (prefer using the ask_question tool): "Which GitHub issue would you like to remediate? (Please provide the issue number or URL, e.g. 2391)"

  2. Retrieve Context & Determine Issue Type:

    • Run the helper script to inspect the issue:
      bash
      python3 .agents/skills/a2ui-remediate-problem/scripts/extract_recommendation.py "${ISSUE_NUMBER}" [RECOMMENDATION_INDEX] --json
    • Scenario A: Compliance Report with Multiple Recommendations:
      • If a recommendation index was provided (e.g. 2), the script extracts that item's details and priority.
      • If no recommendation index was specified, the script outputs all available recommendations in the issue. Ask the user (via ask_question) which recommendation item they would like to address.
      • Review the surrounding audit sections in the report (such as ## Codebase Blueprint Compliance Audit, ## Code & Documentation Sync Audit, or ## Test Quality & Assertions Audit) for detailed findings.
    • Scenario B: General Issue (Bug Report, Feature Request, or Non-Audit Issue):
      • If the issue is not a compliance report, the script returns the issue title and body as the problem statement to remediate.
Step 2: Formulate & Apply Remediation
  1. Identify the files and codebases referenced by the issue or recommendation.
  2. Carefully inspect the current source code, documentation, or blueprint files.
  3. Implement the minimal necessary change to remediate the reported problem.
    • CRITICAL RULE: Do not make unrelated changes, refactorings, or formatting edits outside the scope of the target issue or recommendation.
  4. Format modified files and ensure code style compliance:
    bash
    ./scripts/fix_format.sh
  5. If modifying tests or scripts, execute local tests across the affected packages to ensure no regressions were introduced.
Step 3: Choose Destination & Create Workspace / Branch
  1. Check with the user on where they would like the changes created and what branch name to use (prefer using the ask_question tool or equivalent interactive tool if available):
    • Recommended branch name: remediation/issue-${ISSUE_NUMBER}-${RECOMMENDATION_INDEX} (or remediation/issue-${ISSUE_NUMBER} for general issues).
    • Let the user choose whether to create a separate git worktree (using their preferred local worktree conventions), checkout a new branch in the current directory, or apply changes in place.
  2. Note the chosen branch name in BRANCH_NAME.
  3. Ensure the working tree is clean and up to date with upstream/main.
Show full SKILL.md (307 more words)Show less
Step 4: Commit Changes
  1. Stage all modified files relevant to the remediation:
    bash
    git add -u
  2. Create a conventional commit referencing the issue number:
    • For compliance recommendations:
      bash
      git commit -m "fix(compliance): remediate issue #${ISSUE_NUMBER} recommendation ${RECOMMENDATION_INDEX}"
    • For general issues:
      bash
      git commit -m "fix(scope): remediate issue #${ISSUE_NUMBER} - ${CONCISE_SUMMARY}"
Step 5: Create Pull Request & Notify Issue (Optional / Upon Request)
  1. Check with the user whether they would like to submit a Pull Request (prefer using the ask_question tool or equivalent interactive tool if available):
    • Recommended default: Submit as a Draft PR (--draft) so CI checks run while allowing final review before requesting maintainer approvals.
    • Alternatively, submit directly as ready for review, or skip PR creation if the user wants to inspect changes locally first.
  2. If submitting a PR, generate a clear, descriptive PR title following Conventional Commits that concisely explains the specific fix being made (e.g. fix(swift): create missing top-level README in swift/core). Do NOT include generic issue or recommendation numbers in the PR title.
  3. Draft the PR description into a temporary file pr_description.md following pr-description-template.md.
  4. Push the branch to origin (or user's fork) and create the Pull Request against main:
    bash
    git push -u origin "${BRANCH_NAME}"
PR_URL=$(gh pr create --draft \
  --repo a2ui-project/a2ui \
  --head "${BRANCH_NAME}" \
  --base main \
  --title "${PR_TITLE}" \
  --body-file pr_description.md)
    (Note: Omit --draft if the user prefers an immediate ready-for-review PR. If pushing from a fork, gh pr create automatically resolves the fork's head branch or accepts --head <username>:${BRANCH_NAME}.)
  5. Clean up the temporary file pr_description.md.
  6. Comment on the original issue to notify maintainers of the new PR:
    bash
    gh issue comment "${ISSUE_NUMBER}" \
  --repo a2ui-project/a2ui \
  --body "🤖 Automated remediation triggered! Created PR (${PR_URL}) on branch \`${BRANCH_NAME}\` to address recommendation ${RECOMMENDATION_INDEX}."

References

© a2ui-project, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts, references) in .agents/skills/a2ui-remediate-problem of a2ui-project/a2ui.

  • SKILL.md
  • references/pr-description-template.md
  • scripts/extract_recommendation.py
  • scripts/test_extract_recommendation.py

Open the folder on GitHubat commit ae466ff

Compare with similar skills

A2ui Remediate Problem next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

A2ui Remediate Problem compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
A2ui Remediate Problem this skilla2ui-project/a2ui17k—~1.5kAutomated safety check: PassApache-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

  • GitHub Review Iteration

    prisma/orm

    Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

More from a2ui-project/a2ui

All 20 skills in this repo

  • A2ui Issue Triage

    a2ui-project/a2ui

    Automates the triage of GitHub issues in the A2UI repository.

    17k GitHub stars~1.5k tokensUpdated today
    Auto-check passed

  • A2ui Audit

    a2ui-project/a2ui

    Main coordination skill to run the blueprint compliance, documentation synchronization, and test quality audits, posting the combined results as a labeled GitHub issue.

    17k GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Inference Format Optimizer

    a2ui-project/a2ui

    Iterative benchmarking, evaluation, and algorithmic optimization of alternative A2UI inference formats (such as Express, Atom, and Elemental).

    17k GitHub stars~985 tokensUpdated today
    Auto-check passed

  • A2ui Generate Pydantic Models

    a2ui-project/a2ui

    Automated generator for strongly typed Pydantic v2 data models and basic catalogs across any A2UI protocol version (v0.8, v0.9, v0.9.1, v1.0, etc.).

    17k GitHub stars~2.3k tokensUpdated today
    Auto-check passed

  • A2ui Python Development

    a2ui-project/a2ui

    Grounding, architectural standards, Python best practices, package facade conventions, testing, and verification workflows for developing any Python code across the entire A2UI repository (core…

    17k GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • A2ui Release Python

    a2ui-project/a2ui

    Releases the Python SDKs (a2ui-core, a2ui-agent-sdk) to PyPI by running preflight checks, dispatching the release workflow as a dry run, confirming with the maintainer, publishing, and following the…

    17k GitHub stars~4.2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about A2ui Remediate Problem

What does A2ui Remediate Problem do?

Remediates a specific recommendation from an A2UI compliance report issue, or resolves any general GitHub issue, by inspecting context, implementing minimal targeted fixes, verifying tests, creating…. A2ui Remediate Problem is an agent skill from a2ui-project/a2ui. Remediates a specific recommendation from an A2UI compliance report issue, or resolves any general GitHub issue, by inspecting context, implementing minimal targeted fixes, verifying tests, creating a branch, and opening a developer-signed Pull Request.

When should I use A2ui Remediate Problem?

A2ui Remediate Problem fits situations like: remediate an A2UI compliance audit finding; repository issue.

How do I install A2ui Remediate Problem in Claude Code?

Run `npx skills add a2ui-project/a2ui --skill a2ui-remediate-problem -a claude-code`. Or copy the skill folder (.agents/skills/a2ui-remediate-problem in a2ui-project/a2ui) into .claude/skills/a2ui-remediate-problem in your project. Claude Code loads it when a task matches its description.

How do I install A2ui Remediate Problem in Codex?

Run `npx skills add a2ui-project/a2ui --skill a2ui-remediate-problem -a codex`. Or copy the skill folder (.agents/skills/a2ui-remediate-problem in a2ui-project/a2ui) into .agents/skills/a2ui-remediate-problem in your project. Codex loads it when a task matches its description.

Can I use A2ui Remediate Problem in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add a2ui-project/a2ui --skill a2ui-remediate-problem -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/a2ui-remediate-problem, .gemini/skills/a2ui-remediate-problem, .github/skills/a2ui-remediate-problem and .opencode/skills/a2ui-remediate-problem in your project.

What does A2ui Remediate Problem need to run?

Going by SKILL.md and its folder, A2ui Remediate Problem needs Python for the scripts in its folder and the command-line tools its instructions call (gh and git). Our summary lists: Python 3.

Does A2ui Remediate Problem access the network?

SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is A2ui Remediate Problem safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does A2ui Remediate Problem use?

A2ui Remediate Problem is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does A2ui Remediate Problem use?

About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 704 tokens, read only when the agent opens those files.

What are the alternatives to A2ui Remediate Problem?

Skills that share tags, products or a category with A2ui Remediate Problem: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains A2ui Remediate Problem?

a2ui-project (a GitHub organization) maintains it in a2ui-project/a2ui, which has 16,602 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 7, 2026.

Source: a2ui-project/a2ui on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.