Token导航 LogoToken导航

Agent Skill · 研究检索

ocas-custodian(奥卡斯托管人)

ocas-custodian 用于记录任务执行中的错误、用户纠正、经验和能力缺口,适合在 OpenClaw 中希望让 Agent 持续沉淀问题、修正和最佳实践时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

ocas-custodian 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 30,957。

总安装 2,791周安装 114GitHub Stars 公开资料未说明下载 903核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:ocas-custodian(奥卡斯托管人)
来源仓库:https://github.com/indigokarasu/ocas-custodian
安装命令:
openclaw skills install ocas-custodian
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install ocas-custodian

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

自主监控系统运行状况,修复日志错误并执行通宵维护任务。适用于持续保障 OpenClaw 稳定性和技能初始化。安装后可自动注册任务并处理未解决问题。ocas-custodian 属于研究检索类 Skill,可作为该场景下的辅助能力补充。具备较高系统权限,需谨慎配置以避免误删关键数据。建议在沙箱环境测试后再部署到生产节点。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install ocas-custodian;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

ocas-custodian 怎么安装?

在终端执行 openclaw skills install ocas-custodian。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

ocas-custodian 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

ocas-custodian 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

ocas-custodian 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

ocas-custodian 用的人多吗?

公开数据是累计安装 2,791 次,近一周安装 114 次,下载 903 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

ocas-custodian 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。

先想清楚的地方

  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
ocas-custodian

奥卡斯托管人 · 本页

2,791—需要联网MIT-0有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
ocas-custodian
source
https://github.com/indigokarasu/custodian
install
openclaw skill install https://github.com/indigokarasu/custodian
description
Use when checking system health, fixing log errors, reviewing cron failures, initializing skills, registering missing background tasks, or running overnight maintenance. Trigger phrases: 'check system health', 'fix log errors', 'why is X failing', 'initialize skills', 'clean up errors', 'show open issues', 'what time does custodian run', 'update custodian'. Do not use for skill OKR analysis (use Mentor/Corvus), skill rebuilding (use Forge), knowledge graph queries (use Elephas), social graph queries (use Weave), or research tasks (use Scout/Sift).
metadata
{"openclaw":{"emoji":"🧹"}}

Custodian

Custodian detects, classifies, and repairs OpenClaw operational failures autonomously during quiet hours so the user wakes to clean logs, initialized skills, and registered background tasks -- surfacing only what it could not fix.

When to use

  • Asked to check system health, fix log errors, review cron failures
  • Asked to initialize skills or register missing background tasks
  • Asked why OpenClaw or a specific skill is failing
  • Running overnight maintenance or a system audit
  • Invoked automatically via heartbeat or cron

Responsibility Boundary

Owns: gateway log scanning and error fingerprinting, cron job registry health, skill journal completeness, OCAS data directory health, skill initialization, background task conformance, Tier 1 auto-repair, activity model and schedule optimization, escalation signaling, fix effectiveness tracking.

Does not own: OKR trend analysis (Corvus, Mentor), skill design evaluation or rebuilding (Mentor, Forge), behavioral lesson extraction (Praxis), briefing delivery (Vesper), entity knowledge (Elephas), social graph (Weave). Never modifies any file inside a skill package directory.

Optional Skill Cooperation

  • Vesper -- writes InsightProposals to ~/openclaw/data/ocas-vesper/intake/ after deep scans. Without Vesper, issues stay in issues.jsonl.
  • Mentor -- journals tagged escalation_needed: true are readable by Mentor heartbeat. Without Mentor, escalated issues await manual review.
  • Corvus -- if installed, reads Corvus observation journals for routine_prediction InsightProposals. Blended 70% Corvus / 30% own model. Functions normally without Corvus.

Commands

  • custodian.init -- create storage, register background tasks idempotently, copy bundled plan to Mentor plans dir, build initial activity model
  • custodian.scan.light -- tail gateway log (last 100 lines), check cron registry, retry open fix_attempted_failed items, check for uninitialized skills, write Observation Journal
  • custodian.scan.deep -- full sweep: all light steps + full JSONL scan, doctor diagnostic, journal health, skill conformance, skill init pass, activity model rebuild, schedule optimization, repair pass, web search pass, escalation pass, report, Vesper signal
  • custodian.verify {fix_id} -- verify fix outcome, update record, escalate if failed twice
  • custodian.repair.auto -- apply all pending Tier 1 fixes from last scan
  • custodian.repair.plan -- generate structured repair plan for Tier 2/3 issues
  • custodian.issues.list -- list open issues with tier, status, age, recurrence
  • custodian.issues.resolve {issue_id} -- mark issue resolved manually
  • custodian.status -- emit SkillStatus JSON
  • custodian.schedule.show -- display current and target scan schedule with optimization confidence
  • custodian.update -- pull latest from GitHub source (preserves journals and data)

Execution Loop -- Light Scan

