My NEW FAVORITE Skill - Claude Code Drives My Whole Computer (Better Computer Use)

Video authored by the channel shown, not by IANIA; all rights belong to the creator. Transcript and summary generated automatically; the original-language content is preserved.

Original language: English

Original video: My NEW FAVORITE Skill - Claude Code Drives My Whole Computer (Better Computer Use) · Channel: Cole Medin · 12:45 · Watch on YouTube

Topics: AI agents, Task and workflow automation, Claude Code, AI safety

Summary

Cole Medin presents Drive Screen, a lightweight skill that lets a coding agent control a computer through command-line tools without installing a separate computer-use harness. He describes using it for tasks such as morning setup, opening apps, and testing desktop software, and explains how its scripts and documented workflows make screen control more reliable and customizable across operating systems. The video includes a brief live demo and a walkthrough of the skill’s workflow, tools, and limitations. He discusses prompt-injection risks, recommends using capable models and keeping tasks simple, and explains how viewers can install or adapt the skill.

Key points

Drive Screen is designed as a lightweight alternative to larger computer-use tools and requires no additional tooling beyond a coding agent and command-line access.
The skill can help prepare a morning workspace by opening browser tabs, desktop apps, and other resources.
The creator says he tested the skill on Mac, Linux, and Windows, including different display settings and multiple-monitor setups.
The skill grew out of using terminal commands to research and test desktop applications, then documenting recurring failure modes.
Its workflow first checks whether screen control is necessary, since the creator describes it as the slowest and least reliable way to make a computer do something.
Bundled scripts provide repeatable commands for tasks such as discovering and focusing windows, typing, and pasting.
The skill includes rules for a control loop: discover a window, take a screenshot, focus it, and then act.
The creator cautions that prompt injection is a consideration and suggests reserving screen control for simpler tasks rather than production-grade use.
Viewers can install the skill from the creator’s AI skills repository or adapt its files for their own coding agent.

Chapters

Start	Chapter	Summary
00:00	Introducing Drive Screen	The creator explains why he built a lightweight computer-use skill and describes its potential for everyday productivity.
02:36	Use cases and how the skill began	He shares examples of adaptable AI tasks and recounts using command-line control to test desktop applications.
05:15	Packaging the workflow and sponsor segment	The creator describes turning recurring lessons into a skill, then presents Plural’s Kubernetes DevOps workbenches.
06:49	Live demo and skill design	After a brief demonstration, he outlines the skill’s workflow, including checking whether screen control is needed and using scripts for more deterministic actions.
09:00	Scripts, rules, and customization	He explains the custom CLI, hard rules, control loop, and ways to adapt the skill to different environments.
11:07	Security considerations and installation	The creator discusses prompt injection and model choice, then points viewers to the skill and encourages them to try it.

Quotes

I call it drive screen — 00:00

this alone saves me like a solid like 10-15 minutes every single morning — 02:03

Screen control is the slowest and least reliable way to make a computer do something. — 07:55

first, discover the window with a command, screenshot it so you have the lay of the land, focus in on it, then you can act. — 10:03

You don’t have to bring in any additional tooling — 12:14

Concepts and entities

Drive Screen, Claude Code, Codex, Cole Medin, Plural, MCP, prompt injection, AI skills

Full transcript (original language)

00:00 I have a new favorite skill that I’m using in Claude code and code X every single day for everything under the sun. I call it drive screen and I want to show you how this works today cuz I built it to be a super lightweight alternative to the really bloated and hard to manage computer use tools like what Claude has built into their platform. We have code X computer use. There’s a ton of open source tools out there as well and these are all powerful, but I’ve never been a fan of using them. That’s why I built my own skill and the beauty of what I built here is you just need your coding agent.

00:30 You don’t have to install anything or build any kind of harness. Large language models, especially with Fable 5.1 and GPT-6 Astra now, they’re good enough where they can drive your entire screen for pretty much anything with just the command line. I didn’t realize that until I just tried it out a couple of weeks ago and that’s eventually led to building the skill which I love cuz it works no matter the operating system and now I don’t have to install anything else or rely on a massive out of the box computer use tool. Like I said, I’ve never been a fan of these. I want to control all my tooling and with these

01:01 tools it’s really hard to customize things and tweak it as little issues come up as you’re incorporating it in your workflow. And so because of that, I’ve just always strayed away from computer use as a whole. The problem is computer use is incredibly useful and I’m realizing that more and more the last couple of weeks. There’s a reason I’m obsessed with using the skill now. So if you’re not using computer use at all right now, I would encourage you to at least start dabbling with it with the tool like, you know, code X computer use. Of course, I would encourage you to try out the skill that I’ll link to in

01:31 the description. There’s just endless possibilities, ways to boost your productivity using this kind of capability with your coding agent. Now, of course, there are some security concerns, especially when you’re running just a skill instead of a full harness. We’ll definitely talk about that, but there are so many quick wins I’ve started relying on every single day that I want to show you here. I mean, the most obvious one is to use your coding agent to help you get set up in the morning. So you turn on your computer, you open up your coding agent, and you say get my morning setup, right? Like here are the things I’m working on for today. It could even go look at your

