Guidelines
akash-network/node
Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.
Clean up code with lightweight clarity improvements. An agent skill from jrkerns/pylinac.
Install Clean Up
$ npx skills add jrkerns/pylinac --skill clean-up -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jrkerns/pylinac clean-up --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/jrkerns/pylinac.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/clean-up .claude/skills/clean-up && 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 "clean-up" agent skill from https://github.com/jrkerns/pylinac/tree/master/.agents/skills/clean-up into .claude/skills/clean-up/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-up", 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/jrkerns/pylinac/tree/master/.agents/skills/clean-upType 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 jrkerns/pylinac --skill clean-up -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jrkerns/pylinac clean-up --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jrkerns/pylinac.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/clean-up .agents/skills/clean-up && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "clean-up" agent skill from https://github.com/jrkerns/pylinac/tree/master/.agents/skills/clean-up into .agents/skills/clean-up/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-up", 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 jrkerns/pylinac --skill clean-up -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jrkerns/pylinac clean-up --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jrkerns/pylinac.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/clean-up .cursor/skills/clean-up && 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 "clean-up" agent skill from https://github.com/jrkerns/pylinac/tree/master/.agents/skills/clean-up into .cursor/skills/clean-up/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-up", 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/jrkerns/pylinac.git --path .agents/skills/clean-up--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 jrkerns/pylinac --skill clean-up -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jrkerns/pylinac clean-up --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jrkerns/pylinac.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/clean-up .gemini/skills/clean-up && 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 "clean-up" agent skill from https://github.com/jrkerns/pylinac/tree/master/.agents/skills/clean-up into .gemini/skills/clean-up/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-up", 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 jrkerns/pylinac clean-upInstalls 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 jrkerns/pylinac --skill clean-up -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jrkerns/pylinac.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/clean-up .github/skills/clean-up && 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 "clean-up" agent skill from https://github.com/jrkerns/pylinac/tree/master/.agents/skills/clean-up into .github/skills/clean-up/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-up", 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 jrkerns/pylinac --skill clean-up -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jrkerns/pylinac clean-up --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jrkerns/pylinac.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/clean-up .opencode/skills/clean-up && 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 "clean-up" agent skill from https://github.com/jrkerns/pylinac/tree/master/.agents/skills/clean-up into .opencode/skills/clean-up/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clean-up", 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
clean-up- GitHub stars
- 202
- Token cost
- ~146 tokens
- SKILL.md length
- 69 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
Clean up code with lightweight clarity improvements. An agent skill from jrkerns/pylinac.
- Tasks that involve Refactoring
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Clean Up is an agent skill from jrkerns/pylinac. Clean up code with lightweight clarity improvements
Its SKILL.md is about 150 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 Refactoring. The repository describes itself as: An image analysis library for medical physics. The licence is MIT.
When your agent uses it
- Tasks that involve Refactoring
Example prompts
- “/clean-up”
What it can do on your machine
Read from SKILL.md and the folder at commit 499b06c. 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
Clean Up loads about 146 tokens when it runs. Until then it costs about 15 tokens; SKILL.md has 69 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 jrkerns/pylinac at commit 499b06c, republished under its MIT licence (© jrkerns). 69 words, ~146 tokens.
Download SKILL.mdSave it as
.claude/skills/clean-up/SKILL.md (or your agent's skills folder).- name
- clean-up
- description
- Clean up code with lightweight clarity improvements
- disable-model-invocation
- true
clean-up
When cleaning up, the goal is to make simple modifications that improve clarity or structure of the code without modifying lots of logic.
Don't be aggressive Opportunities for refactor include:
- Adding or clarifying types
- Adding or clarifying docstrings
- Adding comments to code blocks
- Using newer syntax supported by the language
- Clarifying documentation
Do not make helper functions that are 2 lines or less. In that case, don't refactor.
© jrkerns, 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 .agents/skills/clean-up of jrkerns/pylinac.
Open the folder on GitHubat commit 499b06c
Compare with similar skills
Clean Up 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 |
|---|---|---|---|---|---|---|
| Clean Up this skilljrkerns/pylinac | 202 | — | ~146 | Automated safety check: Pass | MIT | |
| Guidelinesakash-network/node | 1.1k | 20 repos | ~577 | Automated safety check: Pass | MIT | |
| Component Refactoringlangflow-ai/langflow | 155k | — | ~3.5k | Automated safety check: Pass | MIT | |
| Migrate Core Code to Submodulestinyhumansai/openhuman | 42k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| ast-grep Structural Searchcode-yeongyu/oh-my-openagent | 70k | — | ~3.3k | Automated safety check: Pass | MIT | |
| Systematic Code Refactoringluongnv89/claude-howto | 42k | — | ~3k | Automated safety check: Pass | MIT |
Similar skills
Component Refactoring
langflow-ai/langflow
Refactor high-complexity React components in Langflow frontend.
Migrate Core Code to Submodules
tinyhumansai/openhuman
Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.
ast-grep Structural Search
code-yeongyu/oh-my-openagent
Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.
Systematic Code Refactoring
luongnv89/claude-howto
Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.
Codex
skills-directory/skill-codex
A skill your agent uses when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing
More from jrkerns/pylinac
Generate Pull Request
jrkerns/pylinac
Generate a draft Bitbucket pull request with proper formatting
Pull Request Review
jrkerns/pylinac
Review a Bitbucket pull request against the project checklist
Refactor
jrkerns/pylinac
Refactor code for big-picture architectural improvements. An agent skill from jrkerns/pylinac.
Related
Categories
Questions about Clean Up
What does Clean Up do?
Clean up code with lightweight clarity improvements. An agent skill from jrkerns/pylinac. Clean Up is an agent skill from jrkerns/pylinac.
When should I use Clean Up?
Clean Up fits situations like: tasks that involve Refactoring.
How do I install Clean Up in Claude Code?
Run `npx skills add jrkerns/pylinac --skill clean-up -a claude-code`. Or copy the skill folder (.agents/skills/clean-up in jrkerns/pylinac) into .claude/skills/clean-up in your project. Claude Code loads it when a task matches its description.
How do I install Clean Up in Codex?
Run `npx skills add jrkerns/pylinac --skill clean-up -a codex`. Or copy the skill folder (.agents/skills/clean-up in jrkerns/pylinac) into .agents/skills/clean-up in your project. Codex loads it when a task matches its description.
Can I use Clean Up 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 jrkerns/pylinac --skill clean-up -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/clean-up, .gemini/skills/clean-up, .github/skills/clean-up and .opencode/skills/clean-up in your project.
What does Clean Up need to run?
SKILL.md names no scripts, command-line tools or credentials: Clean Up is instructions for the agent only.
Does Clean Up 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 Clean Up 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 Clean Up use?
Clean Up 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 Clean Up use?
About 146 tokens (SKILL.md is roughly 584 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 Clean Up?
Skills that share tags, products or a category with Clean Up: Guidelines (akash-network/node, 1.1k stars), Component Refactoring (langflow-ai/langflow, 155k stars), Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars) and ast-grep Structural Search (code-yeongyu/oh-my-openagent, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Clean Up?
jrkerns (a GitHub user) maintains it in jrkerns/pylinac, which has 202 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 8, 2026.
Source: jrkerns/pylinac on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.