---
name: computer-use-writing-loop
description: Use when drafting a technical article with Claude CLI, Claude Code, or Hermes and computer-use style verification. It forces brief-first writing, read-only environment checks, narrow actions, prompt preservation, and final MDX validation.
version: 1.0.0
author: Mustafa Saraç / RICK
license: MIT
platforms: [macos, linux]
metadata:
  hermes:
    tags: [writing, computer-use, claude-cli, hermes, mdx, verification]
    related_skills: [hermes-agent-skill-authoring]
---

# Computer Use Writing Loop

Use this skill when the user wants Claude CLI, Claude Code, or Hermes to help write, revise, or publish a technical article while checking the real local environment instead of hallucinating it. The file is intentionally compatible with both Claude-style `~/.claude/skills/.../SKILL.md` placement and Hermes-style `~/.hermes/skills/.../SKILL.md` placement.

## Operating Principle

Write from verified context, not vibes.

The loop is:

1. Map the target article.
2. Create a short brief.
3. Inspect the repo and existing style references.
4. Verify the environment read-only first.
5. Draft the article.
6. Preserve prompts and decisions inside the repo.
7. Validate before claiming success.

## Safety Rules

- Do not touch secrets, payments, 2FA, private messages, or permission dialogs.
- Prefer read-only checks before any write action.
- If a GUI action is needed, make it narrow and verify with a screenshot or file read afterward.
- Do not publish, commit, push, or send externally unless the user explicitly asks.
- Never hide uncertainty. If something is assumed, label it.

## Article Workflow

### 1. Build a brief first

Create a local brief file such as:

```bash
mkdir -p content/_drafts
$EDITOR content/_drafts/article-brief.md
```

The brief should include:

- target reader
- thesis
- source material
- constraints
- tone references
- acceptance criteria
- files likely to change

### 2. Inspect before writing

Check the repo shape and nearby articles:

```bash
git status --short
find content -maxdepth 2 -type f | sort | head -80
```

Read 2-3 style references before drafting. Match structure and voice; do not clone wording.

### 3. Verify computer-use readiness if relevant

If using a computer-use bridge, check it before relying on it:

```bash
hermes computer-use status || true
cua-driver diagnose || true
```

If permissions are missing, stop and tell the user. Do not continue as if you can see the screen.

### 4. Draft in MDX

Draft with frontmatter, images, captions, and source notes. Keep the first version honest:

- what was actually checked
- what was generated
- what the human approved
- which prompts produced images or diagrams

### 5. Preserve reusable prompts

If the article uses generated images, diagrams, or repeatable prompts, save them inside the article or a sibling draft file. Future articles need the trail.

Recommended section:

```md
## Production notes

**Image concept**
> ...

**Prompt 1**
> ...
```

### 6. Validate

Run the project’s own checks. Examples:

```bash
npm run validate:mdx
npm run build
```

If warnings are from old unrelated files, say that clearly. If the new article caused warnings, fix them.

## Output Standard

At the end, report:

- changed files
- local preview URL if available
- validation commands and results
- publish status: draft or live
- next external action, if any, waiting for explicit approval

## Installation

Claude / Claude Code personal skill:

```bash
mkdir -p ~/.claude/skills/computer-use-writing-loop
curl -L https://mustafasarac.com/static/downloads/claude-computer-use-writing-skill/SKILL.md   -o ~/.claude/skills/computer-use-writing-loop/SKILL.md
```

Hermes personal skill:

```bash
mkdir -p ~/.hermes/skills/writing/computer-use-writing-loop
curl -L https://mustafasarac.com/static/downloads/claude-computer-use-writing-skill/SKILL.md   -o ~/.hermes/skills/writing/computer-use-writing-loop/SKILL.md
```

## Useful Invocation

Claude CLI:

```bash
claude -p "Use the computer-use-writing-loop skill. Draft a technical article from this brief, inspect the repo first, preserve prompts, and validate before reporting."
```

Hermes:

```bash
hermes chat -q "Use the computer-use-writing-loop skill. Draft a technical article from this brief, inspect the repo first, preserve prompts, and validate before reporting."
```

## Done Criteria

- [ ] Existing style references inspected
- [ ] Article draft written or updated
- [ ] Prompts/production notes preserved
- [ ] Images linked and reachable
- [ ] MDX validation run
- [ ] Build run when publishing
- [ ] No external send/publish unless explicitly requested