Skill
attack-path-analysis
Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and…
@cowork-osView SkillProductivity
Skill
/tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
Install
$ npx -y skills add CoWork-OS/CoWork-OS --skill tmux --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/tmux
Context preview
The summary Claude sees to decide when to auto-load this skill.
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
SKILL.md
tmux.SKILL.mdname: tmux
description: "Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output."
version: "1.0.0"
metadata:
author: CoWork OS Contributors <info@coworkosapp.com>
Tmux
Purpose
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
Routing
- Use when: Use when the user asks to remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
- Do not use when: Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead. Avoid using in non-interactive environments unless automation can fully satisfy prompts.
- Outputs: Outcome from Tmux: task-specific result plus concrete action notes.
- Success criteria: Returns concrete actions and decisions matching the requested task, with no fabricated tool-side behavior.
Trigger Examples
Positive
- Use the tmux skill for this request.
- Help me with tmux.
- Use when the user asks to remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
- Tmux: provide an actionable result.
Negative
- Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead. Avoid using in non-interactive environments unless automation can fully satisfy prompts.
- Do not use tmux for unrelated requests.
- This request is outside tmux scope.
- This is conceptual discussion only; no tool workflow is needed.
Runtime Prompt
- Current runtime prompt length: 3942 characters.
- Runtime prompt is defined directly in `../tmux.json`.
Read more
name: tmux description: "Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output." version: "1.0.0" metadata: author: CoWork OS Contributors <info@coworkosapp.com>
Tmux
Purpose
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
Routing
- Use when: Use when the user asks to remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
- Do not use when: Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead. Avoid using in non-interactive environments unless automation can fully satisfy prompts.
- Outputs: Outcome from Tmux: task-specific result plus concrete action notes.
- Success criteria: Returns concrete actions and decisions matching the requested task, with no fabricated tool-side behavior.
Trigger Examples
Positive
- Use the tmux skill for this request.
- Help me with tmux.
- Use when the user asks to remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
- Tmux: provide an actionable result.
Negative
- Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead. Avoid using in non-interactive environments unless automation can fully satisfy prompts.
- Do not use tmux for unrelated requests.
- This request is outside tmux scope.
- This is conceptual discussion only; no tool workflow is needed.
Runtime Prompt
- Current runtime prompt length: 3942 characters.
- Runtime prompt is defined directly in `../tmux.json`.
Ships withcowork-os
Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.
Get the whole plugin
Stats
450
Stars
77
Forks
Active
Maintenance
TypeScript
Language
MIT
License
5d ago
Last commit
7mo ago
Created
Repo: CoWork-OS/CoWork-OS
Other skills on cowork-os.
@cowork-osView SkillSkill
deep-security-scan
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated independent repository-wide…
@cowork-osView SkillSkill
finding-discovery
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository…
@cowork-osView SkillSkill
fix-finding
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch,…
@cowork-osView SkillSkill
security-diff-scan
Use when the user asks for a security review of a pull request, commit, branch diff, working-tree patch, or other Git-backed change set.
@cowork-osView SkillSkill
security-scan
Use when the user asks for a repository-wide or scoped-path security scan.
@cowork-osView Skill