02:03 task management software with the CLI or MCP, and then it can get things open for you. In your browser tabs, opening up tabs in Obsidian, getting desktop apps started, Docker containers, whatever you need, it can set up everything. And so, like this alone saves me like a solid like 10-15 minutes every single morning, and that adds up, especially with all the other things I’ll show you here. And so, it just uses the skill and simple commands to drive everything. There is no additional tooling installed here. And I’ve tested this skill on each operating system, Mac, Linux, and Windows. I’ve tested with multiple

02:36 monitor setups and different display settings. It’s really good and really adaptable. And here’s the thing, even if you’re not super interested in this specific skill I’m showing you right now, the big takeaway here, what really just blows my mind, is how adaptable large language models have become. There’s so many tasks that I’ve just written off before as the LM can’t do it, or I think you need some massive tool like for computer use where now you just don’t. Like you probably have a couple of ideas in your head right now for something you think an LM can’t do. Like computer use or editing a video,

03:07 you think you need some fancy tool, but you actually don’t. Just like try it out right now. Give it an MP4 and say edit this video, take out the ums, add in b-roll and transitions. And especially with like Fable and Astra, like it’ll knock it out. And to be totally honest with you, this Drive Screen skill has been simply born out of necessity cuz recently I’ve just been kind of overwhelmed with all the different things happening in the AI space, things I got going on, applications that I’m trying out, especially a lot of open source projects like Kestra for example. I’m trying out all of these, and a lot of them they have a UI, or there’s something where I can’t just use my

03:39 browser automation, so I needed some kind of computer use to test things out, but also I wanted something super lightweight and easy for me to manage. I didn’t want to bring in a full computer use tool. And so, at the time I just took this GitHub URL and all the other ones I was testing, I mean, this is just one example here. I gave it to Claude and I said, “Research the web, dive into the repo to understand the features, then start the desktop app, and then control my screen to test out different features, and then leave it open for me at the end to continue my own testing.” And I had no idea if that would work. I

04:11 thought maybe it would go for some larger computer use tool and install it, or maybe it would just say it can’t do it and tell me to do things manually. But, to my pleasant surprise, it was able to go through it end to end simply by running commands in the terminal. So, this is about what my session logs look like, especially before I had the skill. So, it runs command after command to click around and take screenshots and analyze results, but it did the whole thing end to end. It took a while, it’s not the most efficient, I mean, computer use isn’t in general, but I just let it go, take control of my computer, I

04:42 worked on another device, I came back, and everything was done, and everything was still up for me to continue the testing as well. It was a beautiful thing. And with all these commands, for me on Windows, it’s just simply PowerShell, right? Like, there’s no additional tool brought in. For Mac, you can use AppleScript. Again, I’ve tested this for every OS. And so, I was hooked on this right away. Testing a bunch of different apps, doing my morning setup, like I showed earlier, having it set things up for my presentations and recordings every single day. Now, it didn’t start as a skill, like I just say like use PowerShell to drive my screen and do XYZ, but it became obvious very

05:15 quickly that we need a full skill, because sometimes the computer use wouldn’t even work through PowerShell. Like, the agent would get totally tripped up, or there’d be certain failure modes that I’d see come out as patterns. And so, I’ve documented all the failure modes. I’ve laid out the workflow, even built some scripts to make things more deterministic, and that is what I have packaged up as the skill for you. The sponsor of today’s video is Plural, and they built something genuinely cool. DevOps agents that live in your own Kubernetes clusters, figure out what’s broken when something is, and then open up pull requests to fix it. They call it workbenches. So, let me

05:48 show you. Right now in my own cluster, I have one of my services, the payments API, that is crash looping. But, all I have to do here is go to the workbench where I can send off any job, and I simply said the payments API service is crash looping, find the root cause, and open up a pull request to fix it. And here, Plural spins up subagents that each have their own context to dive really deep into the pods, the logs, the GitOps repository. A couple minutes later, it identifies the exact problem. It gives me the diff and the evidence, and even builds me a dashboard to help me understand the problem that’s

06:18 happening here in my cluster. And then my favorite part is it spins up a Cloud Code instance in my cluster to make the fix and then open up the pull request. And so, the agent runs in my environment with my model keys, and I still get to be the one to merge the pull request in the end. And you can wire up that same workbench to your alerts, run it on a cron, or even trigger it by saying Plural fix this in a Jira ticket. You can self-host Plural or use their cloud, and it’s free to get started. I’ll have a link to them in the description. So, of course, I want to get into how this skill works, how I’ve kept it simple,

06:49 security considerations. We’ll talk about that in a second, but what I want to do for you really quickly here is show you a live demo of this skill working. And so, I’m obviously going to speed it up a lot, but I’m going to send off this prompt so we can see it in action, loading the skill and then super easily going through any kind of setup that I have for it. And so, I’m going to turn off my video and then fast forward here so you can watch it happen. So, there we go. We completed everything within just a minute here. I know it’s a very simple example I’m showing you here. I don’t want to do anything super

