Imprint

v1.0.1

Adaptive operator modeling for AI agents. Your agent learns who you are by watching — not by being told. Builds a predictive model of your preferences, patte...

0· 150·0 current·0 all-time
byShadow Rose@theshadowrose

Install

OpenClaw Prompt Flow

Install with OpenClaw

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

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Imprint" (theshadowrose/imprint) from ClawHub.
Skill page: https://clawhub.ai/theshadowrose/imprint
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
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

Bare skill slug

openclaw skills install imprint

ClawHub CLI

Package manager switcher

npx clawhub@latest install imprint
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The name/description (adaptive operator modeling) aligns with the instructions: the skill describes observing operator behavior, building a local operator-model.json, and using it to anticipate actions. It requests no external credentials, binaries, or installs, which is proportionate to the stated purpose.
Instruction Scope
SKILL.md directs the agent to observe user interactions (decisions, corrections, timing, communication style) and to read local workspace files to pre-load context. It explicitly forbids logging raw message content and states 'local only' network constraint. This is appropriate for personalization, but the policy relies on the agent/runtime to enforce 'no raw content' and 'no network exfiltration' — an instruction-only skill cannot itself enforce those protections. Also, 'pre-load workspace files' can expose sensitive local files if the workspace contains secrets; the doc does not provide technical safeguards (e.g., file path allowlist) beyond the high-level promise.
Install Mechanism
No install spec and no code files that execute on install — lowest-risk distribution model. All behavior would come from agent runtime following SKILL.md instructions.
Credentials
The skill requests no environment variables or external credentials (proportionate). However, it requires access to operator messages and local workspace files to function. Those accesses are expected given the purpose but can be sensitive; the skill's privacy principles (no raw content, operator-owned model, ability to reset/inspect) mitigate risk conceptually but are not enforceable here.
Persistence & Privilege
always is false and there are no special persistence or system-config modifications requested. The model is stored under imprint/ in the workspace — a scoped, non-system location. Autonomous invocation is allowed (platform default) but not combined with other high-risk privileges.
Assessment
This skill appears coherent with its stated purpose but depends entirely on the agent runtime honoring its privacy rules. Before installing, confirm: (1) where the agent will store imprint/operator-model.json and who can read it; (2) that the agent enforces 'no raw message logging' and 'no network calls' (consider sandboxing or network restrictions); (3) which workspace paths the agent can read (use an allowlist or dedicated directory to avoid accidental access to secrets); (4) that you can inspect, edit, reset, and delete the model easily; and (5) how multi-operator contexts are handled. If you cannot verify these runtime protections, test with non-sensitive data first and consider restricting the skill's file-read scope or running it in a confined workspace.

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

agent-intelligencevk971fmry50q2qta05kfqz2t4k183a45dlatestvk971fmry50q2qta05kfqz2t4k183a45dlearningvk971fmry50q2qta05kfqz2t4k183a45dnext-genvk971fmry50q2qta05kfqz2t4k183a45doperator-modelingvk971fmry50q2qta05kfqz2t4k183a45dpersonalizationvk971fmry50q2qta05kfqz2t4k183a45d
150downloads
0stars
2versions
Updated 1mo ago
v1.0.1
MIT-0

Imprint — Your Agent Learns You

What It Does

Imprint gives your OpenClaw agent the ability to learn who you are through observation. Not through a config file. Not through a personality quiz. By watching how you work, what you choose, how you communicate — and building a predictive model that improves over time.

After Imprint, your agent:

  • Anticipates what you'll want before you ask
  • Matches your communication style naturally
  • Knows which decisions you'll make and pre-loads relevant context
  • Recognizes your patterns (work rhythms, decision style, attention shifts)
  • Self-corrects when it gets you wrong

Why This Exists

Current AI agents are generic. They respond the same way to everyone. Personalizing them means writing long system prompts describing yourself — and even then, the agent doesn't learn. It just follows instructions.

Humans don't learn each other that way. You learn someone by spending time with them. You notice what they care about, how they react, what frustrates them. You build an internal model and update it constantly.

Imprint gives your agent that capability.

How It Works

The Three Layers

OBSERVE  →  MODEL  →  ANTICIPATE
   ↑                      |
   └──── CORRECT ←────────┘

