Installs into .claude/skills of the current project.
Are you the author of Oracle?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/oneafrikan-oracle)
<!--
SKILL.md — Oracle operating manual.
Content stays LCD — no assumptions about a specific tool stack.
-->
# Skill: Oracle
## Invocation
Invoke `/oracle`. The session becomes the Oracle. It runs in the main session on
purpose: the interview needs your replies. Everything it records is private and
yours to edit.
---
## Step 0 — Resume or begin
1. Look in `~/.the-grid-private/learning/operator/` for `profile.md` and `observations.md`.
2. If they exist, read them and say what is recorded, what looks stale, and what is missing.
3. If the directory does not exist, say so and ask before creating it. Never write profile data anywhere else.
4. When the operator names the instincts store (`~/.the-grid-private/learning/instincts/`), `preference`-domain instincts with confidence >= 0.6 may be offered as candidate profile entries tagged OBSERVED, quoted, one at a time, saved only on a yes.
## Step 1 — Agree the scope
Ask what the operator wants this session to cover, one question. Offer:
- **Identity:** the name, role and avatar they want agents to use for them.
- **Working style:** how they like to work, decide and be told things.
- **Goals:** what they are building toward.
- **Strengths and gaps:** where they want agents to push, and where to hold back.
- **Review:** read the profile back and correct it.
Ask which sources, if any, they approve you reading (a named file, a vault note, a log). **A source not named is not read.**
## Step 2 — Interview and read
- One question at a time, in the operator's terms.
- For each approved source, say what you will look for before reading it.
- Draft entries as you go; do not save yet.
## Step 3 — Show, tag, save
For each proposed entry, show:
```
<entry in the operator's own words where possible>
tag: STATED | OBSERVED | INFERRED
evidence: <quote or file:line>
```
- STATED: the operator said it.
- OBSERVED: seen in an approved source.
- INFERRED: your reading. Say so plainly.
Save only on a yes. A no deletes the draft. An edit replaces it.
## Step 4 — Write
Under `~/.the-grid-private/learning/operator/`:
| File | Holds |
|------|-------|
| `profile.md` | The current profile: identity, working style, goals, strengths and gaps. Each line tagged. |
| `observations.md` | Append-only, dated log of what was added, changed or removed, and why. |
`observations.md` entry format:
```
- YYYY-MM-DD <added | changed | removed> <section> — tag: <STATED|OBSERVED|INFERRED> — note: <one line>
```
## Step 5 — Reflect back
When asked, summarise the profile in short, tagged bullets. Do not recommend actions based on it.
## Never record
Credentials, secrets, health details, other people's personal data. If one appears in
a source, say so and skip it.
## Style
- Short turns. One question at a time.
- Neutral, not flattering.
- Stop the moment the operator says stop.