New: 98,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

Composer QA

by dxos in dxos/dxos

Run the executable QA of a .mdl spec — a test QA-n, a suite, or every suite carrying a tag — against a Composer dev server you start, driving each step as one operation call through the agent debug…

Custom licenceAuto-check passed

Install Composer QA

skills CLI
$ npx skills add dxos/dxos --skill composer-qa -a claude-code

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

GitHub CLI
$ gh skill install dxos/dxos composer-qa --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/dxos/dxos.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/composer-qa .claude/skills/composer-qa && 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
composer-qa
GitHub stars
525
Token cost
~4k tokens
SKILL.md length
1,896 words
Files
1
Skills in repo
41
Repo updated
First seen
Licence
Custom licence

At a glance

Run the executable QA of a .mdl spec — a test QA-n, a suite, or every suite carrying a tag — against a Composer dev server you start, driving each step as one operation call through the agent debug…

  • Works in 9 steps: Pick what to run → Consent → Start the server and open the port → …
  • Asked to QA Composer
  • SKILL.md covers 1. Pick what to run, 2. Consent, 3. Start the server and open… and 4. Run a test, plus 6 more sections
  • Calls node and curl

What it does

Composer QA is an agent skill from dxos/dxos. Run the executable QA of a .mdl spec — a test QA-n, a suite, or every suite carrying a tag — against a Composer dev server you start, driving each step as one operation call through the agent debug port, judging every step by the UI snapshot, and writing a per-run report. Use when asked to QA Composer, to run a plugin's QA section, to verify a change end to end against the real app rather than a test runner, or when /dxos:qa is invoked. For ad-hoc probing of a live page use composer-debug; to record a walkthrough…

Its SKILL.md is about 4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: TypeScript implementation of the DXOS protocols, SDK, toolchain and Composer.

When your agent uses it

  • Asked to QA Composer
  • Run a plugins QA section
  • Verify a change end to end against the real app rather than a test runner
  • /dxos:qa is invoked

Example prompts

  • “/composer-qa”

Workflow steps

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

  1. Pick what to run
  2. Consent
  3. Start the server and open the port
  4. Run a test
  5. Run a suite
  6. Report
  7. Feed findings back
  8. Snapshot on demand
  9. Stop what you started

What it can do on your machine

Read from SKILL.md and the folder at commit 2e6b92a. 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

    Shell commands in SKILL.md call:

    • node
    • curl

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

  • Network

    No URLs in SKILL.md. Its commands use curl, 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

Composer QA loads about 4k tokens when it runs. Until then it costs about 142 tokens; SKILL.md has 1,896 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~142
When it runs · the whole SKILL.md, loaded when a task matches
~4k

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); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,896 words (~3,976 tokens).

“A test is a written plan that a human and an agent execute from the same source: the human reads do:, you invoke: and evaluate assert:, both judge expect:. The language is packages/reflect/deus/lang/qa.mdl — read it once; its Execution Rules…”

— opening of SKILL.md by dxos, Custom licence
name
composer-qa

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .agents/skills/composer-qa of dxos/dxos.

Open the folder on GitHubat commit 2e6b92a

Compare with similar skills

Composer QA 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.

Composer QA compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Composer QA this skilldxos/dxos525—~4kAutomated safety check: PassCustom licence
Executealirezarezvani/claude-skills28k—~831Automated safety check: PassMIT
Debugging Executionsn8n-io/n8n207k—~2.6kAutomated safety check: PassCustom licence
Ulw Executecode-yeongyu/oh-my-openagent70k—~6.3kAutomated safety check: PassCustom licence
Executebrycewang-stanford/Auto-Empirical-Research-Skills4.5k—~370Automated safety check: NotesCustom licence
Docker Composesickn33/agentic-awesome-skills47k1 repos~2.2kAutomated safety check: NotesMIT

