MCP HubMCP Hub
Retour aux compétences

remote-viewing-guidance

pjt222
Mis à jour 2 days ago
3 vues
17
2
17
Voir sur GitHub
Designaidesign

À propos

Cette compétence de Claude agit comme un moniteur de vision à distance, guidant un utilisateur à travers les étapes structurées (I à VI) d'une session de Vision à Distance Contrôlée. Elle gère le protocole, fournit des références cibles, et identifie/corrige les intrusions de surimpression analytique (AOL). Utilisez-la lorsqu'un développeur a besoin de pratiquer ou de s'entraîner à la CRV et nécessite un moniteur automatisé pour faciliter une perception intuitive structurée.

Installation rapide

Claude Code

Recommandé
Principal
npx skills add pjt222/agent-almanac -a claude-code
Commande PluginAlternatif
/plugin add https://github.com/pjt222/agent-almanac
Git CloneAlternatif
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/remote-viewing-guidance

Copiez et collez cette commande dans Claude Code pour installer cette compétence

Documentation

Remote View (Guidance)

Guide person through structured CRV session as monitor/tasker. AI manages protocol, gives target ref, catches AOL, redirects through staged data collection.

Use When

  • Person wants CRV practice + needs monitor
  • Train viewer through staged process w/ realtime feedback
  • Facilitate structured intuitive perception in repeatable format
  • Develop non-local awareness complementing healing (see heal-guidance)
  • Viewer needs protocol discipline (AOL catching, stage progression)

In

  • Required: Target ref (coord pair, alphanumeric, sealed envelope — must be blind to viewer)
  • Required: Viewer has paper + pen (CRV = pen-on-paper; no digital during session)
  • Required: Quiet undisturbed space (min 30 min)
  • Optional: Target feedback envelope/info → post-session reveal
  • Optional: Viewer's meditation warmup (strongly rec meditate-guidance first)

Do

Step 1: Cooldown

Transition viewer from analytical → receptive state. Don't skip.

  1. "Sit comfortably with your paper and pen ready"
  2. "Close your eyes and focus on your breath for 5 minutes" (guide via meditate-guidance Steps 2-3 if needed)
  3. "Release all expectations about the target — you know nothing and should want to know nothing yet"
  4. "Let your mental chatter slow naturally — don't force silence"
  5. "When you feel a shift from thinking about things to simply being present, let me know"
  6. Once ready: "Open your eyes and write the target reference at the top of your paper"

Provide target ref only when viewer confirms ready.

→ Calm open mental state, min internal dialogue. Analytical mind quieted not asleep. Viewer alert + receptive.

If err: mind busy after 5 min → extend 10 min. Specific concern intrusive → "Write that concern on a separate sheet — your 'parking lot' — and set it aside." Don't begin Stage I while viewer agitated.

Step 2: Ideogram (Stage I)

Ideogram = spontaneous mark in response to target signal. Guide production.

  1. "Write the target reference on your paper"
  2. "Touch your pen to the paper"
  3. "In one quick, spontaneous motion, let the pen make a mark — don't think, plan, or draw deliberately"
  4. "The mark should take less than 2 seconds — a short squiggle, curve, or angular mark"
  5. Once produced: "Now decode the ideogram — probe it for:"
    • "A: What is the activity at the site? Motion, stillness, energy?"
    • "B: What is the feeling or sensation? Hard, soft, wet, dry, warm, cold?"
  6. "Write the A and B components next to the ideogram"
  7. Ideogram feels incomplete: "You may produce one more — but no more than 3 total"

Watch for deliberate drawing. Viewer takes > 2-3 sec → intervene.

→ Spontaneous mark feels "arrived" not "drawn". A/B decode produces immediate simple descriptors, not complex imagery.

If err: ideogram clearly deliberate (viewer thought what to draw) → "Set that aside. Close your eyes, take 3 breaths, and try again." Can't produce spontaneous → cooldown insufficient → return Step 1.

Step 3: Sensory (Stage II)

Systematically collect sensory data w/o interpretation.

Stage II Sensory Channels:
┌──────────────┬────────────────────────────────────────────────────┐
│ Channel      │ What to Report                                     │
├──────────────┼────────────────────────────────────────────────────┤
│ Visuals      │ Colors, brightness, contrast, patterns (NOT       │
│              │ objects — "blue" not "ocean")                      │
├──────────────┼────────────────────────────────────────────────────┤
│ Textures     │ Rough, smooth, grainy, slippery, porous, metallic │
├──────────────┼────────────────────────────────────────────────────┤
│ Temperatures │ Hot, cold, warm, cool, ambient, fluctuating       │
├──────────────┼────────────────────────────────────────────────────┤
│ Sounds       │ Loud, quiet, rhythmic, sharp, humming, rushing    │
├──────────────┼────────────────────────────────────────────────────┤
│ Smells       │ Sharp, sweet, chemical, organic, damp, dry        │
├──────────────┼────────────────────────────────────────────────────┤
│ Tastes       │ Metallic, salty, sweet, bitter, neutral            │
├──────────────┼────────────────────────────────────────────────────┤
│ Dimensionals │ Wide, tall, narrow, enclosed, open, deep, layered │
├──────────────┼────────────────────────────────────────────────────┤
│ Energetics   │ Moving, still, vibrating, dense, light, pressured │
└──────────────┴────────────────────────────────────────────────────┘
  1. "Go through each sensory channel — write one descriptor per line"
  2. "Write quickly — first impression only, don't deliberate"
  3. "Use single words or short phrases, never sentences"
  4. "If a channel produces nothing, write 'nothing' and move on — don't fabricate"
  5. "Circle any descriptor that feels particularly strong or confident"

