Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Sensory Structured Observation

ASecurity

Applies disciplined observation to a situation — suspending interpretation to see what's actually there before deciding what it means. Triggers: 'observe this carefully', 'structured observation', 'what do you actually see', 'suspend interpretation', 'look more carefully'.

19 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agents

Works with

cli

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill sensory-structured-observation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Sensory Structured Observation?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Sensory Structured Observation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-sensory-structured-observation/badge)](https://www.skillsdirectory.com/skills/rondoflow-sensory-structured-observation)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: sensory-structured-observation
description: "Applies disciplined observation to a situation — suspending interpretation to see what's actually there before deciding what it means. Triggers: 'observe this carefully', 'structured observation', 'what do you actually see', 'suspend interpretation', 'look more carefully'."
---

# Structured Observation

Most observation is interpretation in disguise. We perceive a situation and instantly explain it — but the explanation overwrites the raw data. Structured observation forces a separation between what can be directly seen and what we conclude from it.

---

## Your Process

**Step 1: Define the Target and Time Boundary**
Name the exact thing being observed and the scope. What counts as inside this observation, and what is out of scope?

**Framing check:** Confirm the specific subject before continuing. State what you've identified — the actual object being observed and its boundaries — in one sentence, then use `AskUserQuestion`:
- **Question:** "I'm reading this as: [your one-sentence framing of the specific subject and scope]. Is that right?"
- **Header:** "Framing"
- **Options:**
  - **Yes — proceed** — framing is correct
  - **Adjust** — one element is off; user will correct it before you continue
  - **Reframe** — different situation than read; incorporate the correction before proceeding

**Step 2: Separate Observation from Interpretation**
Write only what can be directly observed — no inferences, no attributions of intent or cause. "User clicked back immediately" not "user was confused." Flag every sentence that is actually an inference and set it aside.

**Step 3: Observe at Three Levels**
- **Events** — what is happening? Discrete, specific occurrences.
- **Patterns** — how is it happening? Recurring structure across events.
- **Absences** — what is not happening that might be expected?

**Step 4: Flag Surprising or Incongruent Observations**
What doesn't fit? Where does something contradict expectations?

**Before narrowing:** Show the complete set of observations from Steps 2–3 to the user first. Use `AskUserQuestion`:
- **Question:** "I've catalogued [N] observations across events, patterns, and absences. Before I select the most surprising or incongruent, are there any you'd flag as especially important, or any I've missed?"
- **Header:** "Prioritise"
- **Options:**
  - **Proceed with your selection** — the set looks right
  - **Flag one** — user will name a specific observation to include
  - **Add a missing one** — user will describe it

These are the most information-rich observations — prioritise them.

**Step 5: Generate Interpretations**
Only after completing Steps 2–4: generate multiple possible interpretations for each key observation. Aim for at least two competing explanations.

**Step 6: Identify the Most Testable Interpretation**
Which interpretation makes the most specific, falsifiable prediction? That is the one to act on first.

---

## Human Check-in

Before proceeding, use the `AskUserQuestion` tool. State your interpretation of the situation in 1–2 sentences — what is being analyzed and what the core question is — then ask:

- **Question:** "My read: [your 1–2 sentence interpretation]. How do you want to proceed?"
- **Header:** "Scope"
- **Options:**
  - **Full analysis** — Complete all steps, reasoning shown throughout
  - **Key findings only** — Bottom-line output, skip step-by-step detail
  - **Initial observations only** — What's actually there before any interpretation is applied
  - **Reframe** — The read is off; correct it and the analysis will follow the corrected framing

Proceed based on their selection. If the user reframes, incorporate the correction before running any analysis.

## Output Format

### Observations
| Level | Observation (no interpretation) |
|-------|----------------------------------|
| Event | ... |
| Pattern | ... |
| Absence | ... |

### Surprising or Incongruent Observations
- List each, with a note on why it is surprising.

### Interpretations per Key Observation
| Observation | Interpretation A | Interpretation B |
|-------------|-----------------|-----------------|
| ... | ... | ... |

### Most Testable Interpretation
State it as a prediction: "If [interpretation] is correct, then [specific observable consequence]."

---

## Notes

Run this before diagnosis, analysis, or decision. The discipline has most value when you feel you already understand the situation — that feeling is usually a sign that interpretation has already overtaken observation.

---

## What's Next

After delivering this output, use `AskUserQuestion` to offer the next move:

- **Question:** "Observation complete. What's next?"
- **Header:** "Next"
- **Options:**
  - `/sensory-detail-mining` — Mine details from what structured observation revealed
  - `/sensory-signal-detection` — Detect signals in the observed
  - `/aesthetic-coherence-check` — Check coherence of what was observed
  - **Done** — Wrap up and synthesise what we have so far

Attribution

rondoflowrondoflow
View sourceMore from rondoflow →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

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 (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693621 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →