Agent Skills
› NeverSight/learn-skills.dev
› tooling-engineer
tooling-engineer
GitHub专注于构建开发者工具，包括CLI、IDE插件、构建优化及环境自动化。旨在提升开发效率与体验，涵盖代码生成、静态分析及任务自动化等场景，不用于CI/CD或生产应用开发。
Trigger Scenarios
构建命令行工具
创建IDE扩展
优化构建系统
自动化开发任务
设置本地开发环境
Install
npx skills add NeverSight/learn-skills.dev --skill tooling-engineer -g -y
SKILL.md
Frontmatter
{
"name": "tooling-engineer",
"description": "Expert in building developer tools, CLI utilities, IDE extensions, and optimizing local development environments."
}
Tooling Engineer
Purpose
Provides expertise in building developer productivity tools including command-line interfaces, IDE extensions, build system optimizations, and local development environment automation. Focuses on improving developer experience and workflow efficiency.
When to Use
- Building command-line tools and utilities
- Creating IDE/editor extensions (VS Code, JetBrains)
- Optimizing build systems and compilation times
- Automating repetitive development tasks
- Setting up local development environments
- Creating code generators and scaffolding tools
- Building linters, formatters, and static analysis tools
- Improving developer onboarding experience
Quick Start
Invoke this skill when:
- Building command-line tools and utilities
- Creating IDE/editor extensions (VS Code, JetBrains)
- Optimizing build systems and compilation times
- Automating repetitive development tasks
- Setting up local development environments
Do NOT invoke when:
- Building CI/CD pipelines → use devops-engineer
- Creating production applications → use appropriate developer skill
- Writing shell scripts for ops → use appropriate PowerShell/Bash skill
- Building MCP servers → use mcp-developer
Decision Framework
Developer Tool Need?
├── Command Line → CLI with argument parsing + subcommands
├── IDE Integration → Extension/plugin for target IDE
├── Build Optimization → Caching, parallelization, incremental builds
├── Code Generation → Templates + AST manipulation
├── Environment Setup → Container or script-based provisioning
└── Automation → Task runner or custom tooling
Core Workflows
1. CLI Tool Development
- Define command structure and argument schema
- Choose CLI framework (Commander, Click, Cobra, etc.)
- Implement core functionality with clear separation
- Add help text and usage examples
- Implement configuration file support
- Add shell completion scripts
- Package for distribution (npm, pip, brew, etc.)
- Write documentation with common use cases
2. IDE Extension Development
- Identify target IDE and extension API
- Define extension capabilities and triggers
- Scaffold extension project structure
- Implement core features (commands, providers, views)
- Add configuration options
- Test across different editor states
- Publish to extension marketplace
- Gather feedback and iterate
3. Build System Optimization
- Profile current build to identify bottlenecks
- Implement caching for expensive operations
- Enable parallel execution where possible
- Set up incremental builds for common changes
- Add build metrics and monitoring
- Document build system for team
- Measure improvement and iterate
Best Practices
- Design CLIs with Unix philosophy (composable, focused)
- Provide sensible defaults with override options
- Include verbose/debug modes for troubleshooting
- Make tools work offline when possible
- Fail fast with clear error messages
- Version tools and maintain backwards compatibility
Anti-Patterns
- Feature creep → Keep tools focused on one job
- Silent failures → Always report errors clearly
- No configuration → Allow customization for different needs
- Manual installation → Provide package manager distribution
- Poor error messages → Include context and suggested fixes
Version History
- e0220ca Current 2026-07-05 21:18
