Skip to content
Back to skills

Improve Nando65 Orathon Second Brain

ASecurity

Turn one recurring pain point into one measurable, bounded workflow improvement.

  • 666 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 8, 2026
ai-agentsgo

Security analysis

A100/100

Scanned October 8, 2026

npx -y skills add majiayu000/claude-skill-registry --skill improve-nando65-orathon-second-brain --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Improve Nando65 Orathon Second Brain?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Improve Nando65 Orathon Second Brain
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-improve-nando65-orathon-second-brain/badge)](https://www.skillsdirectory.com/skills/majiayu000-improve-nando65-orathon-second-brain)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
---
name: improve
description: Turn one recurring pain point into one measurable, bounded workflow improvement.
argument-hint: "[problem or workflow]"
---

# Improve

Read `SYSTEM.md`, current objectives, source registry, decision journal, relevant captures, and recent healthchecks.

The goal is one useful improvement per run, not a broad transformation plan.

## Step 1 — Select one problem

Prefer a problem that is:
- repeated,
- expensive in time or errors,
- tied to a current objective,
- and narrow enough to test.

If the user already supplied a specific problem, use it unless evidence shows a prerequisite is missing.

## Step 2 — Define the before and after

Capture:
- current process,
- current pain or failure mode,
- desired output,
- one measurable success signal,
- who reviews or owns the result.

## Step 3 — Simplify before automating

Ask:
- Can any step be removed?
- Can inputs be standardized?
- Can a deterministic rule solve part of it?
- Which parts genuinely need language-model reasoning?
- Which decisions should remain human-owned?

## Step 4 — Map the workflow

Write:
- trigger,
- inputs and authoritative sources,
- ordered operations,
- decisions/branches,
- output destination,
- error path,
- privacy or permission constraints.

## Step 5 — Choose the smallest implementation

Use the least complex option that meets the goal:

1. checklist or template,
2. reusable prompt,
3. deterministic script,
4. AI-assisted workflow with review,
5. multi-step agent only when the earlier options are insufficient.

## Step 6 — Define acceptance

Before building, specify:
- sample input,
- expected output,
- what must never happen,
- how a human will verify quality,
- what evidence is required before increasing autonomy.

## Deliver

Record the decision in `journal/decisions.md`.

Then create or update one artifact under `workflows/` that implements the chosen approach. Preserve unrelated files.

End with:
- what changed,
- how to test it,
- what evidence would justify the next iteration.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.