pty
Working with PTY sessions for background and interactive processes
53
47%
Does it follow best practices?
Impact
36%
1.12xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./dot_config/opencode/skill/pty/SKILL.mdQuality
Discovery
22%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 description is too vague and incomplete to effectively guide skill selection. It identifies the domain (PTY sessions) but fails to enumerate specific capabilities and entirely lacks a 'Use when...' clause. Without concrete actions and explicit trigger conditions, Claude would struggle to reliably choose this skill over other terminal or process-related skills.
Suggestions
Add specific concrete actions such as 'Spawns PTY sessions, sends commands to background processes, reads output from long-running tasks, and manages interactive terminal sessions.'
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to run long-running commands, interact with terminal-based programs, manage background processes, or work with pseudo-terminals.'
Include natural trigger terms users would say, such as 'terminal', 'shell', 'command execution', 'long-running process', 'background task', and 'pseudo-terminal'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('working with') and does not list concrete actions. It mentions 'PTY sessions' and 'background and interactive processes' but doesn't specify what actions are performed (e.g., spawning, managing, sending input, reading output). | 1 / 3 |
Completeness | The description weakly addresses 'what' (working with PTY sessions) but completely lacks a 'when' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes some relevant technical terms like 'PTY sessions', 'background processes', and 'interactive processes' that a user might mention, but misses common variations like 'terminal', 'shell', 'command execution', 'long-running processes', or 'pseudo-terminal'. | 2 / 3 |
Distinctiveness Conflict Risk | PTY sessions is a somewhat specific domain, but 'background and interactive processes' is broad enough to potentially overlap with general shell/terminal skills or process management skills. The lack of specificity increases conflict risk. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A concise, well-structured skill that efficiently communicates PTY tool usage with good reference tables and parameter guidance. The main weakness is the lack of a concrete end-to-end example showing the typical spawn→read→kill workflow, and missing explicit validation steps (e.g., checking if a server is ready before proceeding).
Suggestions
Add a concrete end-to-end example showing a common workflow: spawn a dev server with pty_spawn, read output with pty_read using a pattern to confirm it's ready, then clean up with pty_kill.
Include an explicit workflow sequence for the most common use case (e.g., 'start background process → verify it's running via pty_list → read output until ready pattern matches → proceed') with a validation checkpoint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of what PTY is or how processes work. The key sequences table is a perfect example of dense, useful information. | 3 / 3 |
Actionability | Provides concrete parameter values and key sequences, but lacks fully executable examples showing a complete workflow (e.g., spawning a process, reading output, then killing it). The pattern examples are useful but shown as plain text rather than in tool-call context. | 2 / 3 |
Workflow Clarity | The sections cover the lifecycle (spawn → read → cleanup) but don't present it as an explicit sequenced workflow. There's no validation checkpoint or feedback loop for common scenarios like 'start server, wait for ready, then proceed.' | 2 / 3 |
Progressive Disclosure | For a skill under 50 lines covering a single focused topic, the content is well-organized into clearly labeled sections with logical progression from 'when to use' through 'cleanup.' No need for external file references. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- athal7/dotfiles
- Commit
07d79b6
- 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.