Code Design Rationale Investigator
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
Triage a user submission from the Composer feedback form — a Linear issue labelled "Composer Feedback Form" carrying an R2 debug-log path.
Install User Submissions
$ npx skills add dxos/dxos --skill user-submissions -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dxos/dxos user-submissions --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/user-submissions .claude/skills/user-submissions && 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 "user-submissions" agent skill from https://github.com/dxos/dxos/tree/main/.agents/skills/user-submissions into .claude/skills/user-submissions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-submissions", 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/user-submissionsType 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 user-submissions -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dxos/dxos user-submissions --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/user-submissions .agents/skills/user-submissions && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "user-submissions" agent skill from https://github.com/dxos/dxos/tree/main/.agents/skills/user-submissions into .agents/skills/user-submissions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-submissions", 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 user-submissions -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dxos/dxos user-submissions --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/user-submissions .cursor/skills/user-submissions && 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 "user-submissions" agent skill from https://github.com/dxos/dxos/tree/main/.agents/skills/user-submissions into .cursor/skills/user-submissions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-submissions", 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/user-submissions--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 user-submissions -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dxos/dxos user-submissions --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/user-submissions .gemini/skills/user-submissions && 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 "user-submissions" agent skill from https://github.com/dxos/dxos/tree/main/.agents/skills/user-submissions into .gemini/skills/user-submissions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-submissions", 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 user-submissionsInstalls 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 user-submissions -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/user-submissions .github/skills/user-submissions && 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 "user-submissions" agent skill from https://github.com/dxos/dxos/tree/main/.agents/skills/user-submissions into .github/skills/user-submissions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-submissions", 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 user-submissions -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 user-submissions --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/user-submissions .opencode/skills/user-submissions && 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 "user-submissions" agent skill from https://github.com/dxos/dxos/tree/main/.agents/skills/user-submissions into .opencode/skills/user-submissions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "user-submissions", 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
user-submissions- GitHub stars
- 525
- Token cost
- ~2.6k tokens
- SKILL.md length
- 1,364 words
- Files
- 1
- Skills in repo
- 41
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Triage a user submission from the Composer feedback form — a Linear issue labelled "Composer Feedback Form" carrying an R2 debug-log path.
- Works in 5 steps: Fetch the logs → Read the bundle → Establish root cause from evidence → …
- Working a DX- issue created from a user report
- SKILL.md covers 1. Fetch the logs, 2. Read the bundle, 3. Establish root cause from… and 4. Then one of two outcomes, plus 2 more sections
- Calls curl, node and python3; reaches 950816f3f59b079880a1ae33fb0ec320.r2.cloudflarestorage.com; needs R2_ACCESS_KEY_ID and R2_SECRET_ACCESS_KEY
What it does
User Submissions is an agent skill from dxos/dxos. Triage a user submission from the Composer feedback form — a Linear issue labelled "Composer Feedback Form" carrying an R2 debug-log path. Use when working a DX- issue created from a user report, when an issue body names a composer-feedback-logs- NDJSON bundle, or when asked to find the root cause of a reported bug from its attached logs.
Its SKILL.md is about 2.6k 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 Root cause analysis. It works with Linear. The repository describes itself as: TypeScript implementation of the DXOS protocols, SDK, toolchain and Composer.
When your agent uses it
- Working a DX- issue created from a user report
- An issue body names a composer-feedback-logs- NDJSON bundle
- Asked to find the root cause of a reported bug from its attached logs
Example prompts
- “Composer Feedback Form”
- “/user-submissions”
Requirements
- Python 3
- A credential in R2_SECRET_ACCESS_KEY
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Fetch the logs
- Read the bundle
- Establish root cause from evidence
- Then one of two outcomes
- Close the loop
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:
curlnodepython3
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
950816f3f59b079880a1ae33fb0ec320.r2.cloudflarestorage.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
R2_ACCESS_KEY_IDR2_SECRET_ACCESS_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
User Submissions loads about 2.6k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 1,364 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,364 words (~2,582 tokens).
“A Composer feedback submission becomes a Linear issue with the label Composer Feedback Form. The user's prose is usually near-worthless — often a single word, often literally test. The attached debug logs are the report. The submission is a pointer…”
- name
- user-submissions
Files
Just SKILL.md in .agents/skills/user-submissions of dxos/dxos.
Open the folder on GitHubat commit 2e6b92a
Compare with similar skills
User Submissions 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 |
|---|---|---|---|---|---|---|
| User Submissions this skilldxos/dxos | 525 | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Code Design Rationale Investigatorcursor/plugins | 10k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| OpenLogi macOS Permissions TriageAprilNEA/OpenLogi | 23k | — | ~2.5k | Automated safety check: Notes | Apache-2.0 | |
| Bug Finder for daisyUIsaadeghi/daisyui | 43k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Root Cause Debugginggarrytan/gstack | 136k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Review PRapache/shardingsphere | 21k | — | ~6.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
OpenLogi macOS Permissions Triage
AprilNEA/OpenLogi
Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.
Bug Finder for daisyUI
saadeghi/daisyui
Investigates suspected bugs in the daisyUI monorepo through read-only analysis, then writes a decision-ready fix plan in tmp/bugs without changing any product code.
Root Cause Debugging
garrytan/gstack
Investigates bugs, errors and stack traces in phases and requires a root-cause hypothesis to be confirmed before any fix is written.
Review PR
apache/shardingsphere
Review Apache ShardingSphere or user-authorized downstream pull requests and PR discussions from public or authorized repository evidence.
Graph-Based Bug Tracing
tirth8205/code-review-graph
Traces a bug through a code knowledge graph, following callers, callees and execution flow before opening source files, within a small token budget.
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
Works with
Categories
Questions about User Submissions
What does User Submissions do?
Triage a user submission from the Composer feedback form — a Linear issue labelled "Composer Feedback Form" carrying an R2 debug-log path. User Submissions is an agent skill from dxos/dxos. Triage a user submission from the Composer feedback form — a Linear issue labelled "Composer Feedback Form" carrying an R2 debug-log path.
When should I use User Submissions?
User Submissions fits situations like: working a DX- issue created from a user report; an issue body names a composer-feedback-logs- NDJSON bundle; asked to find the root cause of a reported bug from its attached logs.
How do I install User Submissions in Claude Code?
Run `npx skills add dxos/dxos --skill user-submissions -a claude-code`. Or copy the skill folder (.agents/skills/user-submissions in dxos/dxos) into .claude/skills/user-submissions in your project. Claude Code loads it when a task matches its description.
How do I install User Submissions in Codex?
Run `npx skills add dxos/dxos --skill user-submissions -a codex`. Or copy the skill folder (.agents/skills/user-submissions in dxos/dxos) into .agents/skills/user-submissions in your project. Codex loads it when a task matches its description.
Can I use User Submissions 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 user-submissions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/user-submissions, .gemini/skills/user-submissions, .github/skills/user-submissions and .opencode/skills/user-submissions in your project.
What does User Submissions need to run?
Going by SKILL.md and its folder, User Submissions needs the command-line tools its instructions call (curl, node and python3) and credentials named R2_ACCESS_KEY_ID and R2_SECRET_ACCESS_KEY. Our summary lists: Python 3; A credential in R2_SECRET_ACCESS_KEY.
Does User Submissions access the network?
SKILL.md names 1 domain. In commands or code: 950816f3f59b079880a1ae33fb0ec320.r2.cloudflarestorage.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is User Submissions 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 User Submissions use?
User Submissions 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 User Submissions use?
About 2.6k tokens (SKILL.md is roughly 10k 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 User Submissions?
Skills that share tags, products or a category with User Submissions: Code Design Rationale Investigator (cursor/plugins, 10k stars), OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars), Bug Finder for daisyUI (saadeghi/daisyui, 43k stars) and Root Cause Debugging (garrytan/gstack, 136k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains User Submissions?
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.