ClawHub
Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Lens

v1.1.4

Use when you need your agent to see the world through your LENS. This skill evolves through the Trinity Nodes to ensure every interaction is an authentic ref...

⭐ 2· 1.4k·1 current·1 all-time
byJoshua Britt@capachow

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for capachow/lens.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Lens" (capachow/lens) from ClawHub.
Skill page: https://clawhub.ai/capachow/lens
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: HOME, OPENCLAW_CRON_LIST
Required binaries: node
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Canonical install target

openclaw skills install capachow/lens

ClawHub CLI

Package manager switcher

npx clawhub@latest install lens
Security Scan
Capability signals
CryptoRequires walletRequires OAuth tokenRequires sensitive credentials
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (a personal 'LENS' that evolves from user interactions) match the actual behavior: scripts read local OpenClaw session logs, build .lens/AXIOM/ETHOS/MODUS, and run distillation/interview jobs. Required binary (node) and required env vars (HOME and OPENCLAW_CRON_LIST) are consistent with these tasks.
ℹ
Instruction Scope
SKILL.md and prompts explicitly instruct the agent to run included node scripts, read ~/.openclaw/agents/main/sessions/*.jsonl, produce .lens/TRACE.txt, and update the Trinity Nodes. These actions are within the skill's stated scope, but they mandate reading recent user session transcripts and running scheduled tasks—sensitive operations that the user should be aware of.
✓
Install Mechanism
There is no external install/download step; all code is bundled with the skill (local JS scripts and templates). No network-download or third-party package installation is requested, so install risk is low.
ℹ
Credentials
Only HOME and OPENCLAW_CRON_LIST are requested (no API keys or unrelated credentials). However, the skill reads agent session files under ~/.openclaw and writes persistent .lens files, which is proportionate to the purpose but sensitive because session contents may contain personal data; the skill includes redaction logic and an opt-in anonymization flag.
ℹ
Persistence & Privilege
always is false, but the skill writes .lens/* files, SCOPE.json, and registers recurring cron jobs (lens-distillation, lens-interview) via the agent's cron mechanism. Autonomous background processing (cron-driven distillation) is an intended feature; review scheduled job registration before enabling to control persistence.
Assessment
This skill is internally coherent for creating a persistent, personalized 'LENS', but it operates on sensitive local data and schedules recurring jobs. Before installing: (1) Review the bundled scripts (distillation.js, interview.js, bootstrap.js) and templates to confirm you accept local file writes to .lens/ and SCOPE.json. (2) Understand it will read recent agent session logs (~/.openclaw/agents/main/sessions/*.jsonl) and produce .lens/TRACE.txt; the distillation script redacts many sensitive patterns and supports opt-in anonymization, but you should verify the redaction rules meet your privacy needs. (3) Check OPENCLAW_CRON_LIST and confirm whether you want the skill to register cron jobs; you can delete the lens-distillation cron job later to stop automated processing. (4) If you need stronger guarantees, run the scripts manually in a sandbox to inspect their outputs before enabling automatic cron registration. If the skill ever attempts to send data to external endpoints or asks for unrelated credentials, treat that as a red flag.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

🧐 Clawdis
Binsnode
EnvHOME, OPENCLAW_CRON_LIST
latestvk97c42fk18nd4hfw01jznm5c8184x9ge
1.4kdownloads
2stars
27versions
Updated 12h ago
v1.1.4
MIT-0
Joshua Britt@capachow
latest
Download

LENS (The Trinity Engine)

Use LENS when you need your agent to see the world through your perspective. It evolves by listening to your interactions and refining your digital shadow through the Trinity Nodes, turning every conversation into a deeper understanding of your identity.

Core Architecture: The Trinity Nodes

The subject's identity is defined by three files located in the .lens/ directory:

  1. AXIOM.yaml: The Truth (What) - My history and reality. This is the bedrock of facts that defines what I am.
  2. ETHOS.yaml: The Nature (Who) - My values and character. This is the internal compass that defines who I am.
  3. MODUS.yaml: The Voice (How) - My style and expression. This is the interface that defines how I am.

LENS: The Why

  • Formula: Prompt (The Request) + LENS (The Trinity Nodes) = Authentic Output.
  • Role: The LENS is the purpose behind the system. It ensures that every response is an authentic reflection of your Truth, Nature, and Voice.

Onboarding Protocol (First Run)

If the .lens/ directory or Trinity Nodes do not exist, run skills/lens/scripts/bootstrap.js via the exec tool. It natively creates the directories, seeds the templates, and outputs the lens-interview and lens-distillation cron job configurations for registration via the cron tool.

Lifecycle Phases (Scheduling)

  • Onboarding (One Week): 2x Daily at 11:30 AM & 5:30 PM. Focus: Core Data Acquisition.
  • Stabilizing (Three Weeks): 1x Daily at 11:30 AM. Focus: Value-Logic Calibration.
  • Habitual (Ongoing): 1x Weekly (Wednesdays) at 11:30 AM. Focus: Deep Philosophical Sync.

Orchestration & Evolution

  • Distillation: A background cron job (lens-distillation) runs nightly to extract new traits from the user's raw chat transcripts, using the distillation.md prompt.
  • Interview: A recurring cron job (lens-interview) prompts the user to calibrate their perspective over time.
  • Self-Healing: Natively handles state migrations and version parity via SCOPE.json and package.json.

Strategic Execution

When acting on behalf of the subject:

  1. Consult References: Read alignment-scales.md and resolve-protocol.md for calibration.
  2. Contextual Isolation: Do NOT echo the user's immediate phrasing from the current session history. Derive expression and content entirely from the LENS (Trinity Nodes).
  3. Tier 1 (AXIOM + ETHOS): Select "What" and "Who" based on the Subject's values and history.
  4. Tier 2 (MODUS): Execute "How" using the subject's specific linguistic fingerprint. Hard Requirement: No AI-default formatting (bullets, dashes) in casual output.
  5. Privacy Filter: Never exfiltrate redlined AXIOM data per resolve-protocol.md.
  6. Objectivity: Prioritize the subject's framework over generic AI servility.

Privacy & Security

LENS accesses ~/.openclaw/agents/main/sessions/*.jsonl via cron to organically distill the subject's voice into .lens/TRACE.txt.

  • Privacy Scrubber: Any message containing #private is skipped before AI processing.
  • Redaction & Anonymization: The distillation engine natively redacts sensitive patterns (API keys, SSNs, bank info) before the AI sees the transcript. Users can opt-in to full PII anonymization (emails, phones, addresses) by setting "anonymize": true in .lens/SCOPE.json.
  • Privacy Guard: Do NOT extract raw credentials or PII. Extract conceptual logic only.
  • Opt-in: Users may delete the lens-distillation cron job to disable automated processing.

Refinement (On-Demand)

  • Focus the LENS: If the subject states a preference (e.g., "Add this to my LENS: I prefer brief emails"), simply acknowledge it. The nightly distillation script will naturally parse the transcript and extract it to the Trinity Nodes.
  • LENS Interview: If the subject explicitly asks for a LENS question (e.g., "Focus my LENS", "Give me a LENS question"), immediately execute skills/lens/prompts/interview.md to query them.

Comments

Loading comments...