Summarise Ecosystem Results
astral-sh/ruff
A skill your agent uses when a user says "summarise ecosystem results", "summarize this ty ecosystem report", "what changed in this ecosystem run?", or asks to summarise or summarize ty ecosystem…
Work on Panache's delegation of embedded code blocks to third-party formatters and linters (ruff, shfmt, shellcheck, rustfmt, ...) — add or change a preset, fix the offset mapping that translates a…
$ npx skills add jolars/panache --skill external-tools -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jolars/panache external-tools --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/jolars/panache.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/external-tools .claude/skills/external-tools && 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 "external-tools" agent skill from https://github.com/jolars/panache/tree/main/.agents/skills/external-tools into .claude/skills/external-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "external-tools", 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/jolars/panache/tree/main/.agents/skills/external-toolsType 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 jolars/panache --skill external-tools -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jolars/panache external-tools --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jolars/panache.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/external-tools .agents/skills/external-tools && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "external-tools" agent skill from https://github.com/jolars/panache/tree/main/.agents/skills/external-tools into .agents/skills/external-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "external-tools", 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 jolars/panache --skill external-tools -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jolars/panache external-tools --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jolars/panache.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/external-tools .cursor/skills/external-tools && 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 "external-tools" agent skill from https://github.com/jolars/panache/tree/main/.agents/skills/external-tools into .cursor/skills/external-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "external-tools", 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/jolars/panache.git --path .agents/skills/external-tools--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 jolars/panache --skill external-tools -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jolars/panache external-tools --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jolars/panache.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/external-tools .gemini/skills/external-tools && 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 "external-tools" agent skill from https://github.com/jolars/panache/tree/main/.agents/skills/external-tools into .gemini/skills/external-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "external-tools", 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 jolars/panache external-toolsInstalls 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 jolars/panache --skill external-tools -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jolars/panache.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/external-tools .github/skills/external-tools && 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 "external-tools" agent skill from https://github.com/jolars/panache/tree/main/.agents/skills/external-tools into .github/skills/external-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "external-tools", 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 jolars/panache --skill external-tools -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jolars/panache external-tools --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jolars/panache.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/external-tools .opencode/skills/external-tools && 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 "external-tools" agent skill from https://github.com/jolars/panache/tree/main/.agents/skills/external-tools into .opencode/skills/external-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "external-tools", 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.
external-toolsWork on Panache's delegation of embedded code blocks to third-party formatters and linters (ruff, shfmt, shellcheck, rustfmt, ...) — add or change a preset, fix the offset mapping that translates a…
External Tools is an agent skill from jolars/panache. Work on Panache's delegation of embedded code blocks to third-party formatters and linters (ruff, shfmt, shellcheck, rustfmt, ...) — add or change a preset, fix the offset mapping that translates a tool's line/column diagnostics back onto document positions, or debug why a tool is not being invoked. Use when touching the [formatters] / [linters] config surface or anything under the external tool execution paths.
Its SKILL.md is about 1.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 Linting and formatting. It works with Ruff. The repository describes itself as: Language server, formatter, and linter for Markdown, Quarto, and R Markdown. The licence is MIT.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit e28d49b. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
cargoFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
github.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
External Tools loads about 1.2k tokens when it runs. Until then it costs about 109 tokens; SKILL.md has 535 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.
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.
The full file from jolars/panache at commit e28d49b, republished under its MIT licence (© jolars). 535 words, ~1,200 tokens.
.claude/skills/external-tools/SKILL.md (or your agent's skills folder).Use this skill when adding a tool preset, changing how an external tool is invoked, or debugging wrong spans on diagnostics that came from one.
Key architectural fact: this is entirely a host concern.
crates/panache-formatter never spawns a process. If a change wants to run a
subprocess from the formatter crate, the design is wrong — the formatter crate
is dependency-lean by intent and is consumed as a published crate by
jolars/dprint-plugin-panache.
| Path | Role |
|---|---|
src/config/formatter_presets.rs | PRESETS table of FormatterPresetMetadata |
src/linter/external_linters.rs | Linter preset table + tool output parsing |
src/external_tools_common.rs | Shared process plumbing, invocation budget, warning de-dup |
src/external_formatters_sync.rs | Synchronous formatter execution (CLI + LSP) |
src/linter/external_linters_sync.rs | Synchronous linter execution |
src/external_formatters_common.rs | Reindentation and fence-boundary handling of tool output |
src/linter/code_block_collector.rs | Gathers the code blocks to dispatch |
src/linter/offsets.rs | Maps tool line/column back onto document offsets |
Add an entry to the PRESETS table:
FormatterPresetMetadata {
name: "air",
url: "https://github.com/posit-dev/air",
description: "R formatter for reproducible style conventions.",
cmd: "air",
args: &["format", "{}"],
stdin: false,
supported_languages: &["r"],
},{} in args is the filename placeholder.stdin: false means the tool rewrites a temp file in place rather than
reading stdin; stdin: true means it reads stdin and writes stdout.supported_languages is matched against the code block's language token, so
include every alias users actually write (sh/bash, r/R).build.rs reruns on src/config/formatter_presets.rs and
src/linter/external_linters.rs, so adding an entry regenerates
docs/reference/_formatter-presets-details.qmd and
_linter-presets-details.qmd. Never hand-edit those.
Verify the preset resolves and the tool actually runs before committing —
a wrong cmd or arg order fails silently into "tool not found" warnings.
The external tool sees dedented code with no fence and no container prefix.
Its reported line and column numbers are relative to that stripped view, so
they must be translated back onto the original document
(src/linter/offsets.rs).
Anything that changes the stripped view changes the mapping:
When a diagnostic points at the wrong line, suspect the mapping before suspecting the tool. Write the failing case as a fixture with the block nested in a list item — that is where the prefix arithmetic goes wrong.
init_external_tool_budget in src/external_tools_common.rs bounds how many
external processes a single run may spawn, so a large document or a directory
walk cannot fork thousands of subprocesses. If a tool appears to stop being
applied partway through a big run, check the budget before assuming a
detection bug. external-max-parallel is the related config key.
Missing-tool warnings are de-duplicated per run, so a tool absent from PATH
warns once, not once per code block.
cargo test --test external_formatters
cargo test --test external_lintersThese require the real binaries on PATH and skip when a tool is absent —
which means they can pass locally for the wrong reason. Run them inside the
devenv shell, which installs shfmt, ruff, shellcheck, stylua, eslint,
and the rest.
supported_languages?PATH as the CLI sees it?cargo run -- clean --all or pass --no-cache. The cache key is only
panache@<version>, so it does not invalidate on code changes under a fixed
in-development version.RUST_LOG=debug cargo run -- format document.qmd to see the dispatch
decisions.© jolars, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agents/skills/external-tools of jolars/panache.
Open the folder on GitHubat commit e28d49b
External Tools 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 |
|---|---|---|---|---|---|---|
| External Tools this skilljolars/panache | 235 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Summarise Ecosystem Resultsastral-sh/ruff | 50k | 1 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Minimizing Ty Ecosystem Changesastral-sh/ruff | 50k | — | ~4.6k | Automated safety check: Pass | MIT | |
| Kedro Babysitkedro-org/kedro | 11k | — | ~4k | Automated safety check: Pass | Custom licence | |
| Saleor Commit Workflowsaleor/saleor | 23k | — | ~575 | Automated safety check: Pass | BSD-3-Clause | |
| Mnemosyne Contextmnemosyne-oss/mnemosyne | 3.4k | — | ~2.6k | Automated safety check: Pass | MIT |
astral-sh/ruff
A skill your agent uses when a user says "summarise ecosystem results", "summarize this ty ecosystem report", "what changed in this ecosystem run?", or asks to summarise or summarize ty ecosystem…
astral-sh/ruff
A skill your agent uses when a user says "minimize this ty ecosystem change", "reproduce this ecosystem result", "investigate a primer difference", "investigate a mypyprimer difference"…
kedro-org/kedro
Run Kedro's local lint / format / type-check / tests on changed files (uses the project's pre-commit hooks, ruff, mypy, pytest, lint-imports, detect-secrets, Make targets — in the right venv), or…
saleor/saleor
Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.
mnemosyne-oss/mnemosyne
Load this when working on the mnemosyne memory system — its repo, sync server, memory databases, or CI.
astral-sh/ruff
A skill your agent uses when a user says "add a ty rule", "add a ty diagnostic", "write this new ty diagnostic", "change a ty error message", "review ty diagnostics", or asks to add, update, or…
jolars/panache
Add a new block-level or inline-level syntax construct to Panache's parser and formatter — confirm the pandoc-native shape first, add SyntaxKinds for every byte category, gate it behind an extension…
jolars/panache
Grow Panache's CommonMark spec conformance under Flavor::CommonMark by running every spec.txt example through the shared parser, comparing rendered HTML against the spec's expected HTML…
jolars/panache
Investigate panache's linter (and, secondarily, its parser) against a real-world Quarto/Markdown codebase.
jolars/panache
Implement or debug Panache's TeX math parser and formatter internals, including the lossless CST, semantic model, diagnostics, and Badness parity.
jolars/panache
Add a new built-in lint rule to the Panache linter — wire it into the registry, gate it on the right extension/flavor, add a regression fixture with focused assertions, and document it.
jolars/panache
Profile-driven performance work on the panache parser or formatter.
Works with
Categories
Work on Panache's delegation of embedded code blocks to third-party formatters and linters (ruff, shfmt, shellcheck, rustfmt, ...) — add or change a preset, fix the offset mapping that translates a…. External Tools is an agent skill from jolars/panache.) — add or change a preset, fix the offset mapping that translates a tool's line/column diagnostics back onto document positions, or debug why a tool is not being invoked.
External Tools fits situations like: touching the [formatters] / [linters] config surface; anything under the external tool execution paths.
Run `npx skills add jolars/panache --skill external-tools -a claude-code`. Or copy the skill folder (.agents/skills/external-tools in jolars/panache) into .claude/skills/external-tools in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jolars/panache --skill external-tools -a codex`. Or copy the skill folder (.agents/skills/external-tools in jolars/panache) into .agents/skills/external-tools in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jolars/panache --skill external-tools -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/external-tools, .gemini/skills/external-tools, .github/skills/external-tools and .opencode/skills/external-tools in your project.
Going by SKILL.md and its folder, External Tools needs the command-line tools its instructions call (cargo).
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
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.
External Tools is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with External Tools: Summarise Ecosystem Results (astral-sh/ruff, 50k stars), Minimizing Ty Ecosystem Changes (astral-sh/ruff, 50k stars), Kedro Babysit (kedro-org/kedro, 11k stars) and Saleor Commit Workflow (saleor/saleor, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jolars (a GitHub user) maintains it in jolars/panache, which has 235 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 7, 2026.
Source: jolars/panache on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.