Similar skills

  • Execute

    alirezarezvani/claude-skills

    /cs:execute <decision — Generate a 90-day execution plan with weekly milestones, DRIs, and check-in cadence from an approved decision.

    28k GitHub stars~831 tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed

  • Debugging Executions

    n8n-io/n8n

    Official

    Debug failed or wrong-output workflow executions using executions tools.

    207k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed

  • Ulw Execute

    code-yeongyu/oh-my-openagent

    Executes a written ulw-plan work plan with Boulder state, evidence ledger, worktree discipline, and parallel subagents.

    70k GitHub stars~6.3k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Execute

    brycewang-stanford/Auto-Empirical-Research-Skills

    Executes all registered notebooks, strips noisy cell metadata, and syncs Jupytext pairs.

    4.5k GitHub stars~370 tokensUpdated 3 days ago
    Data & AnalyticsAuto-check: notes

  • Docker Compose

    sickn33/agentic-awesome-skills

    Define and run multi-container Docker applications using Docker Compose.

    47k GitHub starsUsed in 1 repo~2.2k tokens
    DevOps & CloudAuto-check: notes

  • Safe SQL Execution

    supabase/supabase

    Official

    A skill your agent uses whenever code will build, return, fetch, or execute SQL that runs against a user's real Postgres database — even when the request reads like an ordinary feature or bug fix…

    111k GitHub stars~4.2k tokensUpdated today
    DatabasesAuto-check passed

More from dxos/dxos

All 41 skills in this repo

  • Agentic Review

    dxos/dxos

    Run the rule-driven agentic code review — discover rule blocks in the repo's .mdl files, prepare per-rule review groups (full project by default; diff-only with --pr-only), spawn one focused Sonnet…

    525 GitHub stars~4.4k tokensUpdated today
    Auto-check passed

  • Composer Forensics

    dxos/dxos

    Forensically inspect and repair Composer browser profiles — offline (Chrome OPFS / SQLite extract) or live via /recovery.html debug port.

    525 GitHub stars~3.1k tokensUpdated today
    Auto-check passed

  • Migrate Oxfmt

    dxos/dxos

    Guide for migrating a project from Prettier or Biome to Oxfmt.

    525 GitHub starsUsed in 3 repos~2.2k tokens
    Auto-check passed

  • Moon

    dxos/dxos

    This skill should be used when the user asks to "configure moon", "set up moonrepo", "create moon tasks", "run moon commands", "configure moon workspace", "add moon project", "moon ci setup", "moon…

    525 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Subduction Policy

    dxos/dxos

    Reference for SubductionPolicy (the four hooks authorizeConnect, authorizeFetch, authorizePut, filterAuthorizedFetch passed via Subduction.hydrate(..., policy) or new Repo({ subductionPolicy })).

    525 GitHub stars~3.4k tokensUpdated today
    Auto-check passed

  • Autocue

    dxos/dxos

    Record a demo of the running app that the agent drives itself — a .mdl QA test or an ad-hoc walkthrough — as a captioned .webm (or a screenshot), trimmed of dead air and ready to attach.

    525 GitHub stars~12k tokensUpdated today
    Auto-check passed

Questions about Composer QA

What does Composer QA do?

Run the executable QA of a .mdl spec — a test QA-n, a suite, or every suite carrying a tag — against a Composer dev server you start, driving each step as one operation call through the agent debug…. Composer QA is an agent skill from dxos/dxos.mdl spec — a test QA-n, a suite, or every suite carrying a tag — against a Composer dev server you start, driving each step as one operation call through the agent debug port, judging every step by the UI snapshot, and writing a per-run report.

When should I use Composer QA?

Composer QA fits situations like: asked to QA Composer; run a plugins QA section; verify a change end to end against the real app rather than a test runner; /dxos:qa is invoked.

How do I install Composer QA in Claude Code?

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

How do I install Composer QA in Codex?

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

Can I use Composer QA 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 dxos/dxos --skill composer-qa -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/composer-qa, .gemini/skills/composer-qa, .github/skills/composer-qa and .opencode/skills/composer-qa in your project.

What does Composer QA need to run?

Going by SKILL.md and its folder, Composer QA needs the command-line tools its instructions call (node and curl).

Does Composer QA access the network?

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

Is Composer QA 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. Review the folder before installing.

What licence does Composer QA use?

Composer QA has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Composer QA use?

About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Composer QA?

Skills that share tags, products or a category with Composer QA: Execute (alirezarezvani/claude-skills, 28k stars), Debugging Executions (n8n-io/n8n, 207k stars), Ulw Execute (code-yeongyu/oh-my-openagent, 70k stars) and Execute (brycewang-stanford/Auto-Empirical-Research-Skills, 4.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Composer QA?

dxos (a GitHub organization) maintains it in dxos/dxos, which has 525 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on October 9, 2026.

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