Skip to content
Back to skills

Perch

ASecurity

Mid-session orientation — summarize what's done, surface unresolved points. Assesses clear-readiness and offers to do the work if conditions are right.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 19, 2026
toolsgo

Security analysis

A100/100

Scanned October 19, 2026

npx -y skills add MinhHaDuong/ImperialDragonHarness --skill perch --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Perch?

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

Security grade badge for Perch
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/minhhaduong-perch/badge)](https://www.skillsdirectory.com/skills/minhhaduong-perch)

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

Download with Pro
SKILL.md
---
name: perch
description: "Mid-session orientation — summarize what's done, surface unresolved points. Assesses clear-readiness and offers to do the work if conditions are right."
user-invocable: true
argument-hint:
---

# Perch — mid-session position check

Read-only report from conversation context. Run at any point to re-orient.

## Steps

1. **Report: Done.** What is concretely finished in this conversation:
   - Files written or edited.
   - Commits and PRs merged.
   - Tickets closed.
   - Decisions reached.
   Items only. No prose.

2. **Report: Open.** Raised but not finished:
   - Work mentioned but not started or deferred.
   - Issues discovered but not fixed.
   - Docs or state noted as stale.
   - Questions asked and not answered.
   Items only. Be specific — a vague "follow-up needed" is useless.

3. **Report: Drift** (only if present). Topics that diverged from the original goal. Omit section entirely if there was no drift.

4. **One-line stance.** Where things stand and what the natural next move is.

5. **Assess clear-readiness.** Silently evaluate:
   - Is this a natural reset point? (task complete, decision made, milestone reached)
   - Are Open items light enough to close out quickly? (ticket, memorize, or commit each one)
   - Is there uncommitted work that needs a commit first?

   **If conditions are favorable:** propose a clear offer — one sentence naming exactly what you will do (e.g. "I can ticket X, save memory Y, and commit Z, then we're clear to /clear"). Wait for yes.

   **If not favorable** (deep mid-task, many open threads, risky uncommitted state): say nothing. The report stands alone.

## Output shape

```
## Done
- …

## Open
- …

## Drift  ← omit if none
- …

**Stance:** [one sentence]

[Clear offer if conditions are right — else nothing]
```

No headers beyond these. No preamble. No "Here is a summary of…" opener.

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.