TS SDK Author
mindfold-ai/Trellis
Design, build, verify, and publish production-grade TypeScript SDKs as npm packages inside a pnpm monorepo.
Tooling conventions for repositories on the eserstack toolchain: pnpm installs and Deno runs, package.json over generated deno.json, JSR over npm, workspace dependencies, vetting new dependencies…
Custom licenceAuto-check passed
Install Tooling Standards
$ npx skills add eser/stack --skill tooling-standards -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install eser/stack tooling-standards --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/eser/stack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/tooling-standards .claude/skills/tooling-standards && 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 "tooling-standards" agent skill from https://github.com/eser/stack/tree/main/.agents/skills/tooling-standards into .claude/skills/tooling-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tooling-standards", 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/eser/stack/tree/main/.agents/skills/tooling-standardsType 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 eser/stack --skill tooling-standards -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install eser/stack tooling-standards --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eser/stack.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/tooling-standards .agents/skills/tooling-standards && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "tooling-standards" agent skill from https://github.com/eser/stack/tree/main/.agents/skills/tooling-standards into .agents/skills/tooling-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tooling-standards", 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 eser/stack --skill tooling-standards -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install eser/stack tooling-standards --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eser/stack.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/tooling-standards .cursor/skills/tooling-standards && 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 "tooling-standards" agent skill from https://github.com/eser/stack/tree/main/.agents/skills/tooling-standards into .cursor/skills/tooling-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tooling-standards", 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/eser/stack.git --path .agents/skills/tooling-standards--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 eser/stack --skill tooling-standards -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install eser/stack tooling-standards --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eser/stack.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/tooling-standards .gemini/skills/tooling-standards && 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 "tooling-standards" agent skill from https://github.com/eser/stack/tree/main/.agents/skills/tooling-standards into .gemini/skills/tooling-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tooling-standards", 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 eser/stack tooling-standardsInstalls 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 eser/stack --skill tooling-standards -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/eser/stack.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/tooling-standards .github/skills/tooling-standards && 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 "tooling-standards" agent skill from https://github.com/eser/stack/tree/main/.agents/skills/tooling-standards into .github/skills/tooling-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tooling-standards", 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 eser/stack --skill tooling-standards -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install eser/stack tooling-standards --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eser/stack.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/tooling-standards .opencode/skills/tooling-standards && 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 "tooling-standards" agent skill from https://github.com/eser/stack/tree/main/.agents/skills/tooling-standards into .opencode/skills/tooling-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tooling-standards", 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
tooling-standards- GitHub stars
- 128
- Token cost
- ~527 tokens
- SKILL.md length
- 172 words
- Files
- 5 (incl. references)
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Tooling conventions for repositories on the eserstack toolchain: pnpm installs and Deno runs, package.json over generated deno.json, JSR over npm, workspace dependencies, vetting new dependencies…
- Adding a dependency
- SKILL.md covers Always and References
- Calls deno
- Project command
What it does
Tooling Standards is an agent skill from eser/stack. Tooling conventions for repositories on the eserstack toolchain: pnpm installs and Deno runs, package.json over generated deno.json, JSR over npm, workspace dependencies, vetting new dependencies, manifest scripts, editor settings, file naming, license headers, adding a workspace package. Use when adding a dependency, package or project command, editing package config, or naming or creating files.
Its SKILL.md is about 530 tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `evals/triggers.json`, `references/deno-and-packages.md` and `references/repo-conventions.md`).
It works with npm, Deno and pnpm. The repository describes itself as: The Portability Solution for Your Code! 🚀 Powered By Deno and JavaScript.
When your agent uses it
- Adding a dependency
- Project command
- Editing package config
Example prompts
- “/tooling-standards”
Requirements
- Node.js
What it can do on your machine
Read from SKILL.md and the folder at commit 64939e6. 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:
deno
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
Tooling Standards loads about 527 tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 105 tokens; SKILL.md has 172 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 172 words (~527 tokens).
“Tools, configuration files, dependencies and repository conventions shared by every repository on the eserstack toolchain. Repository-specific facts (paths, generators, command list) are in AGENTS.md.”
- name
- tooling-standards
Files
SKILL.md and 4 other files (references) in .agents/skills/tooling-standards of eser/stack.
- SKILL.md
- evals/triggers.json
- references/deno-and-packages.md
- references/repo-conventions.md
- references/scripts-and-editor.md
Open the folder on GitHubat commit 64939e6
Compare with similar skills
Tooling Standards 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 |
|---|---|---|---|---|---|---|
| Tooling Standards this skilleser/stack | 128 | — | ~527 | Automated safety check: Pass | Custom licence | |
| TS SDK Authormindfold-ai/Trellis | 15k | — | ~6.1k | Automated safety check: Pass | MIT | |
| npm Supply Chain Securitybodadotsh/npm-security-best-practices | 859 | — | ~1k | Automated safety check: Warn | MIT | |
| Migrate to Denodenoland/skills | 100 | — | ~2.2k | Automated safety check: Warn | MIT | |
| Swpm Manage Commands Argsdeinsoftware/swpm | 125 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Link Workspace Packagesnomcopter/react-mosaic | 4.8k | 6 repos | ~760 | Automated safety check: Pass | Custom licence |
Similar skills
npm Supply Chain Security
bodadotsh/npm-security-best-practices
Applies safer package manager defaults and dependency vetting to JavaScript and TypeScript projects to reduce supply-chain attack risk.
- Official
Migrate to Deno
denoland/skills
Moves a Node.js, npm, Yarn, pnpm or Bun project to Deno in reversible steps, starting with Deno as the package manager and changing no code unless needed.
Swpm Manage Commands Args
deinsoftware/swpm
Manage cmds and args props in SWPM package manager configs (src/packages/managers/.ts), including adding, modifying or removing command and argument mappings across npm, yarn, pnpm, bun, deno.
Link Workspace Packages
nomcopter/react-mosaic
Link workspace packages in monorepos (npm, yarn, pnpm, bun).
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
More from eser/stack
All 13 skills in this repoEser Rules Manager
eser/stack
Picks the skills a task needs and maintains the rules in .agents/skills.
Architecture Guidelines
eser/stack
System design in eserstack: double-layered hexagonal architecture, explicit adapter composition, public API and CLI surface, request metadata, testing strategy, ADRs.
Coding Practices
eser/stack
Language-neutral code quality rules for eserstack, TypeScript and Go.
Enrichment
eser/stack
Interviews the user about a plan, decision or idea in rounds, level by level down a decision tree, until both share one understanding; facts are researched by sub-agents, decisions stay with the user.
Go Practices
eser/stack
Go conventions for eserstack's ajan framework, services and FFI bridge.
Javascript Practices
eser/stack
TS and JS conventions for eserstack packages: namespace imports, mod.ts entries, cross-runtime APIs, explicit checks, async, tests and laroux React components.
Related
Questions about Tooling Standards
What does Tooling Standards do?
Tooling conventions for repositories on the eserstack toolchain: pnpm installs and Deno runs, package.json over generated deno.json, JSR over npm, workspace dependencies, vetting new dependencies…. Tooling Standards is an agent skill from eser/stack.json, JSR over npm, workspace dependencies, vetting new dependencies, manifest scripts, editor settings, file naming, license headers, adding a workspace package.
When should I use Tooling Standards?
Tooling Standards fits situations like: adding a dependency; project command; editing package config.
How do I install Tooling Standards in Claude Code?
Run `npx skills add eser/stack --skill tooling-standards -a claude-code`. Or copy the skill folder (.agents/skills/tooling-standards in eser/stack) into .claude/skills/tooling-standards in your project. Claude Code loads it when a task matches its description.
How do I install Tooling Standards in Codex?
Run `npx skills add eser/stack --skill tooling-standards -a codex`. Or copy the skill folder (.agents/skills/tooling-standards in eser/stack) into .agents/skills/tooling-standards in your project. Codex loads it when a task matches its description.
Can I use Tooling Standards 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 eser/stack --skill tooling-standards -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tooling-standards, .gemini/skills/tooling-standards, .github/skills/tooling-standards and .opencode/skills/tooling-standards in your project.
What does Tooling Standards need to run?
Going by SKILL.md and its folder, Tooling Standards needs the command-line tools its instructions call (deno). Our summary lists: Node.js.
Does Tooling Standards 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 Tooling Standards 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 Tooling Standards use?
Tooling Standards 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 Tooling Standards use?
About 527 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2k tokens, read only when the agent opens those files.
What are the alternatives to Tooling Standards?
Skills that share tags, products or a category with Tooling Standards: TS SDK Author (mindfold-ai/Trellis, 15k stars), npm Supply Chain Security (bodadotsh/npm-security-best-practices, 859 stars), Migrate to Deno (denoland/skills, 100 stars) and Swpm Manage Commands Args (deinsoftware/swpm, 125 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Tooling Standards?
eser (a GitHub user) maintains it in eser/stack, which has 128 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 3, 2026.
Source: eser/stack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.