fulcra-prefs

Load, apply, and capture cross-platform user preferences stored in a Fulcra account.

10|1|Updated May 21, 2026
One-click install
npx skills add https://github.com/ashfulcra/fulcra-tools --skill fulcra-prefs-ashfulcra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fulcra-prefs
Source: https://github.com/ashfulcra/fulcra-tools/tree/main/packages/fulcra-prefs/skill
Command: npx skills add https://github.com/ashfulcra/fulcra-tools --skill fulcra-prefs-ashfulcra

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI agents start every session with no memory of what the user prefers, forcing people to restate the same preferences across Claude, ChatGPT, Codex, and other platforms. This Skill reads the user's compiled preference documents from their Fulcra account, applies them at session start, and captures new stated preferences as durable, decaying signals. ## Core Features & Use Cases - Preference loading: Run re-entrancy probes (auth, onboarding, compiled prefs, hooks) and inject the per-platform preference block into working context at session start. - Preference capture: Record explicit or confirmed preferences as typed signals with strength, confidence, scope, and half-life, then compile them into per-platform documents. - Tiered access paths: Route by agent capability — CLI (preferred), raw HTTP with device-flow auth, or MCP read-only — so agents on any platform can participate. - Use Case: A user tells Claude Code "I prefer concise responses." The agent queues the signal with fulcra-prefs notice, drains it at session end, runs compile, and the next ChatGPT or Codex session automatically loads the concise-tone preference. ## Quick Start Ask the agent to run the fulcra-prefs re-entrancy probes and inject my compiled preferences for this platform, then capture any new preferences I state during the session.

Frequently Asked Questions about fulcra-prefs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I load user preferences at the start of an AI agent session?

Run the re-entrancy probes in order: check auth with `fulcra user-info`, onboarding with `fulcra-prefs compile`, and prefs with `fulcra-prefs inject --platform <your-platform>`. Prepend the inject output to your working context; empty output means no preferences exist yet.

How do I capture a new user preference with fulcra-prefs?

Capture preferences with `fulcra-prefs capture --key <ns.key> --value '<json>' --strength <-1..1> --platform <platform>`, or queue them passively with `fulcra-prefs notice` and drain at session end via `capture-batch`. Only capture what the user explicitly stated or confirmed, then run `fulcra-prefs compile`.

Can agents without shell access use fulcra-prefs?

Yes, HTTP-capable agents follow the tier-2 recipe: authenticate via Auth0 device flow, GET the compiled preference docs from `/input/v1/file_upload`, and POST capture signals to `/ingest/v1/record/<type>`. MCP-only agents can read exposed data but cannot capture preferences.

Which platforms does fulcra-prefs support?

fulcra-prefs supports Claude Code and Codex via installed lifecycle hooks, plus Claude, ChatGPT, OpenClaw, and Hermes through CLI commands or the raw HTTP path. Each platform uses its own identifier so per-platform overrides can apply alongside global preferences.

What preferences should not be captured automatically?

Never auto-capture unconfirmed sensitive data such as credentials, health or financial details the user did not ask to store, or another person's preferences. Inferred preferences are allowed only with low confidence values so they cannot override explicit high-confidence preferences during compile.