agentleFS
TheVellerTheVeller/claude-skills/skills/agent-operations/contexto-aristas/SKILL.md

contexto-aristas

Skill4 starsChanged 13 days agoMITView on GitHub

Use this when briefing Hermes/Instinct by AgentMail: deep map + where to verify (Drive vault vs Mac-only vs Grok-only), not a short role list or carry dump.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when writing to Hermes, Instinct, or another outer peer on the report thread, or when auditing that a mail gave real cross-environment …

    line 10
  2. Distinctive:

    Every Grok→peer brief must include:

    line 16
  3. Very specific:

    Never only a short role list.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Contexto aristas (AgentMail)

Use when writing to Hermes, Instinct, or another outer peer on the report thread, or when auditing that a mail gave real cross-environment context.

Why

Peers do not share memory, disk, or tools. A carry/todo list is not enough. Instinct needs what it cannot see and where to verify what it can.

Depth bar

Every Grok→peer brief must include:

  1. Mapa — who lives where
  2. Dónde verificar — Drive vault paths, Notion/GitHub/Linear when relevant; mark Mac-only vs Grok-only
  3. Qué cambió on Grok computer / Kit OS
  4. Ciegos — explicit “Instinct cannot see X”
  5. Ask — one next step Never only a short role list. Prefer the living doc /workspace/lab/wiki/aristas-mapa.md.

Players

  • Ignacio — human A3 — [REDACTED: email]
  • Grok Bot — [REDACTED: email] — roster, HITL, Homelab PC, Kit OS
  • Hermes — Mac CoS — [REDACTED: email] (may reply via Ignacio Gmail)
  • Instinct — [REDACTED: email] — cloud edge

Verify (default)

  • Drive vault (Hermes/corp mirror): My Drive/One Drive/Obsidian/Claude Code Setup/Claude Code — Departments (Grok Bot), BOTS-INVENTORY, Agent-Contracts, Loops
  • Notion contracts index: Agent-Contracts page Ignacio already uses
  • Grok-only: ZeroClaw/NullClaw/Herdr/lab /workspace/lab — Instinct only via this mail
  • Daily WA/agentz ≠ AgentMail map

Never

  • Dump only Hermes carry
  • Claim Mac cron/WA health unread
  • Secrets in mail
  • Auto-send without Ignacio OK

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.