Trellis Session Insight
mindfold-ai/Trellis
Reach into past AI conversation history through the trellis mem CLI.
Drive a live Composer page from the agent side via the loopback debug port — evaluate expressions against the running client, list plugins and operations, invoke an operation.
Install Composer Debug
$ npx skills add dxos/dxos --skill composer-debug -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dxos/dxos composer-debug --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dxos/dxos.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/composer-debug .claude/skills/composer-debug && rm -rf skills-srcUse ~/.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/
Install the "composer-debug" agent skill from https://github.com/dxos/dxos/tree/main/.agents/skills/composer-debug into .claude/skills/composer-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "composer-debug", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dxos/dxos/tree/main/.agents/skills/composer-debugType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dxos/dxos --skill composer-debug -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dxos/dxos composer-debug --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dxos/dxos.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/composer-debug .agents/skills/composer-debug && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "composer-debug" agent skill from https://github.com/dxos/dxos/tree/main/.agents/skills/composer-debug into .agents/skills/composer-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "composer-debug", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dxos/dxos --skill composer-debug -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dxos/dxos composer-debug --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dxos/dxos.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/composer-debug .cursor/skills/composer-debug && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "composer-debug" agent skill from https://github.com/dxos/dxos/tree/main/.agents/skills/composer-debug into .cursor/skills/composer-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "composer-debug", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dxos/dxos.git --path .agents/skills/composer-debug--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dxos/dxos --skill composer-debug -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dxos/dxos composer-debug --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dxos/dxos.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/composer-debug .gemini/skills/composer-debug && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "composer-debug" agent skill from https://github.com/dxos/dxos/tree/main/.agents/skills/composer-debug into .gemini/skills/composer-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "composer-debug", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dxos/dxos composer-debugInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dxos/dxos --skill composer-debug -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dxos/dxos.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/composer-debug .github/skills/composer-debug && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "composer-debug" agent skill from https://github.com/dxos/dxos/tree/main/.agents/skills/composer-debug into .github/skills/composer-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "composer-debug", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dxos/dxos --skill composer-debug -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dxos/dxos composer-debug --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dxos/dxos.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/composer-debug .opencode/skills/composer-debug && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "composer-debug" agent skill from https://github.com/dxos/dxos/tree/main/.agents/skills/composer-debug into .opencode/skills/composer-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "composer-debug", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
composer-debug- GitHub stars
- 525
- Token cost
- ~5.2k tokens
- SKILL.md length
- 1,999 words
- Files
- 1
- Skills in repo
- 41
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Drive a live Composer page from the agent side via the loopback debug port — evaluate expressions against the running client, list plugins and operations, invoke an operation.
- Works in 6 steps: Handoff — the user opens the port → Connect → Writing snippets → …
- Debugging a booting-but-misbehaving app (hang
- SKILL.md covers Safety, 1. Handoff — the user opens…, 2. Connect and 3. Writing snippets, plus 4 more sections
- Calls node
What it does
Composer Debug is an agent skill from dxos/dxos. Drive a live Composer page from the agent side via the loopback debug port — evaluate expressions against the running client, list plugins and operations, invoke an operation. Use when debugging a booting-but-misbehaving app (hang, bad query, plugin fault, wrong UI state) and you would otherwise ask the user to paste console output. The user opens the port; the agent never opens a browser. For a profile that will not boot, or for storage-level forensics, use composer-forensics instead.
Its SKILL.md is about 5.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Debugging. The repository describes itself as: TypeScript implementation of the DXOS protocols, SDK, toolchain and Composer.
When your agent uses it
- Debugging a booting-but-misbehaving app (hang
- Wrong UI state) and you would otherwise ask the user to paste console output
Example prompts
- “/composer-debug”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
- Handoff — the user opens the port
- Connect
- Writing snippets
- What is in scope
- Recipes
- Gotchas
What it can do on your machine
Read from SKILL.md and the folder at commit f0fc12a. 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
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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 Debug loads about 5.2k tokens when it runs. Until then it costs about 127 tokens; SKILL.md has 1,999 words of instructions outside code blocks.
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,999 words (~5,207 tokens).
“Evaluate code in the user's live Composer tab and read the structured result, instead of writing a probe for a human to paste into DevTools and screenshot back. A wrong probe costs a retry, not a round trip.”
- name
- composer-debug
Files
Just SKILL.md in .agents/skills/composer-debug of dxos/dxos.
Open the folder on GitHubat commit f0fc12a
Compare with similar skills
Composer Debug 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Composer Debug this skilldxos/dxos | 525 | — | ~5.2k | Automated safety check: Pass | Custom licence | |
| Trellis Session Insightmindfold-ai/Trellis | 15k | 4 repos | ~1.7k | Automated safety check: Pass | AGPL-3.0 | |
| Native Data FetchingCherryHQ/cherry-studio-app | 4k | 6 repos | ~2.9k | Automated safety check: Notes | MIT | |
| Debugging Executionsn8n-io/n8n | 207k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Aoti Debugpytorch/pytorch | 104k | 1 repos | ~1.7k | Automated safety check: Pass | Custom licence | |
| Herdr Throwaway Reproductionherdrdev/herdr | 43k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Native Data Fetching
CherryHQ/cherry-studio-app
A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.
- Official
Debugging Executions
n8n-io/n8n
Debug failed or wrong-output workflow executions using executions tools.
Aoti Debug
pytorch/pytorch
Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.
Herdr Throwaway Reproduction
herdrdev/herdr
Runs a disposable, uniquely named Herdr session inside an existing one so runtime, pane, terminal or API bugs can be reproduced without touching the main session.
Systematic Debugging
ultralisp/ultralisp
A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes
More from dxos/dxos
All 41 skills in this repoAgentic 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…
Composer Forensics
dxos/dxos
Forensically inspect and repair Composer browser profiles — offline (Chrome OPFS / SQLite extract) or live via /recovery.html debug port.
Migrate Oxfmt
dxos/dxos
Guide for migrating a project from Prettier or Biome to Oxfmt.
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…
Subduction Policy
dxos/dxos
Reference for SubductionPolicy (the four hooks authorizeConnect, authorizeFetch, authorizePut, filterAuthorizedFetch passed via Subduction.hydrate(..., policy) or new Repo({ subductionPolicy })).
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.
Related
Categories
Questions about Composer Debug
What does Composer Debug do?
Drive a live Composer page from the agent side via the loopback debug port — evaluate expressions against the running client, list plugins and operations, invoke an operation. Composer Debug is an agent skill from dxos/dxos. Drive a live Composer page from the agent side via the loopback debug port — evaluate expressions against the running client, list plugins and operations, invoke an operation.
When should I use Composer Debug?
Composer Debug fits situations like: debugging a booting-but-misbehaving app (hang; wrong UI state) and you would otherwise ask the user to paste console output.
How do I install Composer Debug in Claude Code?
Run `npx skills add dxos/dxos --skill composer-debug -a claude-code`. Or copy the skill folder (.agents/skills/composer-debug in dxos/dxos) into .claude/skills/composer-debug in your project. Claude Code loads it when a task matches its description.
How do I install Composer Debug in Codex?
Run `npx skills add dxos/dxos --skill composer-debug -a codex`. Or copy the skill folder (.agents/skills/composer-debug in dxos/dxos) into .agents/skills/composer-debug in your project. Codex loads it when a task matches its description.
Can I use Composer Debug 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-debug -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-debug, .gemini/skills/composer-debug, .github/skills/composer-debug and .opencode/skills/composer-debug in your project.
What does Composer Debug need to run?
Going by SKILL.md and its folder, Composer Debug needs the command-line tools its instructions call (node).
Does Composer Debug access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Composer Debug 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 Debug use?
Composer Debug 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 Debug use?
About 5.2k tokens (SKILL.md is roughly 21k 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 Debug?
Skills that share tags, products or a category with Composer Debug: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Debugging Executions (n8n-io/n8n, 207k stars) and Aoti Debug (pytorch/pytorch, 104k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Composer Debug?
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 8, 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.