Watch analytical labels creeping. Viewer says "ocean" not "blue, moving, wet" → redirect: "That sounds like an interpretation — what are the raw sensations underneath it?"

→ List of 10-20 raw sensory descriptors feeling "received" not "invented". Low-level (textures, colors, temps), not high-level (names, functions, labels).

If err: every descriptor fabricated → "Stop. Close your eyes. Take 3 breaths. Touch your pen to the ideogram and reconnect." One channel dominates → "Shift to a different sense — what about temperature? What about texture?" Data dries up → move Stage III.

Step 4: Dimensional (Stage III)

Move raw sensory → spatial + structural info.

  1. "Close your eyes briefly and sense the overall scope — is it large or small, enclosed or open, natural or constructed?"
  2. "Begin a rough sketch of the spatial layout — not a picture, just proportions and relationships"
  3. "Probe for dimensions: height, width, depth — how many distinct areas?"
  4. "Note spatial relationships: what's to the left, right, above, below?"
  5. "Write dimensional descriptors alongside your sketch"
  6. "Note Aesthetic Impact (AI) — how does the target make you feel? Not what it is, but how it affects you"

→ Rough spatial diagram w/ dimensional annotations. Target's general scope clearer. Aesthetic impact captures "feeling" of site.

If err: sketch feels pure imagination → simplify: "Draw only basic shapes — circles, rectangles, lines — representing spatial relationships." No dimensional data → redirect Stage II: "Go back to sensory probing. Look for dimensional hints in textures and temperatures."

Step 5: Target Sketch

Coach more developed visual rep from accumulated data.

  1. "On a fresh sheet, draw what the accumulated data suggests — NOT what you think the target is"
  2. "Use your sensory descriptors to guide the sketch — if 'smooth, curved, tall' appeared, draw a smooth curved tall form"
  3. "Label areas of the sketch with the sensory data that generated them"
  4. "Add any new impressions that arise during sketching"
  5. "Don't erase or second-guess — if something contradicts an earlier impression, draw both and note it"

→ Sketch repping perceptual data, labeled w/ source descriptors. May not look recognizable.

If err: can't sketch → accept written spatial: "Tall form center, low flat area right, rounded shape upper left." Reassure sketch = organizational tool, not art exercise.

Step 6: Manage AOL

AOL mgmt = monitor's most important fn. Watch entire session.

AOL Types and Monitor Response:
┌──────────────────┬─────────────────────────────────────────────────┐
│ Type             │ Monitor Action                                  │
├──────────────────┼─────────────────────────────────────────────────┤
│ AOL (naming)     │ If the viewer says "it's a bridge" — instruct: │
│                  │ "Declare 'AOL: bridge' on your paper and move  │
│                  │ on. Don't pursue or suppress it."              │
├──────────────────┼─────────────────────────────────────────────────┤
│ AOL Drive        │ If naming becomes insistent and recurring —     │
│                  │ instruct: "Write 'AOL Drive: [label]' and take │
│                  │ a 60-second break with eyes closed."            │
├──────────────────┼─────────────────────────────────────────────────┤
│ AOL Signal       │ After declaring AOL, extract the signal:        │
│                  │ "The word 'bridge' — what raw descriptors are  │
│                  │ underneath that? Spanning? Long? Connecting     │
│                  │ two areas? Write those as valid data."          │
├──────────────────┼─────────────────────────────────────────────────┤
│ AOL Peacocking   │ If the viewer constructs elaborate scenarios — │
│                  │ intervene: "Write 'AOL/P' and return to Stage  │
│                  │ II basics. Report raw sensations only."         │
└──────────────────┴─────────────────────────────────────────────────┘

Emphasize: "Discipline ≠ avoiding AOL — catching + declaring so no contaminate data. Every viewer experiences AOL. Skill = how fast you catch."

→ AOL recognized in seconds, declared on paper, session continues w/o derail. Sensory-level data stays separate from analytical labels.

If err: AOL takes over (viewer constructing narrative for several min) → "Let's call an AOL Break. Close your eyes, take 10 breaths, and we'll restart from Stage II." Mark heavily contaminated segments in record.

Step 7: Later Stages (Optional)

For experienced viewers, later stages probe deeper. Only proceed if Stages I-III produced solid data.

