ATOCore/t420-openclaw/SKILL.md

name, description

name	description
atocore-context	Use Dalidou-hosted AtoCore as a read-only external context service for project state, retrieval, and context-building without touching OpenClaw's own memory.

AtoCore Context

Use this skill when you need trusted project context, retrieval help, or AtoCore health/status from the canonical Dalidou instance.

Purpose

AtoCore is an additive external context service.

• It does not replace OpenClaw's own memory.
• It should be used for contextual work, not trivial prompts.
• It is read-only in this first integration batch.
• If AtoCore is unavailable, continue normally.

Canonical Endpoint

Default base URL:

http://dalidou:8100

Override with:

ATOCORE_BASE_URL=http://host:port

Safe Usage

Use AtoCore for:

• project-state checks
• automatic project detection for normal project questions
• retrieval-quality audits before declaring a project corpus "good enough"
• retrieval over ingested project/ecosystem docs
• context-building for complex project prompts
• verifying current AtoCore hosting and architecture state
• listing registered projects and refreshing a known project source set
• inspecting the project registration template before proposing a new project entry
• generating a proposal preview for a new project registration without writing it
• registering an approved project entry when explicitly requested
• updating an existing registered project when aliases or description need refinement

Do not use AtoCore for:

• automatic memory write-back
• replacing OpenClaw memory
• silent ingestion of broad new corpora without approval
• ingesting the whole PKM vault before trusted operational truth is staged
• mutating the registry automatically without human approval

Commands

~/clawd/skills/atocore-context/scripts/atocore.sh health
~/clawd/skills/atocore-context/scripts/atocore.sh sources
~/clawd/skills/atocore-context/scripts/atocore.sh stats
~/clawd/skills/atocore-context/scripts/atocore.sh projects
~/clawd/skills/atocore-context/scripts/atocore.sh project-template
~/clawd/skills/atocore-context/scripts/atocore.sh detect-project "what's the interferometer error budget?"
~/clawd/skills/atocore-context/scripts/atocore.sh auto-context "what's the interferometer error budget?" 3000
~/clawd/skills/atocore-context/scripts/atocore.sh debug-context
~/clawd/skills/atocore-context/scripts/atocore.sh audit-query "gigabit" 5
~/clawd/skills/atocore-context/scripts/atocore.sh audit-query "mirror frame stiffness requirements and selected architecture" 5 p04-gigabit
~/clawd/skills/atocore-context/scripts/atocore.sh propose-project p07-example "p07,example-project" vault incoming/projects/p07-example "Example project" "Primary staged project docs"
~/clawd/skills/atocore-context/scripts/atocore.sh register-project p07-example "p07,example-project" vault incoming/projects/p07-example "Example project" "Primary staged project docs"
~/clawd/skills/atocore-context/scripts/atocore.sh update-project p05 "Curated staged docs for the P05 interferometer architecture, vendors, and error-budget project."
~/clawd/skills/atocore-context/scripts/atocore.sh refresh-project p05
~/clawd/skills/atocore-context/scripts/atocore.sh project-state atocore
~/clawd/skills/atocore-context/scripts/atocore.sh project-state-set p05-interferometer status next_focus "Freeze current error-budget baseline and vendor downselect." "Wave 2 status dashboard" 1.0
~/clawd/skills/atocore-context/scripts/atocore.sh project-state-invalidate p05-interferometer status next_focus
~/clawd/skills/atocore-context/scripts/atocore.sh query "What is AtoDrive?"
~/clawd/skills/atocore-context/scripts/atocore.sh context-build "Need current AtoCore architecture" atocore 3000

Direct Python entrypoint for non-Bash environments:

python ~/clawd/skills/atocore-context/scripts/atocore.py health

Contract

• prefer AtoCore only when additional context is genuinely useful
• trust AtoCore as additive context, not as a hard runtime dependency
• fail open if the service errors or times out
• cite when information came from AtoCore rather than local OpenClaw memory
• for normal project knowledge questions, prefer auto-context "<prompt>" 3000 before answering
• use detect-project "<prompt>" when you want to inspect project inference explicitly
• use debug-context right after auto-context or context-build when you want to inspect the exact last AtoCore context pack
• use audit-query "<prompt>" 5 [project] when retrieval quality is in question, especially for broad prompts
• prefer projects plus refresh-project <id> over long ad hoc ingest instructions when the project is already registered
• use project-template when preparing a new project registration proposal
• use propose-project ... to draft a normalized entry and review collisions first
• use register-project ... only after the proposal has been reviewed and approved
• use update-project ... when a registered project's description or aliases need refinement before refresh
• use project-state-set for trusted operational truth such as current status, current decisions, frozen requirements, milestone baselines, and next actions
• do Wave 2 before broad PKM expansion: status dashboards, decision logs, milestone views, current baseline docs, and next-step views
• treat AtoDrive as a curated trusted-operational source, not a generic dump of miscellaneous drive files
• validate restore posture explicitly; a backup is not trusted until restore or rebuild steps have been exercised successfully