Runs every heartbeat. Must be fast (seconds). No web search, doctor, or report.

  1. Read ~/.openclaw/cron/jobs.json -- find jobs with enabled: false that were previously enabled in skill_conformance.jsonl. Re-enable (Tier 1).
  2. Tail /tmp/openclaw/openclaw-YYYY-MM-DD.log -- last 100 lines. Fingerprint ERROR entries against references/known_issues.json then learned_issues.jsonl. Apply Tier 1 fixes. Open issues for Tier 3/4.
  3. Check issues.jsonl for status: fix_attempted_failed. Retry Tier 1 up to 3 times before escalating.
  4. Check for uninitialized skills (data dir or config.json missing). Initialize immediately.
  5. Write Observation Journal.

Execution Loop -- Deep Scan

Runs on optimized 6-hour cron schedule. Isolated session, lightContext.

  1. Load context -- own journals (7 days), fix_effectiveness.jsonl. Identify recurring fingerprints, known-failed fixes, already-searched queries.
  2. Collect -- full day gateway log, cron run logs, skill journals from scan window, all OCAS data dirs, openclaw doctor --non-interactive.
  3. Fingerprint + classify -- match against references/known_issues.json then learned_issues.jsonl. Unknowns default Tier 3.
  4. Rebuild activity model -- parse gateway log message.processed events (source: user vs source: cron|heartbeat). Blend Corvus if present (70/30). Update activity_model.json. Determine current_state.
  5. Optimize schedule -- score current schedule against activity model. If score < 6, compute better schedule. Shift max 30 min per slot. Update cron if changed.
  6. Skill conformance -- scan installed skills, parse ## Background tasks, cross-reference against openclaw cron list and HEARTBEAT.md. Register missing (Tier 1). Surface mismatches (Tier 2).
  7. Skill init pass -- initialize any skill missing data dir, config.json, or journal dir.
  8. Repair pass -- all Tier 1 fixes. Activity-aware: if active, only urgent fixes (failure in last 5 min); defer rest. Register verify jobs. Execute prior deferred fixes if now quiet.
  9. Web search pass -- for unknown fingerprints with recurrence_count >= 1, run next mutation query (see Web Search Protocol).
  10. Escalation pass -- Tier 3/4 open issues: write InsightProposal to Vesper intake. Tag journal escalation_needed: true.
  11. Report -- ~/openclaw/data/ocas-custodian/reports/YYYY-MM-DD-HHMM.md. If all clean and previous cycle also clean: suppress Vesper signal.
  12. Write journal -- Action (if fixes applied) or Observation (scan-only).

Fix Safety Envelope

Every autonomous fix must satisfy all four:

  1. Non-destructive -- no delete, overwrite, or permanent alteration
  2. Reversible -- pre-fix state restorable without backup
  3. Minimal scope -- smallest surface to address symptom
  4. Functionality-preserving -- cannot reduce capability

Hard constraints: never modify skill package files, never delete files, never modify another skill's data dir, never restart gateway, never change user settings without acknowledgment.

Tier Classification

TierLabelAction
1Auto-fixApply immediately, register verify job, log fix record
2PlanSurface with proposed change, do not apply
3EscalateWrite to escalation journal + Vesper intake, invoke Mentor plan if available
4Alert onlyCannot fix -- surface with diagnostics

High-recurrence override: if recurrence_after_fix / successes > 0.5, auto-promote next occurrence from Tier 1 to Tier 3.

Tier 1 Auto-Fix Registry

All Tier 1 fixes defined in references/known_issues.json. Read at start of every scan. Pre-seeded fingerprints:

FingerprintFix
oc_cron_disabled_transientRe-enable cron job
oc_cron_stuck_missedForce-run missed job
oc_intake_dir_missingCreate directory
oc_journal_dir_missingCreate directory
oc_skill_data_dir_missingCreate directory + default config.json
oc_jsonl_oversizedRotate with date suffix
oc_jsonl_malformed_linesQuarantine to .error file
oc_gateway_token_missingopenclaw doctor --generate-gateway-token
oc_oauth_token_expiringOAuth refresh (token still valid, expiry <= 12h)
oc_background_task_missingRegister cron or heartbeat entry per SKILL.md
oc_skill_uninitializedCreate storage dirs, default config, empty JSONL

Fix Verification

Every Tier 1 fix registers a one-shot cron job custodian:verify:{fix_id} with delay per fix type (2-15 min). On verification failure: set outcome: fix_attempted_failed. Two consecutive failures: promote to Tier 3. Fix records appended to fixes.jsonl with fix_id, issue_id, command, reversibility, pre_fix_state, post_fix_state, outcome.

Post-Fix Cleanup

After successful verification, run fix-specific cleanup (check backoff, confirm next run, validate permissions). Record in cleanup_events.jsonl.

Skill Conformance Checking

On every deep scan: scan ~/.openclaw/workspace/skills/, parse each SKILL.md ## Background tasks, cross-reference against openclaw cron list and HEARTBEAT.md. Missing tasks: Tier 1 fix. Schedule mismatches: Tier 2. Orphaned custodian:* jobs: Tier 2. Write skill_conformance.jsonl per skill.