07:22 comprehensive right now, but the point is that it’s fast. It didn’t take a lot of commands either because the skill guides it and even gives it some tooling to move faster. And by the way, what it did here even includes validating the environment to make sure it has all the tools it needs, and that it has the permission it needs on the machine as well. And so, that’s just a super quick example. Now, let’s talk more about how the skill works. So, this skill as a whole is a little under 400 lines long. So, not the longest, but also not the shortest. I I wanted to have a full workflow laid out for the agent here, and also make it work for every operating system. And there’s a lot of

07:55 nuances I wanted to build in, little failure modes that I’ve seen as I’ve tested it out. And so, the workflow starts by figuring out, do we even need screen control at all? I want the agent to have the opportunity to push back when you use this skill, because sometimes it really doesn’t require computer use when you think. There’s some other kind of tool like browser automation to get the job done. Like it says right here, screen control is the slowest and least reliable way to make a computer do something. So, it’s the most adaptable and flexible, but it’s the slowest. And there’s the

08:27 security issues where you can have prompt injection attacks come on your screen, so the agent views that and does something malicious. Large language models really don’t fall for that anymore, which is also a big reason why I’m trusting it with this kind of capability now. But just something to keep in mind. That’s also why I stick to really simple things when I’m using this tool. If I want any kind of production-grade computer use, I’m still going to be using some kind of larger harness or tool. And then going up to the top of the skill really quickly, I want to call up the different scripts that ship with the skill. This provides more determinism. So, instead of the

09:00 agent having to figure out the exact commands for certain things in real time, like I had to do initially, I have all the best practices packaged up into these scripts now. For window discovery and focusing and typing and pasting. There’s many different ways to do these things. I figured out the best from all the testing I’ve done. And let me tell you, I’ve done hours and hours and hours of testing. And then I built it into essentially this little CLI for the agent to call upon with the different commands and arguments. And so, it’s my own little custom CLI. We don’t have to get into the details of all this right

09:31 now. There’s quite a bit here because there’s so many different operations the agent can perform, but it’s a big part of what makes this more reliable. And it’s also very easy to customize things if you’re working on some other kind of distribution of Linux, for example, that might need things to operate a bit differently, you can just go in and edit the skill, right? So, like when you install the skill from my skills repository, everything comes with it, the reference, of course, the skill.md, and all the scripts for the CLI. And then scrolling back down again, we have all the hard rules. These are things I learned the hard way, just as I was building up the skill and using it over

10:03 and over again. So, that makes it more reliable. We have the control loop, like whenever you’re operating in a window, here’s what you should do, right? Like first, discover the window with a command, screenshot it so you have the lay of the land, focus in on it, then you can act. And here are the ways that you act and the CLI that you have to help you with that, right? So, you can see everything coming together here. I don’t even have to go and read through it literally everything, but there’s also like a whole CLI for watching a session, like if you have it drive another coding agent session and needs to watch for approvals or things like that. I’ve done a lot of that as well.

10:35 Auto driving, we have uh different traps that we needed to watch out for. And so, some of these things are specific to what I’ve been automating with, like browser tabs, and desktop applications, and then other coding agent sessions. Maybe you’re going to be doing the same things, maybe not, but again, that you can take this skill and customize it to your liking. So, if you want to take out traps cuz they don’t apply to you or add some in, you can feel free to do that, right? Like that’s the kind of thing that you can’t really do with a larger computer use tool. Just going back to that reason again and again and why I love having this flexibility so much. Now, like I

11:07 mentioned a bit ago, you also do have to be aware of prompt injection attacks for just computer use in general. I’ll link to this article in the description, it’s a really good read. But also, I got to say, and this might bite me in the butt a little bit, I don’t think you have to worry about prompt injection attacks that much anymore as long as you’re using the new best models like Fable 5.1 and GPT-6 Astra. There are a lot of studies coming out that are showing that even without fancy guardrails or a fancy harness, these LLMs are very very hard to prompt inject. And so I’m just not concerned about it these days, at least

11:42 nearly not nearly as much as I was before. I don’t think you have to be either. And especially if we’re using the skill for simpler things like what I showed in this video like morning setup and testing desktop apps, things like that, you really don’t have to worry about it. And so yeah, I would say just make sure you’re using the most powerful LLMs when you’re using computer use makes it the most reliable anyway. And this skill, it is pretty token efficient. It’s not the fastest, but it’s because it’s waiting on different inputs and things, not because it’s burning through tens of thousands of tokens. And so use it your own risk and I would encourage you to use better

12:14 models, but I will say at least for me I don’t consider it a risk for computer use anymore, especially when I have something that I can control so much like this. So I would encourage you to install the skill, try it out. You don’t have to bring in any additional tooling, it’s just right here in my AI skills GitHub repo. can install it as a Claude code plugin if you want to bring in all my skills or you can just take that skills folder that I have linked in the description and bring it into any coding agent. And so I hope that you find this useful. And even just exploring with me in general the new capabilities of LLMs,

12:45 how they’re able to do these incredible things without an additional harness anymore. And so if you appreciate this video, you’re looking forward to more things on coding agent skills and AI coding in general, I would really appreciate a like and a subscribe. And with that, I will see you in the next video.