Pc Control

Hands on the local Mac for any agent - system state (battery, volume, brightness, IP), app launch/quit, open websites and YouTube, media and browser control via keystrokes, screenshots, clipboard, notifications, TTS, and honest mic/speaker hardware tests. Use whenever the user asks to control the computer, change volume or brightness, open an app or site, play or pause media, check battery/IP/running apps, take a screenshot, or test the mic or speakers. Rebuilt from the PC-Automation repo: the agent is the intent brain; this skill is only the hands.

40 stars 9 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)

npx skills add AnubhavChaturvedi-GitHub/PC-Automation --skill pc-control

Manual install

git clone --depth 1 https://github.com/AnubhavChaturvedi-GitHub/PC-Automation.git /tmp/PC-Automation
mkdir -p ~/.claude/skills
cp -r /tmp/PC-Automation/. ~/.claude/skills/pc-control

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# pc-control

One stdlib-only CLI gives the agent verified hands on this Mac. No third
party Python packages, no daemon, no interactive prompts. Every verb takes
arguments, returns useful text (or `--json`), and exits nonzero on failure
with a fix suggestion.

```bash
python3 ~/.claude/skills/pc-control/scripts/pc.py <command> [args] [--json]
```

## Start here

1. `pc.py doctor` - capability report. Run this first in a new environment;
   it tells you exactly which verbs are live and which are blocked by
   missing permissions, with the fix for each.
2. `pc.py <family> <action> --dry-run` - keystroke and URL verbs print what
   they would do without doing it. Use this when unsure.

## Verbs

### System state
| Command | Does |
|---|---|
| `battery` | percent, charging state, source, time remaining |
| `volume get\|set N\|up [N]\|down [N]\|mute\|unmute` | system output volume, 0-100 |
| `brightness up [steps]\|down [steps]` | display brightness via key codes (needs Accessibility) |
| `brightness get\|set V` | absolute values; works only where the DisplayServices API survives (broken on macOS 26, the command says so and points to up/down) |
| `ip [--public]` | local interface address; `--public` adds the WAN address |
| `apps [--all]` | visible apps, or every process with `--all` |
| `doctor` | environment and permission audit |

### Apps
| Command | Does |
|---|---|
| `app open NAME` | launch by name (`open -a`) |

Read the full skill on GitHub

Details

Skill name: pc-control
Repository: AnubhavChaturvedi-GitHub/PC-Automation
Repo updated: 12 August 2026

FAQ

What does the Pc Control skill do?

How do I install the Pc Control skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add AnubhavChaturvedi-GitHub/PC-Automation --skill pc-control. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Pc Control popular?

It lives in AnubhavChaturvedi-GitHub/PC-Automation, which has 40 GitHub stars and 9 forks.

Related skills

Econometrics

xiaomihu1992/econometrics-skill

Causal inference and applied econometric analysis on tabular data, from uploaded-data diagnostics and cleaning advice to treatment-effect estimation and publication-grade applied research design. Use for policy impact, ATE/ATT/LATE/ITT, OLS, propensity scores, IV/2SLS, DID/event studies, RDD, robustness checks, falsification tests, identification memos, 因果推断, 政策评估, 数据清洗建议, 稳健性检验, and 异质性分析.

Testing & QA

Cypress Explain

cypress-io/ai-toolkit

Explains Cypress tests (E2E and component tests), and answers questions about Cypress use and behavior. Use when the user asks to explain how a test works, explain how Cypress works, review or critique a test without writing code. Apply even when the user does not say 'Cypress' (e.g. 'explain this test'). Prefer the cypress-author skill when the user wants to create, fix, or update tests.

Testing & QAIn 1 list

Trip Planner

skywain/trip-planner-skill

End-to-end international trip planning: turns "I want to go to X for N days" into a verified, bookable plan — route skeleton across cities, flight price scans (international + domestic legs), train-vs-fly decisions, hour-by-hour daily timelines with opening hours, dwell times, holiday collisions and tappable turn-by-turn map links (小时级行程+地图导航+离线KML), hotel shortlists by neighborhood, budget rollup, and a booking checklist with deep links. Use this whenever the user asks to plan a trip, vacation, itinerary or honeymoon, compare flight dates/prices, pick between cities or routes, schedule a trav

Testing & QA

Cypress Docs

cypress-io/ai-toolkit

Search and extract Cypress information from official documentation (docs.cypress.io, cypress.io); prefer LLM markdown under /llm/* and refuse unverified API or behavior claims.

Testing & QAIn 1 list

Vibe Testing

knot0-com/vibe-testing

This skill should be used when the user asks to "test my specs", "validate my design docs", "find gaps in my architecture", "stress-test the spec", "vibe test", "pressure test the docs", or mentions spec validation before implementation begins.

Testing & QAIn 1 list

Cypress Author

cypress-io/ai-toolkit

Creates, updates, and fixes Cypress tests (E2E/end-to-end and component tests). Use when the user asks to create tests, add tests, write tests, update tests, test this file/component, new spec, or fix a failing or flaky test. Apply even when the user does not say 'Cypress' (e.g. 'create tests for this file'). Prefer cypress-explain when the user only wants to explain or review tests without changing code.

Testing & QAIn 1 list

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.