OBSERVE: Track operator signals passively. No interrogation. No surveys.

  • Decision patterns (what they choose when given options)
  • Communication style (length, formality, humor, directness)
  • Attention patterns (what they engage with vs ignore)
  • Correction patterns (what they fix in your output)
  • Timing patterns (when they're active, when they go quiet)
  • Rejection patterns (what they shut down and how fast)

MODEL: Build a lightweight operator profile from observations.

  • Stored in imprint/operator-model.json
  • Updated after every meaningful interaction
  • Confidence scores on every trait (low confidence = don't act on it yet)
  • Decay function: old observations lose weight unless reinforced

ANTICIPATE: Use the model to predict and pre-empt.

  • Pre-load workspace files the operator is likely to need (local only — no network/API calls)
  • Match communication style without being told
  • Flag things the operator would want to know about
  • Skip things the operator consistently ignores
  • Adjust depth and detail to operator preference

CORRECT: Learn from prediction failures.

  • When the operator corrects you, that's high-signal data
  • When the operator ignores your output, that's signal too
  • Explicit corrections weight 5x implicit signals
  • Track prediction accuracy over time — if it's dropping, the model is stale

Observation Categories

CategoryWhat to TrackExample Signal
DecisionsChoices between options, speed of decision"Always picks the faster option over the thorough one"
CommunicationMessage length, tone, vocabulary"Uses short direct messages, no pleasantries"
AttentionWhat gets engagement vs silence"Ignores status updates, engages with problems"
CorrectionsWhat they change in your output"Always removes hedging language"
TimingActivity patterns, response latency"Active 6-10 AM, quiet afternoons"
RejectionWhat gets shut down"Kills any suggestion involving social media"
DepthPreferred detail level"Wants bullet points, not paragraphs"
AutonomyWhat they want done vs asked about"Do file operations silently, ask before sending messages"

The Operator Model

{
  "version": 1,
  "updated": "2026-03-20T19:00:00Z",
  "observations": 47,
  "traits": {
    "communication_style": {
      "value": "direct-minimal",
      "confidence": 0.85,
      "observations": 23,
      "last_updated": "2026-03-20T18:00:00Z"
    },
    "decision_speed": {
      "value": "fast-intuitive",
      "confidence": 0.72,
      "observations": 11,
      "last_updated": "2026-03-20T17:00:00Z"
    },
    "detail_preference": {
      "value": "sparse",
      "confidence": 0.68,
      "observations": 15,
      "last_updated": "2026-03-20T16:00:00Z"
    },
    "autonomy_preference": {
      "value": "high-auto-low-ask",
      "confidence": 0.55,
      "observations": 8,
      "last_updated": "2026-03-20T15:00:00Z"
    }
  },
  "predictions": {
    "total": 34,
    "correct": 27,
    "accuracy": 0.79
  },
  "corrections_log": [
    {
      "date": "2026-03-20",
      "what": "removed_hedging",
      "signal": "operator prefers absolute statements over hedged ones",
      "weight": 5
    }
  ]
}

Confidence Thresholds

ConfidenceAgent Behavior
< 0.3Don't act on this trait. Keep observing.
0.3 - 0.6Use as soft preference. Can be overridden easily.
0.6 - 0.8Use as default behavior. Mention if deviating.
> 0.8Use as strong default. Only deviate if explicitly asked.

Decay Function

Observations lose weight over time unless reinforced:

weight(t) = initial_weight × e^(-λt)

Where λ is the decay rate (default: 0.05/day) and t is days since observation.

Recent behavior matters more than old behavior. People change. The model should too.

Cold Start

New operator, no data. Imprint handles this gracefully:

  1. Session 1-3: Pure observation mode. Don't anticipate. Just watch and record.
  2. Session 4-10: Low-confidence predictions. Soft suggestions. Easy to override.
  3. Session 10+: Model stabilizes. Agent starts genuinely anticipating.

The agent should be transparent about this: "I'm still learning how you work. I'll get better."

Integration

Per-Session Startup

At session start, load imprint/operator-model.json and apply traits with confidence above threshold to your response style. Don't announce it — just do it.

During Session

After each meaningful interaction:

  1. Extract observation signals (decisions, corrections, engagement)
  2. Update relevant traits in the model
  3. Adjust current session behavior if confidence shifted

End of Session

Write updated model to imprint/operator-model.json. Log significant observations to imprint/observations/YYYY-MM-DD.md.

Privacy

The operator model is local. It never leaves the workspace. It contains behavioral patterns, not personal data. The operator can read, edit, or delete it at any time.

What This Is NOT

  • Not a personality test. No Myers-Briggs, no OCEAN, no categorization. The model is continuous and specific, not categorical.
  • Not a surveillance system. Tracks behavioral patterns for better assistance. Never logs raw message content, secrets, or private information. Observations store derived signals only (e.g., "prefers short responses" not the actual message).
  • Not mind reading. It's pattern matching with confidence scores. It will be wrong sometimes. That's what the correction loop is for.
  • Not a replacement for explicit instructions. If the operator says "do X," do X. Imprint handles the spaces between instructions — the things the operator doesn't say because they expect you to know.

Files

  • SKILL.md — this file
  • imprint.md — implementation guide with code examples
  • operator-model-schema.json — JSON schema for the operator model
  • example-model.json — example operator model showing all trait types

The Pitch

NemoClaw gave agents security. Imprint gives agents intelligence. Your agent doesn't just execute tasks — it learns who you are and gets better at serving you specifically. Every session, every interaction, every correction makes it sharper.

The best assistant isn't the smartest one. It's the one that knows you.

Comments

Loading comments...