Rtk Skill
sopaco/deepwiki-rs
A skill your agent uses when running shell commands that produce verbose output (git, test, build, lint, package managers, docker).
Installing dependencies, running dev/build/test/lint, filtering packages, single-test runs, git hooks, preparing a clone (.env.development / .env.test), or Docker-backed local services and dev…
Install Toolchain Commands
$ npx skills add latitude-dev/latitude-llm --skill toolchain-commands -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install latitude-dev/latitude-llm toolchain-commands --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/latitude-dev/latitude-llm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/toolchain-commands .claude/skills/toolchain-commands && 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 "toolchain-commands" agent skill from https://github.com/latitude-dev/latitude-llm/tree/development/.agents/skills/toolchain-commands into .claude/skills/toolchain-commands/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "toolchain-commands", 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/latitude-dev/latitude-llm/tree/development/.agents/skills/toolchain-commandsType 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 latitude-dev/latitude-llm --skill toolchain-commands -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install latitude-dev/latitude-llm toolchain-commands --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/latitude-dev/latitude-llm.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/toolchain-commands .agents/skills/toolchain-commands && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "toolchain-commands" agent skill from https://github.com/latitude-dev/latitude-llm/tree/development/.agents/skills/toolchain-commands into .agents/skills/toolchain-commands/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "toolchain-commands", 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 latitude-dev/latitude-llm --skill toolchain-commands -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install latitude-dev/latitude-llm toolchain-commands --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/latitude-dev/latitude-llm.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/toolchain-commands .cursor/skills/toolchain-commands && 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 "toolchain-commands" agent skill from https://github.com/latitude-dev/latitude-llm/tree/development/.agents/skills/toolchain-commands into .cursor/skills/toolchain-commands/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "toolchain-commands", 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/latitude-dev/latitude-llm.git --path .agents/skills/toolchain-commands--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 latitude-dev/latitude-llm --skill toolchain-commands -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install latitude-dev/latitude-llm toolchain-commands --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/latitude-dev/latitude-llm.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/toolchain-commands .gemini/skills/toolchain-commands && 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 "toolchain-commands" agent skill from https://github.com/latitude-dev/latitude-llm/tree/development/.agents/skills/toolchain-commands into .gemini/skills/toolchain-commands/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "toolchain-commands", 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 latitude-dev/latitude-llm toolchain-commandsInstalls 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 latitude-dev/latitude-llm --skill toolchain-commands -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/latitude-dev/latitude-llm.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/toolchain-commands .github/skills/toolchain-commands && 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 "toolchain-commands" agent skill from https://github.com/latitude-dev/latitude-llm/tree/development/.agents/skills/toolchain-commands into .github/skills/toolchain-commands/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "toolchain-commands", 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 latitude-dev/latitude-llm --skill toolchain-commands -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install latitude-dev/latitude-llm toolchain-commands --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/latitude-dev/latitude-llm.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/toolchain-commands .opencode/skills/toolchain-commands && 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 "toolchain-commands" agent skill from https://github.com/latitude-dev/latitude-llm/tree/development/.agents/skills/toolchain-commands into .opencode/skills/toolchain-commands/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "toolchain-commands", 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
toolchain-commands- GitHub stars
- 4.7k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 483 words
- Files
- 1
- Skills in repo
- 28
- Repo updated
- First seen
- Licence
- MIT
At a glance
Installing dependencies, running dev/build/test/lint, filtering packages, single-test runs, git hooks, preparing a clone (.env.development / .env.test), or Docker-backed local services and dev…
- Tasks that involve Containers
- SKILL.md covers Stack (summary), Top-level commands (repo root), Searching the repo and Git hooks (pre-commit), plus 5 more sections
- Calls pnpm, curl and mise
- Tasks that involve Linting and formatting
What it does
Toolchain Commands is an agent skill from latitude-dev/latitude-llm. Installing dependencies, running dev/build/test/lint, filtering packages, single-test runs, git hooks, preparing a clone (.env.development / .env.test), or Docker-backed local services and dev servers.
Its SKILL.md is about 1.4k 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 DevOps & Cloud, covering Containers and Linting and formatting. It works with Git, Docker, pnpm and TypeScript. The repository describes itself as: Open-source observability for AI agents. Find where your agents fail, dispatch your coding agent to fix it, and verify the fix against real traces. The licence is MIT.
When your agent uses it
- Tasks that involve Containers
- Tasks that involve Linting and formatting
Example prompts
- “/toolchain-commands”
Requirements
- Node.js
- Docker
What it can do on your machine
Read from SKILL.md and the folder at commit 12e8591. 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:
pnpmcurlmisedockervitest
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, curl and docker, which can reach the network depending on how they are called.
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
Toolchain Commands loads about 1.4k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 483 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:3
test runs, git hooks, preparing a clone (.env.development / .env.test), or Docker-backed local services and dev servers. - NoteMentions a .env fileSKILL.md:8
est runs, git hooks, preparing a clone (`.env.development` / `.env.test`), or **Docker-backed local services and dev ser - NoteMentions a .env fileSKILL.md:89
**Before starting work**, ensure `.env.development` and `.env.test` exist. They are required for the dev server, tests, - NoteMentions a .env fileSKILL.md:92
cp .env.example .env.development - NoteMentions a .env fileSKILL.md:93
cp .env.example .env.test - NoteMentions a .env fileSKILL.md:98
- In `.env.development`: `NODE_ENV=development` - NoteMentions a .env fileSKILL.md:99
- In `.env.test`: `NODE_ENV=test` - NoteRuns commands with sudoSKILL.md:108
sudo dockerd &>/dev/null & # if the daemon is not already running - NoteRuns commands with sudoSKILL.md:109
sudo docker compose up -d postgres clickhouse redis redis-bullmq mailpit temporal temporal-ui
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 latitude-dev/latitude-llm at commit 12e8591, republished under its MIT licence (© latitude-dev). 483 words, ~1,418 tokens.
Download SKILL.mdSave it as
.claude/skills/toolchain-commands/SKILL.md (or your agent's skills folder).- name
- toolchain-commands
- description
- Installing dependencies, running dev/build/test/lint, filtering packages, single-test runs, git hooks, preparing a clone (.env.development / .env.test), or Docker-backed local services and dev servers.
Toolchain, commands, and CI
When to use: Installing dependencies, running dev/build/test/lint, filtering packages, single-test runs, git hooks, preparing a clone (.env.development / .env.test), or Docker-backed local services and dev servers.
Stack (summary)
- Runtime: Node.js
25viamise.toml(alsoenginesin rootpackage.json). Usemise install/mise execso Vitest andUint8Array.fromHex/toHexmatch production; Node 22 lacks those APIs and will fail tests that touch@repo/utilscrypto helpers. - Package manager:
package.jsonpackageManagerfield (e.g. pnpm). Install deps:pnpm install - Task runner:
turbovia root scripts - Lint/format: Biome (
@biomejs/biome1.9.x) - TypeScript: 6.0.x + TypeScript 7 beta (
@typescript/native-preview) for typechecking.pnpm typecheckrunstsgo(the native preview binary) — never invoketscdirectly in scripts or docs. - Bundler:
tsdown(replaces the deprecatedtsup). App builds and library DTS emission run undertsdown. - Tests: Vitest 3.x
- Core logic: Effect TS primitives
- Postgres ORM: Drizzle
- API/ingest boundaries: Hono
- Web app: TanStack Start + React
Top-level commands (repo root)
pnpm dev— run all workspacedevtasks via Turbopnpm build— run all workspace buildspnpm check— run all workspace lint and format check scriptspnpm typecheck— run all workspace typecheckspnpm test— run all workspace testspnpm hooks— configure local git hooks for this clone
Searching the repo
grep is a shadowed shell function here, and some sources (e.g. packages/domain/spans/src/otlp/transform.ts) trip binary-file detection because of lone surrogates, which silently suppresses matches. Use command grep -a, or the dedicated search tools, before concluding a string is absent.
Git hooks (pre-commit)
- Pre-commit hook lives at
.husky/pre-commit - Pre-commit runs:
pnpm check,pnpm typecheck, andpnpm knip - Hooks are auto-configured on dependency install via root
preparescript (pnpm hooks) - Existing clones should run
pnpm hooksonce to configurecore.hooksPathand hook permissions
Package-scoped (--filter)
pnpm --filter @app/api check
pnpm --filter @app/api typecheck
pnpm --filter @app/api build
pnpm --filter @app/api testPath-based filtering also works:
pnpm --filter ./apps/api test
pnpm --filter ./packages/domain/workspaces checkSingle-test workflows
Vitest is invoked as vitest run --passWithNoTests:
# Single test file
pnpm --filter @app/api test -- src/some-file.test.ts
# Test name pattern
pnpm --filter @app/api test -- -t "health endpoint"
# Specific file + name
pnpm --filter @app/api test -- src/some-file.test.ts -t "returns 200"Show full SKILL.md (189 more words)Show less
CI-equivalent local checks
Before opening PRs:
pnpm check
pnpm typecheck
pnpm testCI workflows (check.yml, typecheck.yml, knip.yml, test.yml) use Node 25 + pnpm and run the same commands.
Cloud agent environment setup
Before starting work, ensure .env.development and .env.test exist. They are required for the dev server, tests, and tooling like knip.
cp .env.example .env.development
cp .env.example .env.testThen set NODE_ENV appropriately:
- In
.env.development:NODE_ENV=development - In
.env.test:NODE_ENV=test
This provides working defaults for all services (Postgres, ClickHouse, Redis, etc.) that match the Docker Compose setup. For LAT_* naming and parseEnv usage when you add variables, see env-configuration.
Local services (Docker) and dev apps
Start infrastructure before app processes (e.g. in cloud agents or a fresh clone):
sudo dockerd &>/dev/null & # if the daemon is not already running
sudo docker compose up -d postgres clickhouse redis redis-bullmq mailpit temporal temporal-uiMigrations and seeds (only when the user asked you to set up DBs in this conversation — see database-postgres and database-clickhouse-weaviate for agent rules):
pnpm --filter @platform/db-postgres pg:migrate
pnpm --filter @platform/db-clickhouse ch:up
pnpm --filter @platform/db-postgres pg:seed # optional: seed users
pnpm --filter @platform/db-clickhouse ch:seed # optional: sample spansDev servers (e.g. tmux-style):
pnpm --filter @app/web dev &
pnpm --filter @app/api dev &
pnpm --filter @app/ingest dev &
pnpm --filter @app/workers dev &
pnpm --filter @app/workflows dev &
pnpm --filter @app/design-system dev &| Service | Port | Health check |
|---|---|---|
| Web | 3000 | curl http://localhost:3000 (redirect to /login) |
| API | 3001 | curl http://localhost:3001/health |
| Ingest | 3002 | curl http://localhost:3002/health |
| Workers | 9090 | curl http://localhost:9090/health |
| Workflows | 9091 | curl http://localhost:9091/health |
| Design system | 5173 (Vite default) | pnpm --filter @app/design-system dev |
| Mailpit UI | 8025 | curl http://localhost:8025 |
| Temporal UI | 8233 | curl http://localhost:8233 |
Manual auth: magic links appear in Mailpit at http://localhost:8025 after signup at http://localhost:3000/signup.
© latitude-dev, 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/toolchain-commands of latitude-dev/latitude-llm.
Open the folder on GitHubat commit 12e8591
Compare with similar skills
Toolchain Commands 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 |
|---|---|---|---|---|---|---|
| Toolchain Commands this skilllatitude-dev/latitude-llm | 4.7k | — | ~1.4k | Automated safety check: Notes | MIT | |
| Rtk Skillsopaco/deepwiki-rs | 3.1k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Releasear-io/ar-io-node | 127 | — | ~4.2k | Automated safety check: Notes | AGPL-3.0 | |
| Configuration GeneratorArabelaTso/Skills-4-SE | 253 | — | ~2.8k | Automated safety check: Notes | Apache-2.0 | |
| Debug CIweb-infra-dev/rslint | 460 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Devcontainer Devstacklok/toolhive-studio | 170 | — | ~3.8k | Automated safety check: Notes | Apache-2.0 |
Similar skills
Release
ar-io/ar-io-node
Drive the AR.IO Node release process end-to-end — preflight checks, prepare commit, finalize with image SHAs, test docker compose profiles, tag & publish, and post-release cleanup.
Configuration Generator
ArabelaTso/Skills-4-SE
Generate configuration files for applications, services, and infrastructure.
Debug CI
web-infra-dev/rslint
Reproduce Linux CI failures locally using Docker when the same tests pass on the host, especially Go platform differences and VS Code extension tests requiring xvfb.
Devcontainer Dev
stacklok/toolhive-studio
Spin up and interact with ToolHive Studio's containerized dev environment (Xvfb + noVNC + DinD).
Ssh Skill
badseal/ssh-skill
A skill your agent uses when a task requires SSH or SCP/SFTP behavior, a remote server, server alias/IP/hostname/user@host, bastion or jump-host access, remote command execution, upload/download…
More from latitude-dev/latitude-llm
All 28 skills in this repoBetter Auth Best Practices
latitude-dev/latitude-llm
Configure Better Auth server and client, set up database adapters, manage sessions, add plugins, and handle environment variables.
Artifact Designer
latitude-dev/latitude-llm
Create, validate, preview, and publish self-contained HTML artifacts.
CI Watchdog
latitude-dev/latitude-llm
Continuously monitor GitHub PR CI checks and automatically fix failures until all checks pass.
Temporal Developer
latitude-dev/latitude-llm
This skill should be used when the user asks to "create a Temporal workflow", "write a Temporal activity", "debug stuck workflow", "fix non-determinism error", "Temporal Python", "Temporal…
Docs
latitude-dev/latitude-llm
Review the current conversation context and git changes, then persist durable repository knowledge into dev-docs/.md by domain and into AGENTS.md for cross-cutting repo rules.
Managing Maintenance Windows
latitude-dev/latitude-llm
Enables or disables Latitude production maintenance mode by redirecting all publicly exposed production services to the Better Stack status page.
Related
Works with
Categories
Questions about Toolchain Commands
What does Toolchain Commands do?
Installing dependencies, running dev/build/test/lint, filtering packages, single-test runs, git hooks, preparing a clone (.env.development / .env.test), or Docker-backed local services and dev…. Toolchain Commands is an agent skill from latitude-dev/latitude-llm.test), or Docker-backed local services and dev servers.
When should I use Toolchain Commands?
Toolchain Commands fits situations like: tasks that involve Containers; tasks that involve Linting and formatting.
How do I install Toolchain Commands in Claude Code?
Run `npx skills add latitude-dev/latitude-llm --skill toolchain-commands -a claude-code`. Or copy the skill folder (.agents/skills/toolchain-commands in latitude-dev/latitude-llm) into .claude/skills/toolchain-commands in your project. Claude Code loads it when a task matches its description.
How do I install Toolchain Commands in Codex?
Run `npx skills add latitude-dev/latitude-llm --skill toolchain-commands -a codex`. Or copy the skill folder (.agents/skills/toolchain-commands in latitude-dev/latitude-llm) into .agents/skills/toolchain-commands in your project. Codex loads it when a task matches its description.
Can I use Toolchain Commands 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 latitude-dev/latitude-llm --skill toolchain-commands -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/toolchain-commands, .gemini/skills/toolchain-commands, .github/skills/toolchain-commands and .opencode/skills/toolchain-commands in your project.
What does Toolchain Commands need to run?
Going by SKILL.md and its folder, Toolchain Commands needs the command-line tools its instructions call (pnpm, curl, mise, docker and vitest). Our summary lists: Node.js; Docker.
Does Toolchain Commands access the network?
SKILL.md contains no URLs. Its commands use curl and docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Toolchain Commands safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file; runs commands with sudo), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Toolchain Commands use?
Toolchain Commands 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 Toolchain Commands use?
About 1.4k tokens (SKILL.md is roughly 5.7k 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 Toolchain Commands?
Skills that share tags, products or a category with Toolchain Commands: Rtk Skill (sopaco/deepwiki-rs, 3.1k stars), Release (ar-io/ar-io-node, 127 stars), Configuration Generator (ArabelaTso/Skills-4-SE, 253 stars) and Debug CI (web-infra-dev/rslint, 460 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Toolchain Commands?
latitude-dev (a GitHub organization) maintains it in latitude-dev/latitude-llm, which has 4,714 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 7, 2026.
Source: latitude-dev/latitude-llm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.