mcp-cli-scripts
Build CLI scripts alongside MCP servers for terminal environments. File I/O, batch processing, caching, richer output formats. Templates for TypeScript scripts and SCRIPTS.md. Use when: MCP companion scripts, batch processing, saving results to files, CLI API wrappers. Troubleshoot: context too large, no file access, batch input.
Install with Tessl CLI
npx tessl i github:jezweb/claude-skills --skill mcp-cli-scripts90
Does it follow best practices?
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its purpose (CLI scripts alongside MCP servers), lists specific capabilities (file I/O, batch processing, caching), and provides explicit trigger guidance with a 'Use when:' clause. The inclusion of troubleshooting scenarios adds valuable context for skill selection. Uses appropriate third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Build CLI scripts alongside MCP servers', 'File I/O', 'batch processing', 'caching', 'richer output formats', and mentions specific deliverables like 'Templates for TypeScript scripts and SCRIPTS.md'. | 3 / 3 |
Completeness | Clearly answers both what (build CLI scripts, file I/O, batch processing, templates) and when with explicit 'Use when:' clause listing specific scenarios like 'MCP companion scripts', 'batch processing', 'saving results to files', plus troubleshooting triggers. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'CLI scripts', 'MCP servers', 'batch processing', 'File I/O', 'caching', 'CLI API wrappers', 'TypeScript scripts'. Also includes troubleshooting triggers like 'context too large', 'no file access', 'batch input'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on CLI scripts specifically as MCP server companions for terminal environments. The combination of 'MCP companion scripts', 'CLI API wrappers', and troubleshooting scenarios creates a distinct trigger profile unlikely to conflict with general coding or MCP server skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with strong actionability and clear workflows. The main weakness is some verbosity in explanatory sections that Claude doesn't need (like explaining why CLI scripts are useful alongside MCP). The concrete examples, templates, and checklist make this highly usable.
Suggestions
Condense the 'Why CLI Scripts' comparison table - Claude understands these tradeoffs; a 2-line summary would suffice
Remove duplicate package.json version snippets (appears twice with identical content)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary explanation (e.g., the comparison table could be more compact, and some sections like 'Why CLI Scripts' explain concepts Claude likely understands). The repeated package.json snippets and version information add redundancy. | 2 / 3 |
Actionability | Provides concrete, executable guidance throughout: specific shebang syntax, copy-paste ready commands, complete directory structures, and clear code examples. The templates section gives exact file paths and commands to use. | 3 / 3 |
Workflow Clarity | The complete setup checklist at the end provides a clear sequence with validation steps (test script, verify JSON output). The 'Critical Rules' section with Always Do/Never Do provides clear guardrails. The workflow for creating scripts is unambiguous. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections, references to external templates and rules files, and appropriate use of bundled resources. The skill points to templates/ and rules/ directories for detailed content rather than inlining everything. Navigation is straightforward. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.