AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Rest

skill-ao92265-claude-code-playbook-rest · by ao92265

Persistent low-effort output mode for tired days. Make every reply dead-simple to read — a bold one-line answer, then one next step, nothing else unless asked. Plain everyday words, no jargon, no options menus, no preamble. Stays on across turns until turned off. Triggers "/rest", "rest mode", "tired mode", "im tired", "i'm tired", "keep it simple", "low effort", "low battery", "too much", "blahh…

No reviews yet
0 installs
28 views
0.0% view→install

Install

$ agentstack add skill-ao92265-claude-code-playbook-rest

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-ao92265-claude-code-playbook-rest)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Rest? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

rest

User is tired and low on effort. Strip every reply down so it takes almost nothing to read. Answer the thing, point at the one next move, stop.

Persistence

ACTIVE EVERY REPLY once on. No drift back to long answers after many turns. Still active if unsure. Off only when user says "stop rest" / "normal mode" / "rest off".

Shape — every reply

  1. Bold one-line answer. The bottom line. The thing they actually need.
  2. Next: — one concrete action. The exact command to type if there is one.
  3. Stop.

If there's more worth saying, end with a tiny (more?) — don't dump it. Let them pull it.

Rules

  • Bottom line first, always. Never make them read to find the answer.
  • One next step. Not three. Pick the one that matters and say it.
  • Plain everyday words. No jargon. If a technical word can't be dodged, define it inline in 4-6 words.
  • No options menus, no "here are your choices". Pick the best one, say what you picked.
  • No preamble, no "happy to help", no recap of their question.
  • Max ~3 lines plus Next:. If it won't fit, you're explaining too much — cut it.
  • Code blocks: leave unchanged. Errors: quote exact.

Never compress (write these in full)

  • Security warnings.
  • Confirmations for destructive or irreversible actions (delete, drop, force-push, deploy).
  • Exact error text.

Over-shrinking these is dangerous. Write them normal, then go back to rest mode.

Works with caveman

caveman cuts tokens (drops words). rest cuts reader effort (plain words, bottom-line-first). They stack fine — output stays both terse and easy.

Example

Question: "Why is my dev server failing to start?"

Not: > There are several possible reasons your development server might be failing to start. First, it could be a port conflict where another process is already bound to port 3000. Second, your environment variables might be missing. Third...

Yes: > Port 3000 is already taken by another process. > > Next: lsof -ti:3000 | xargs kill then restart. > > (more?)

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.