terminal-integration-specialist
Terminal emulation, text rendering optimization, and SwiftTerm integration for modern Swift applications
35
20%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./spatial-terminal-integration/skills/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a reasonably specific domain (SwiftTerm and terminal emulation in Swift) but reads more like a topic label than an actionable skill description. It lacks concrete actions, explicit trigger guidance ('Use when...'), and natural keyword variations that would help Claude reliably select this skill from a large pool.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user is building a terminal emulator in Swift, integrating SwiftTerm, or working with PTY/console rendering in a macOS/iOS app.'
List specific concrete actions such as 'configure SwiftTerm terminal views, handle escape sequences, optimize text rendering performance, manage PTY connections'.
Include natural keyword variations users might say: 'terminal app', 'console view', 'xterm', 'PTY', 'macOS terminal', 'iOS terminal emulator'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (terminal emulation, SwiftTerm) and some general actions (text rendering optimization, integration), but doesn't list specific concrete actions like 'parse escape sequences', 'render terminal output', or 'configure terminal sessions'. | 2 / 3 |
Completeness | Describes a rough 'what' (terminal emulation and SwiftTerm integration) but completely lacks any 'when should Claude use it' clause or explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' itself is weak enough to warrant a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'SwiftTerm', 'terminal emulation', and 'Swift applications' that users might mention, but misses common variations like 'terminal app', 'console', 'xterm', 'PTY', or 'command line interface in Swift'. | 2 / 3 |
Distinctiveness Conflict Risk | SwiftTerm is a fairly specific library which helps distinguish it, but 'terminal emulation' and 'text rendering optimization' are broad enough to potentially overlap with general Swift UI skills or other terminal-related skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads as a persona description or capability statement rather than an actionable skill file. It lists topics and areas of expertise but provides no concrete code examples, no step-by-step workflows, and no specific instructions that would help Claude perform terminal integration tasks. Nearly every token is spent describing what the skill covers rather than teaching how to do it.
Suggestions
Replace the descriptive bullet lists with concrete, executable SwiftUI/SwiftTerm code examples showing how to embed a terminal view, handle input, and connect SSH streams.
Add step-by-step workflows for common tasks like 'Setting up SwiftTerm in a SwiftUI app' or 'Connecting an SSH session to a terminal view' with validation checkpoints.
Remove self-referential capability descriptions ('Complete mastery of...', 'Deep understanding of...') and replace them with specific API patterns, gotchas, and solutions Claude wouldn't already know.
Create separate reference files for detailed topics (e.g., SWIFTTERM_SETUP.md, SSH_BRIDGING.md) and link to them from a concise overview in the main skill file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is almost entirely descriptive bullet points explaining concepts and domains Claude already knows. It reads like a resume or capability statement rather than actionable instructions. Phrases like 'Complete mastery of SwiftTerm's public API' and 'Deep understanding of terminal protocol specifications' are self-descriptions that waste tokens. | 1 / 3 |
Actionability | There is zero executable code, no concrete commands, no specific API calls, no examples of SwiftTerm usage, and no copy-paste ready snippets. The entire skill describes what the agent should know rather than providing concrete guidance on how to do anything. | 1 / 3 |
Workflow Clarity | There are no workflows, no step-by-step processes, no validation checkpoints, and no sequenced instructions. The content is purely declarative lists of topics without any procedural guidance for accomplishing tasks. | 1 / 3 |
Progressive Disclosure | The content has clear section headers and some external documentation references at the bottom, which is useful. However, the sections themselves are all at the same level of abstraction (shallow bullet lists) with no deeper reference files for detailed implementation guidance. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- OpenRoster-ai/awesome-openroster
- Commit
09aef5d
- 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.