Asd Ste100
danyuchn/asd-ste100-skill
A skill your agent uses when English text must be parsed without a human to resolve ambiguity — tool descriptions, error messages, inter-agent instructions, system prompts, status reports — and…
Implement evaluated findings: load code-style rules, apply the accepted fixes, then close out the change with full or quick QA.
Install Resolve Findings
$ npx skills add tobihagemann/turbo --skill resolve-findings -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tobihagemann/turbo resolve-findings --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/tobihagemann/turbo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/codex/skills/resolve-findings .claude/skills/resolve-findings && 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 "resolve-findings" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/resolve-findings into .claude/skills/resolve-findings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-findings", 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/tobihagemann/turbo/tree/main/codex/skills/resolve-findingsType 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 tobihagemann/turbo --skill resolve-findings -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tobihagemann/turbo resolve-findings --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/codex/skills/resolve-findings .agents/skills/resolve-findings && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "resolve-findings" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/resolve-findings into .agents/skills/resolve-findings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-findings", 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 tobihagemann/turbo --skill resolve-findings -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tobihagemann/turbo resolve-findings --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/codex/skills/resolve-findings .cursor/skills/resolve-findings && 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 "resolve-findings" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/resolve-findings into .cursor/skills/resolve-findings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-findings", 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/tobihagemann/turbo.git --path codex/skills/resolve-findings--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 tobihagemann/turbo --skill resolve-findings -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tobihagemann/turbo resolve-findings --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/codex/skills/resolve-findings .gemini/skills/resolve-findings && 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 "resolve-findings" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/resolve-findings into .gemini/skills/resolve-findings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-findings", 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 tobihagemann/turbo resolve-findingsInstalls 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 tobihagemann/turbo --skill resolve-findings -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .github/skills && cp -r skills-src/codex/skills/resolve-findings .github/skills/resolve-findings && 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 "resolve-findings" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/resolve-findings into .github/skills/resolve-findings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-findings", 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 tobihagemann/turbo --skill resolve-findings -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tobihagemann/turbo resolve-findings --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/codex/skills/resolve-findings .opencode/skills/resolve-findings && 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 "resolve-findings" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/resolve-findings into .opencode/skills/resolve-findings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-findings", 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
resolve-findings- GitHub stars
- 408
- Token cost
- ~312 tokens
- SKILL.md length
- 130 words
- Files
- 1
- Skills in repo
- 81
- Repo updated
- First seen
- Licence
- MIT
At a glance
Implement evaluated findings: load code-style rules, apply the accepted fixes, then close out the change with full or quick QA.
- Works in 3 steps: Run $code-style Skill → Run $apply-findings Skill → Close Out the Change
- Asks to resolve findings
- SKILL.md covers Task Tracking, Step 1: Run $code-style Skill, Step 2: Run $apply-findings… and Step 3: Close Out the Change
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Resolve Findings is an agent skill from tobihagemann/turbo. Implement evaluated findings: load code-style rules, apply the accepted fixes, then close out the change with full or quick QA. Use after $evaluate-findings has tagged findings and they need to be implemented, or when the user asks to "resolve findings", "apply evaluated findings", or "dispatch findings to implementation".
Its SKILL.md is about 310 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 Writing & Content, covering Plain language and style rules. The repository describes itself as: Reusable workflows for planning, building, reviewing, and shipping with Claude Code and Codex. The licence is MIT.
When your agent uses it
- Asks to resolve findings
- Apply evaluated findings
- Dispatch findings to implementation
Example prompts
- “resolve findings”
- “apply evaluated findings”
- “dispatch findings to implementation”
- “/resolve-findings”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 931eda5. 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
No scripts in the folder and no shell commands in SKILL.md.
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
Resolve Findings loads about 312 tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 130 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
The full file from tobihagemann/turbo at commit 931eda5, republished under its MIT licence (© tobihagemann). 130 words, ~312 tokens.
Download SKILL.mdSave it as
.claude/skills/resolve-findings/SKILL.md (or your agent's skills folder).- name
- resolve-findings
- description
- Implement evaluated findings: load code-style rules, apply the accepted fixes, then close out the change with full or quick QA. Use after $evaluate-findings has tagged findings and they need to be implemented, or when the user asks to "resolve findings", "apply evaluated findings", or "dispatch findings to implementation".
Resolve Findings
Apply evaluated findings and close out the change.
Task Tracking
At the start, use update_plan to track each step, restating any remaining steps of a parent workflow alongside them:
- Run
$code-styleskill - Run
$apply-findingsskill - Close out the change
Step 1: Run $code-style Skill
Run the $code-style skill to load existence, reuse, mirror, and symmetry rules before editing.
Step 2: Run $apply-findings Skill
Run the $apply-findings skill on the evaluated findings.
Step 3: Close Out the Change
If no changes were made, skip this step.
Use request_user_input to choose how to close out the change:
- Full QA — run the
$finalizeskill - Quick close — run the
$quick-finalizeskill
Then call update_plan to mark this step completed and continue with the next step of the active workflow.
© tobihagemann, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in codex/skills/resolve-findings of tobihagemann/turbo.
Open the folder on GitHubat commit 931eda5
Compare with similar skills
Resolve Findings 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 |
|---|---|---|---|---|---|---|
| Resolve Findings this skilltobihagemann/turbo | 408 | — | ~312 | Automated safety check: Pass | MIT | |
| Asd Ste100danyuchn/asd-ste100-skill | 4.3k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Technical Writing Standardcursor/plugins | 11k | 10 repos | ~2.3k | Automated safety check: Pass | None | |
| Ponytail AuditDietrichGebert/ponytail | 160k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Natural Japanese Business Writingcoji/natural-japanese | 1.9k | — | ~2.1k | Automated safety check: Pass | MIT | |
| PgjevrealZachi/pg-jev | 1.1k | — | ~2.9k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Technical Writing Standard
cursor/plugins
Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.
Ponytail Audit
DietrichGebert/ponytail
Quality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split.
Natural Japanese Business Writing
coji/natural-japanese
Writes and edits Japanese business documents so they read clearly and naturally, removes AI-sounding phrasing and can score how AI-like a text reads.
Pgjev
realZachi/pg-jev
Install, configure, query and explain pgjev (the jev PostgreSQL extension that filters, ranks and classifies rows with plain-language conditions via TypeSafe's Jev model).
Defensive Writing Editor
lennney/stop-that-shit
Cuts defensive disclaimers, stacked hedging and self-protective narration from proposals and summaries, keeping only limits that affect the reader's decision.
More from tobihagemann/turbo
All 81 skills in this repoConsult Oracle
tobihagemann/turbo
Consult ChatGPT Pro via ChatGPT browser automation for problems that resist standard approaches.
Fetch PR Comments
tobihagemann/turbo
Fetch and summarize review feedback and conversation from a GitHub PR (unresolved review threads, review bodies, and PR conversation comments) without making changes.
Recall Rationale
tobihagemann/turbo
Recall why a past change was made by locating the Claude Code transcript that produced it.
Resolve PR Comments
tobihagemann/turbo
Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments.
Resolve PR Comments
tobihagemann/turbo
Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments.
Assess Technical Debt
tobihagemann/turbo
Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, architecture rot, and low-value tests.
Related
Categories
Questions about Resolve Findings
What does Resolve Findings do?
Implement evaluated findings: load code-style rules, apply the accepted fixes, then close out the change with full or quick QA. Resolve Findings is an agent skill from tobihagemann/turbo. Implement evaluated findings: load code-style rules, apply the accepted fixes, then close out the change with full or quick QA.
When should I use Resolve Findings?
Resolve Findings fits situations like: asks to resolve findings; apply evaluated findings; dispatch findings to implementation.
How do I install Resolve Findings in Claude Code?
Run `npx skills add tobihagemann/turbo --skill resolve-findings -a claude-code`. Or copy the skill folder (codex/skills/resolve-findings in tobihagemann/turbo) into .claude/skills/resolve-findings in your project. Claude Code loads it when a task matches its description.
How do I install Resolve Findings in Codex?
Run `npx skills add tobihagemann/turbo --skill resolve-findings -a codex`. Or copy the skill folder (codex/skills/resolve-findings in tobihagemann/turbo) into .agents/skills/resolve-findings in your project. Codex loads it when a task matches its description.
Can I use Resolve Findings 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 tobihagemann/turbo --skill resolve-findings -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/resolve-findings, .gemini/skills/resolve-findings, .github/skills/resolve-findings and .opencode/skills/resolve-findings in your project.
What does Resolve Findings need to run?
SKILL.md names no scripts, command-line tools or credentials: Resolve Findings is instructions for the agent only.
Does Resolve Findings 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 Resolve Findings 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 Resolve Findings use?
Resolve Findings is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Resolve Findings use?
About 312 tokens (SKILL.md is roughly 1.2k 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 Resolve Findings?
Skills that share tags, products or a category with Resolve Findings: Asd Ste100 (danyuchn/asd-ste100-skill, 4.3k stars), Technical Writing Standard (cursor/plugins, 11k stars), Ponytail Audit (DietrichGebert/ponytail, 160k stars) and Natural Japanese Business Writing (coji/natural-japanese, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Resolve Findings?
tobihagemann (a GitHub user) maintains it in tobihagemann/turbo, which has 408 GitHub stars. The repository holds 81 skills in this directory. The repository was last updated on October 9, 2026.
Source: tobihagemann/turbo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.