Stage IV (Emotional/Intangible):

  1. "Probe for the emotional tone at the target site"
  2. "Note intangible impressions: purpose, significance, historical context"
  3. "Write these separately and mark them as Stage IV data"

Stage V (Interrogation):

  1. "Direct specific questions at the target: What is the primary function? Who is associated?"
  2. "Write the first impression — don't deliberate"
  3. "Mark all Stage V data clearly — it carries higher AOL risk"

Stage VI (3D Model):

  1. If materials available: "Build a clay or detailed sketch model from all your data"
  2. "Use this to test spatial relationships and discover overlooked elements"

→ Deeper, more specific data beyond physical description. Stage IV+ needs strong I-III foundation.

If err: later stages produce only AOL → "Let's step back to Stage II. The protocol is sequential for a reason — each stage needs the foundation of the one before it."

Step 8: Close + Review

End session formally + structured review.

  1. "Write 'Session End' and the current time on your paper"
  2. "Review all pages in order: ideogram, sensory data, dimensional data, sketches, AOL declarations"
  3. "Circle the 5-10 data points you feel most confident about"
  4. "Write a brief summary — 2-3 sentences about what the target feels like, not what it is"
  5. Target feedback available → reveal target + guide comparison
  6. "Compare data point by point — note hits, misses, and AOL contamination"
  7. "File the session for future reference and pattern recognition"

→ Complete session record w/ clearly separated raw data, AOL declarations, summary. Upon feedback, some hits, misses, ambiguous.

If err: viewer feels session produced nothing → guide review anyway: "Viewers freq underestimate accuracy because look for exact ID. Description of 'tall, smooth, cold, outdoor, historical' matching monument = successful session — even w/o naming."

Check

  • Cooldown done + verified before Stage I
  • Ideogram spontaneous (< 2 sec), not deliberate
  • Stage II = low-level sensory descriptors, not analytical labels
  • All AOL caught + declared on paper at moment of recognition
  • Session progressed sequentially (I → II → III → sketch → higher)
  • Target blind to viewer throughout
  • Closed formally w/ summary before feedback
  • All session papers preserved for review
  • Monitor maintained protocol w/o leading viewer

Traps

  • Lead viewer: Monitor provides protocol structure not content hints — never say "try focusing on the structure" if you know target is building
  • Insufficient cooldown: Let viewer take time — rushing into Stage I = most common cause of poor sessions
  • Fail catch AOL: Monitor must actively listen for analytical labels + intervene immediately — letting AOL run contaminates all data
  • Over-monitoring: Constant interruptions break signal contact — intervene only for AOL, protocol violations, viewer distress
  • Front-loading: Any info about target before session biases data — maintain strict blindness for viewer
  • Dismiss ambiguous: CRV produces descriptive matches not identifications — train viewer to value accurate description over naming

  • remote-viewing — AI self-directed variant for unknown problems w/o preconceptions
  • meditate-guidance — shamatha concentration = foundation of mental stillness for CRV
  • heal-guidance — energy healing + remote viewing share non-local awareness; same coaching
  • forage-plants — detailed sensory obs of plants develops perceptual acuity for Stage II

Dépôt GitHub

pjt222/agent-almanac
Chemin: i18n/caveman-ultra/skills/remote-viewing-guidance
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

Compétences associées

executing-plans

Design

Utilisez la compétence executing-plans lorsque vous disposez d'un plan de mise en œuvre complet à exécuter par lots contrôlés avec des points de contrôle de revue. Elle charge et examine le plan de manière critique, puis exécute les tâches par petits lots (3 tâches par défaut) tout en rapportant la progression entre chaque lot pour une revue par l'architecte. Cela garantit une mise en œuvre systématique avec des points de contrôle de qualité intégrés.

Voir la compétence

requesting-code-review

Design

Cette compétence délègue un sous-agent réviseur de code pour analyser les modifications apportées au code par rapport aux exigences avant de poursuivre. Elle doit être utilisée après avoir terminé des tâches, implémenté des fonctionnalités majeures, ou avant une fusion vers la branche principale. La revue aide à détecter précocement les problèmes en comparant l'implémentation actuelle avec le plan initial.

Voir la compétence

connect-mcp-server

Design

Cette compétence fournit un guide complet permettant aux développeurs de connecter des serveurs MCP à Claude Code via les transports HTTP, stdio ou SSE. Elle couvre l'installation, la configuration, l'authentification et la sécurité pour intégrer des services externes tels que GitHub, Notion et des API personnalisées. Utilisez-la lors de la configuration d'intégrations MCP, de la configuration d'outils externes ou du travail avec le Protocole de Contexte de Modèle de Claude.

Voir la compétence

web-cli-teleport

Design

Cette compétence aide les développeurs à choisir entre les interfaces Web et CLI de Claude Code en fonction de l'analyse des tâches, puis permet une téléportation transparente des sessions entre ces environnements. Elle optimise le flux de travail en gérant l'état et le contexte de la session lors du passage entre le web, la CLI ou le mobile. Utilisez-la pour des projets complexes nécessitant différents outils à diverses étapes.

Voir la compétence