Technical Analyst
tradermonty/claude-trading-skills
This skill should be used when analyzing weekly price charts for stocks, stock indices, cryptocurrencies, or forex pairs.
Analyze coverage of the vscode-extension's tool-family definitions (DEFAULTTOOLFAMILIES in vscode-extension/src/toolFamilies.ts) against the canonical tool-name list in src/toolNames.json and/or a…
Install Improve Tool Families
$ npx skills add rajbos/ai-engineering-fluency --skill improve-tool-families -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rajbos/ai-engineering-fluency improve-tool-families --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/rajbos/ai-engineering-fluency.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/improve-tool-families .claude/skills/improve-tool-families && 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 "improve-tool-families" agent skill from https://github.com/rajbos/ai-engineering-fluency/tree/main/.claude/skills/improve-tool-families into .claude/skills/improve-tool-families/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "improve-tool-families", 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/rajbos/ai-engineering-fluency/tree/main/.claude/skills/improve-tool-familiesType 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 rajbos/ai-engineering-fluency --skill improve-tool-families -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rajbos/ai-engineering-fluency improve-tool-families --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rajbos/ai-engineering-fluency.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/improve-tool-families .agents/skills/improve-tool-families && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "improve-tool-families" agent skill from https://github.com/rajbos/ai-engineering-fluency/tree/main/.claude/skills/improve-tool-families into .agents/skills/improve-tool-families/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "improve-tool-families", 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 rajbos/ai-engineering-fluency --skill improve-tool-families -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rajbos/ai-engineering-fluency improve-tool-families --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rajbos/ai-engineering-fluency.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/improve-tool-families .cursor/skills/improve-tool-families && 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 "improve-tool-families" agent skill from https://github.com/rajbos/ai-engineering-fluency/tree/main/.claude/skills/improve-tool-families into .cursor/skills/improve-tool-families/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "improve-tool-families", 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/rajbos/ai-engineering-fluency.git --path .claude/skills/improve-tool-families--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 rajbos/ai-engineering-fluency --skill improve-tool-families -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rajbos/ai-engineering-fluency improve-tool-families --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rajbos/ai-engineering-fluency.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/improve-tool-families .gemini/skills/improve-tool-families && 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 "improve-tool-families" agent skill from https://github.com/rajbos/ai-engineering-fluency/tree/main/.claude/skills/improve-tool-families into .gemini/skills/improve-tool-families/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "improve-tool-families", 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 rajbos/ai-engineering-fluency improve-tool-familiesInstalls 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 rajbos/ai-engineering-fluency --skill improve-tool-families -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rajbos/ai-engineering-fluency.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/improve-tool-families .github/skills/improve-tool-families && 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 "improve-tool-families" agent skill from https://github.com/rajbos/ai-engineering-fluency/tree/main/.claude/skills/improve-tool-families into .github/skills/improve-tool-families/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "improve-tool-families", 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 rajbos/ai-engineering-fluency --skill improve-tool-families -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rajbos/ai-engineering-fluency improve-tool-families --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rajbos/ai-engineering-fluency.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/improve-tool-families .opencode/skills/improve-tool-families && 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 "improve-tool-families" agent skill from https://github.com/rajbos/ai-engineering-fluency/tree/main/.claude/skills/improve-tool-families into .opencode/skills/improve-tool-families/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "improve-tool-families", 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
improve-tool-families- GitHub stars
- 118
- Token cost
- ~1.3k tokens
- SKILL.md length
- 501 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- MIT
At a glance
Analyze coverage of the vscode-extension's tool-family definitions (DEFAULTTOOLFAMILIES in vscode-extension/src/toolFamilies.ts) against the canonical tool-name list in src/toolNames.json and/or a…
- Works in 4 steps: Loads the canonical set of known tool… → Parses DEFAULT_TOOL_FAMILIES out of… → Reports which candidate tool names are… → …
- The Tool Output Token Analysis tab shows too many tools bucketed under Other Tools
- SKILL.md covers What the script does, Usage, Workflow: applying the… and Related files
- Calls node and npm
What it does
Improve Tool Families is an agent skill from rajbos/ai-engineering-fluency. Analyze coverage of the vscode-extension's tool-family definitions (DEFAULTTOOLFAMILIES in vscode-extension/src/toolFamilies.ts) against the canonical tool-name list in src/toolNames.json and/or a live agent tool list, and suggest which family missing tool names likely belong to. Use when the Tool Output Token Analysis tab shows too many tools bucketed under "Other Tools", after adding a new editor adapter, after a new agent/CLI's tool list grows, or when asked to improve/expand the preconfigured tool families.
Its SKILL.md is about 1.3k 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 Business, Finance & HR, covering Crypto and DeFi analysis. It works with Visual Studio Code. The repository describes itself as: Extension that shows information about the estimated token usage and more of AI in editors/CLI's. The licence is MIT.
When your agent uses it
- The Tool Output Token Analysis tab shows too many tools bucketed under Other Tools
- After adding a new editor adapter
- After a new agent/CLIs tool list grows
- Asked to improve/expand the preconfigured tool families
Example prompts
- “Other Tools”
- “/improve-tool-families”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Loads the canonical set of known tool names from src/toolNames.json
- Parses DEFAULT_TOOL_FAMILIES out of vscode-extension/src/toolFamilies.ts
- Reports which candidate tool names are not yet covered by any
- Suggests a likely family for each uncovered name using keyword
What it can do on your machine
Read from SKILL.md and the folder at commit d51325f. 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:
nodenpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, 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
Improve Tool Families loads about 1.3k tokens when it runs. Until then it costs about 135 tokens; SKILL.md has 501 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 rajbos/ai-engineering-fluency at commit d51325f, republished under its MIT licence (© rajbos). 501 words, ~1,298 tokens.
Download SKILL.mdSave it as
.claude/skills/improve-tool-families/SKILL.md (or your agent's skills folder).- name
- improve-tool-families
- description
- Analyze coverage of the vscode-extension's tool-family definitions (DEFAULT_TOOL_FAMILIES in vscode-extension/src/toolFamilies.ts) against the canonical tool-name list in src/toolNames.json and/or a live agent tool list, and suggest which family missing tool names likely belong to. Use when the Tool Output Token Analysis tab shows too many tools bucketed under "Other Tools", after adding a new editor adapter, after a new agent/CLI's tool list grows, or when asked to improve/expand the preconfigured tool families.
Improve Tool Families Skill
The "Tool Output Token Analysis" tab in the VS Code extension groups tool
calls into families (File Reading, File Writing, Search & Discovery,
Shell / Terminal, Code Intelligence, Web & Research, ...) so a "built-in"
tool's token efficiency can be compared against "alternative" tools that do
the same job. That grouping comes from DEFAULT_TOOL_FAMILIES in
vscode-extension/src/toolFamilies.ts, merged with any user overrides in the
aiEngineeringFluency.toolFamilies VS Code setting.
The matching is an exact string match against the raw tool name recorded
per editor (see src/adapters/*.ts and usageAnalysis.ts writing into
toolCalls.byTool/outputTokensByTool) — there is no cross-editor
normalization step first. That means every spelling a different editor/agent
uses for "read a file", "run a shell command", "search text", etc. must be
listed explicitly, or it silently falls into the generic "Other Tools"
bucket instead of being compared.
What the script does
analyze-tool-families.js:
- Loads the canonical set of known tool names from
src/toolNames.json(the cross-editor tool-name → friendly-name map used elsewhere in the repo) and/or an ad-hoc list passed via--tools. - Parses
DEFAULT_TOOL_FAMILIESout ofvscode-extension/src/toolFamilies.ts(no build step needed). - Reports which candidate tool names are not yet covered by any
family's
builtIn/alternativesarrays. - Suggests a likely family for each uncovered name using keyword
heuristics (e.g. names containing
read/view→reading,grep/glob/search→search,run/terminal/bash→shell,web/fetch→web, etc.).
It does not edit toolFamilies.ts automatically — deciding whether a
tool is a plain "builtIn" (baseline) tool or a more token-efficient
"alternative" is a judgment call that needs a human/agent to review the
tool's actual behavior, not just its name.
Usage
# Compare against every name in src/toolNames.json
node .github/skills/improve-tool-families/analyze-tool-families.js
# Also check specific tool names (e.g. the current agent session's own tool list)
node .github/skills/improve-tool-families/analyze-tool-families.js --tools view,edit,grep,glob,powershell,web_fetch,ask_user
# Machine-readable JSON (for further processing)
node .github/skills/improve-tool-families/analyze-tool-families.js --jsonOptions
| Flag | Meaning |
|---|---|
--tools=a,b,c | Additional comma-separated tool names to check for coverage (e.g. this session's own live tool list) |
--json | Emit JSON only |
--help | Print this file |
Exit codes
0— ran successfully (report may still list uncovered tools)2— configuration / environment error (source files not found or unparsable)
Show full SKILL.md (198 more words)Show less
Workflow: applying the suggestions
- Run the script (optionally with
--toolsset to your current tool list — in an agent session this is just the list of tools you have available). - For each suggested family, look at the listed tool names and decide:
- Is it just another editor's spelling of an existing baseline tool
(e.g.
Read,read_filevs.read/view) → add tobuiltIn. - Is it a genuinely more targeted/efficient tool for the same job
(e.g.
apply_patch,replace_string_in_file,multi_editvs. a full file rewrite) → add toalternatives. - Is it not actually comparable (e.g. issue/PR/notebook management
tools, orchestration tools like
task/write_agent) → leave it out; not every tool needs a family.
- Is it just another editor's spelling of an existing baseline tool
(e.g.
- Edit
vscode-extension/src/toolFamilies.ts(DEFAULT_TOOL_FAMILIES). - Verify with
cd vscode-extension && npm run validate(tsc + eslint + esbuild). - Re-run this script to confirm the previously-uncovered names are now covered.
Related files
vscode-extension/src/toolFamilies.ts—DEFAULT_TOOL_FAMILIES,mergeToolFamilies,getToolFamilies(source of truth for family data)vscode-extension/package.json— JSON schema for theaiEngineeringFluency.toolFamiliesoverride settingvscode-extension/src/webview/diagnostics/main.ts—renderToolAnalysisTab/renderToolFamilySection(exact-match rendering logic; anything not claimed by a family lands in "Other Tools")src/toolNames.json— canonical cross-editor tool-name → friendly-name map, the best available source of real-world tool name spellingssrc/adapters/*.ts,src/usageAnalysis.ts— where raw tool names are recorded intotoolCalls.byTool/outputTokensByToolper editor
© rajbos, 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 .claude/skills/improve-tool-families of rajbos/ai-engineering-fluency.
Open the folder on GitHubat commit d51325f
Compare with similar skills
Improve Tool Families 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 |
|---|---|---|---|---|---|---|
| Improve Tool Families this skillrajbos/ai-engineering-fluency | 118 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Technical Analysttradermonty/claude-trading-skills | 3k | 4 repos | ~4.6k | Automated safety check: Pass | MIT | |
| Polyclawchainstacklabs/polyclaw | 359 | 1 repos | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Longbridge Researchhelsome/folio | 271 | 3 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Stock Analysis24mlight/StockClaw | 101 | 2 repos | ~2k | Automated safety check: Notes | MIT | |
| Swapper Depositswapperfinance/swapper-toolkit | 852 | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
Polyclaw
chainstacklabs/polyclaw
Trade on Polymarket via split + CLOB execution. An agent skill from chainstacklabs/polyclaw.
Longbridge Research
helsome/folio
Institution ratings, consensus price targets, EPS/revenue forecasts, finance calendar, shareholder data, fund holders, insider trades (SEC Form 4), short interest, industry rankings, peer group…
Stock Analysis
24mlight/StockClaw
Analyze stocks and cryptocurrencies using Yahoo Finance data.
Swapper Deposit
swapperfinance/swapper-toolkit
Deposit and bridge funds into a wallet or protocol using Swapper Finance.
Okx Cex Earn
okx/agent-skills
Manages OKX Simple Earn (flexible savings/lending), Flash Earn, On-chain Earn (staking/DeFi), Dual Investment (DCD/双币赢), and AutoEarn (自动赚币) via the okx CLI.
More from rajbos/ai-engineering-fluency
All 21 skills in this repoCheck Urls
rajbos/ai-engineering-fluency
Find all hardcoded URLs in TypeScript source files and verify they resolve (return HTTP 2xx/3xx).
Create Issue
rajbos/ai-engineering-fluency
Create a well-scoped GitHub issue in this repo. An agent skill from rajbos/ai-engineering-fluency.
Deduplicate Code
rajbos/ai-engineering-fluency
Detect copy-pasted code blocks across the shared source (vscode-extension/src, the repo-root src/, cli/src) with the dependency-free check-code-duplication.js detector, then pick one duplicate group…
Load Cache Data
rajbos/ai-engineering-fluency
Load and display the last 10 cache entries as raw JSON output.
PR Risk Review
rajbos/ai-engineering-fluency
Assess the risk of a changeset (a PR, a branch, or the working tree) and classify it as low, medium, or high with a written rationale.
Session Log Data
rajbos/ai-engineering-fluency
Describes the data files available in the coding agent environment after copilot-setup-steps runs.
Related
Works with
Categories
Questions about Improve Tool Families
What does Improve Tool Families do?
Analyze coverage of the vscode-extension's tool-family definitions (DEFAULTTOOLFAMILIES in vscode-extension/src/toolFamilies.ts) against the canonical tool-name list in src/toolNames.json and/or a…. Improve Tool Families is an agent skill from rajbos/ai-engineering-fluency.json and/or a live agent tool list, and suggest which family missing tool names likely belong to.
When should I use Improve Tool Families?
Improve Tool Families fits situations like: the Tool Output Token Analysis tab shows too many tools bucketed under Other Tools; after adding a new editor adapter; after a new agent/CLIs tool list grows; asked to improve/expand the preconfigured tool families.
How do I install Improve Tool Families in Claude Code?
Run `npx skills add rajbos/ai-engineering-fluency --skill improve-tool-families -a claude-code`. Or copy the skill folder (.claude/skills/improve-tool-families in rajbos/ai-engineering-fluency) into .claude/skills/improve-tool-families in your project. Claude Code loads it when a task matches its description.
How do I install Improve Tool Families in Codex?
Run `npx skills add rajbos/ai-engineering-fluency --skill improve-tool-families -a codex`. Or copy the skill folder (.claude/skills/improve-tool-families in rajbos/ai-engineering-fluency) into .agents/skills/improve-tool-families in your project. Codex loads it when a task matches its description.
Can I use Improve Tool Families 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 rajbos/ai-engineering-fluency --skill improve-tool-families -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/improve-tool-families, .gemini/skills/improve-tool-families, .github/skills/improve-tool-families and .opencode/skills/improve-tool-families in your project.
What does Improve Tool Families need to run?
Going by SKILL.md and its folder, Improve Tool Families needs the command-line tools its instructions call (node and npm).
Does Improve Tool Families access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Improve Tool Families 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 Improve Tool Families use?
Improve Tool Families 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 Improve Tool Families use?
About 1.3k tokens (SKILL.md is roughly 5.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 Improve Tool Families?
Skills that share tags, products or a category with Improve Tool Families: Technical Analyst (tradermonty/claude-trading-skills, 3k stars), Polyclaw (chainstacklabs/polyclaw, 359 stars), Longbridge Research (helsome/folio, 271 stars) and Stock Analysis (24mlight/StockClaw, 101 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Improve Tool Families?
rajbos (a GitHub user) maintains it in rajbos/ai-engineering-fluency, which has 118 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 11, 2026.
Source: rajbos/ai-engineering-fluency on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.