Skill Initialization

Uninitialized when: data dir missing, config.json missing, or journal dir missing. Sequence (additive only, never overwrite):

  1. Create ~/openclaw/data/{skill-name}/ if missing
  2. Write default config.json with ConfigBase fields -- only if absent
  3. Create ~/openclaw/journals/{skill-name}/ if missing
  4. Create declared intake dirs if missing
  5. Run conformance check for background tasks
  6. Register missing tasks (Tier 1, subject to parameter availability)
  7. Register verify job (15 min delay)
  8. Append DecisionRecord

Do not run the skill's own {skill}.init command.

Activity Model

Maintained in activity_model.json, rebuilt every deep scan from 14-day gateway log window. Confidence per hour: active_days / total_days (>= 0.75 high, >= 0.40 med, < 0.40 low). current_state: active if hour confidence >= med and in active window, else quiet.

Repair rules: quiet = all Tier 1; active = urgent only (failure in last 5 min), defer rest; low confidence = execute but suppress noisy effects. Cold start: 01:00, 07:00, 13:00, 19:00 PT. Optimization begins after 7 days.

Schedule Optimization

Exactly 4 runs/day, min 2h gap, max 30 min shift per cycle. Score each run time against activity model (-2 to +2 per slot, max +8). If score >= 6: no change. If < 6: find candidate maximizing score, shift toward target. Update cron registration.

Confidence gate: high = optimize freely, med = only if score <= 2, low = hold.

Web Search Protocol

Fire when: fingerprint unknown, recurrence increased since last search, last search not actionable, not escalated/suppressed, < 5 attempts.

Query mutation sequence: (1) {error} openclaw, (2) {error} {tech_context}, (3) {error_pattern} fix, (4) {component} {failure_mode}, (5) {failure_mode} root cause diagnosis.

On actionable result: attempt fix, append to learned_issues.jsonl if successful. On no result: record and continue mutation on next recurrence.

Self-Improvement

fix_effectiveness.jsonl: per-fingerprint tracking of attempts, successes, failures, recurrence. High-recurrence escalation: recurrence_after_fix / successes > 0.5 promotes to Tier 3.

Custodian OKRs (every journal): success_rate, issues_detected, issues_auto_fixed, fix_success_rate, mean_time_to_fix_ms, open_residuals, escalations, high_recurrence_fingerprints, skills_initialized, background_tasks_registered, schedule_score, journal_completeness.

Escalation Path

Tier 3: append status: escalated to issues.jsonl, tag journal escalation_needed: true, write InsightProposal (anomaly_alert) to ~/openclaw/data/ocas-vesper/intake/. If Mentor present, note mentor.plan.run custodian-repair --arg issue_id={id} available.

Clean state: zero open issues + previous cycle clean = suppress Vesper signal. First run of day or issues now resolved = emit clean bill of health.

Journal Outputs

  • Observation Journal -- scan-only runs, no fixes applied
  • Action Journal -- any run with Tier 1 fixes or cron registrations

Both include full Custodian OKR block. Path: ~/openclaw/journals/ocas-custodian/YYYY-MM-DD/{run_id}.json

Background tasks

JobMechanismScheduleCommand
custodian:lightheartbeatevery heartbeat cyclecustodian.scan.light
custodian:deepcronoptimized 6h (initial: 0 1,7,13,19 * * * PT)custodian.scan.deep
custodian:updatecron0 0 * * * (midnight daily)Self-update from GitHub source

Registration during custodian.init (idempotent -- check openclaw cron list first).

Storage Layout

~/openclaw/data/ocas-custodian/
  config.json                  -- ConfigBase + scan_window_minutes, optimization settings
  issues.jsonl                 -- issue lifecycle records
  fixes.jsonl                  -- fix attempt records with pre/post state
  cleanup_events.jsonl         -- post-fix cleanup records
  fix_effectiveness.jsonl      -- per-fingerprint outcome tracking
  learned_issues.jsonl         -- runtime-learned fingerprints from web search
  skill_conformance.jsonl      -- per-skill background task conformance
  activity_model.json          -- rolling 14-day activity pattern (rebuilt each deep scan)
  deferred_fixes.jsonl         -- fixes queued for next quiet window
  schedule_state.json          -- current/target schedule, optimization history
  decisions.jsonl              -- DecisionRecord entries
  reports/
    YYYY-MM-DD-HHMM.md         -- deep scan summaries (7-day retention)
~/openclaw/journals/ocas-custodian/
  YYYY-MM-DD/{run_id}.json

Support File Map

FilePurposeWhen to read
references/known_issues.jsonPre-seeded fingerprint registry with tier, fix, reversibilityStart of every scan before classifying errors
references/plans/custodian-repair.plan.mdMentor Workflow Plan for Tier 3 multi-step repairCopied to Mentor plans dir during init; referenced in escalation

平台分布

OpenClaw

90.59%
按下载量换算818

安全审计

VirusTotal

可疑

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills