terminal-integration-specialist
Provides concrete guidance on building terminal emulators in Swift using SwiftTerm, including configuring terminal views, parsing ANSI/VT100 escape sequences, managing PTY connections, and optimizing text rendering performance. Use when the user is building a terminal app, console view, or xterm-compatible emulator in Swift, integrating SwiftTerm into a SwiftUI or UIKit/AppKit app, working with PTY or SSH stream bridging, handling keyboard input and escape sequences, or optimizing terminal rendering on macOS, iOS, or visionOS.
96
96%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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 an excellent skill description that hits all the marks. It provides highly specific technical capabilities, comprehensive trigger terms covering the full range of user queries, explicit 'Use when' guidance with multiple scenarios, and occupies a very distinct niche that minimizes conflict risk. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: configuring terminal views, parsing ANSI/VT100 escape sequences, managing PTY connections, and optimizing text rendering performance. These are highly specific technical capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (building terminal emulators in Swift with specific capabilities) and 'when' with an explicit 'Use when...' clause listing five distinct trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a user would use: 'terminal emulator', 'SwiftTerm', 'ANSI/VT100', 'PTY', 'SSH stream', 'escape sequences', 'terminal app', 'console view', 'xterm-compatible', 'SwiftUI', 'UIKit/AppKit', 'macOS', 'iOS', 'visionOS'. These are the exact terms developers would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Extremely niche and distinctive — the combination of Swift, SwiftTerm, terminal emulation, PTY connections, and ANSI escape sequences creates a very clear, narrow domain that is unlikely to conflict with any other skill. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that provides concrete, executable guidance for SwiftTerm integration across multiple use cases. Its strengths are excellent actionability with real Swift code, clear workflow sequencing with checkpoints, and efficient use of tokens without unnecessary explanation. The main weakness is that all content lives in a single file rather than using progressive disclosure to split advanced topics (performance, accessibility, error reference) into separate documents.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It avoids explaining what terminals, PTYs, or escape sequences are, and jumps straight into actionable code. Every section earns its place with concrete implementation details rather than conceptual padding. | 3 / 3 |
Actionability | Nearly every section provides copy-paste-ready Swift code with specific API calls, method signatures, and concrete examples. The escape sequence table, SSH bridging pattern, and embedding steps are all directly executable with minimal adaptation. | 3 / 3 |
Workflow Clarity | The embedding workflow (sections 1-3) is clearly sequenced with explicit step numbering and checkpoint markers (✅) that define what success looks like at each stage. Gotchas serve as implicit validation guidance, and the error table in section 8 provides a feedback loop for common failure modes. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear numbered sections and tables, but it's a fairly long single file (~200 lines of substantive content). The performance optimization, accessibility, and error tables could be split into referenced files. Reference links at the bottom are helpful but the skill itself doesn't point to any companion files for deeper dives. | 2 / 3 |
Total | 11 / 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-agents
- Commit
010799b
- 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.