Ocas Triage
v1.2.0System scheduler and priority queue manager. Determines what gets attention next across all pending work. Use when prioritizing competing tasks, checking que...
⭐ 0· 115·0 current·0 all-time
byIndigo Karasu@indigokarasu
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description, SKILL.md, README, and references consistently describe a scheduler that maintains a local durable queue and emits signals. There are no unrelated environment variables, binaries, or external endpoints required that would be inconsistent with a local scheduler.
Instruction Scope
The runtime instructions explicitly require writing and appending records under a local .triage directory (queue.jsonl, signals.jsonl, journals, etc.) and expect consumers (Mentor, Dispatch, base agent) to poll or acknowledge signals. This is in-scope for a scheduler, but it does grant the skill the ability to persist scheduling state locally; review whether you are comfortable with the agent process creating and maintaining these files. The SKILL.md does not instruct reading unrelated system files or exfiltrating data.
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is downloaded or written by an installer. Lowest-risk install posture.
Credentials
No required environment variables, credentials, or config paths beyond the .triage directory. The requested access is proportional to a local scheduler: persistent local storage only.
Persistence & Privilege
The skill persists state to the agent filesystem (.triage/) and creates journal files and logs. It does not request always:true or other elevated privileges and claims not to write outside .triage. Confirm your environment's file-permission model and retention policy for these files before enabling.
Assessment
This skill appears to be what it says: a local task scheduler that stores audit logs and emits pickup signals for consumers. Before installing, confirm you are comfortable with the agent creating and maintaining a .triage directory (queue.jsonl, signals.jsonl, journals, etc.) in the agent environment and that other skills or processes will honor the stated boundaries. Also verify that Mentor/Dispatch integrations in your system follow the described protocols (polling and acknowledgments) and that no external network endpoints are added later. If you have strict storage or retention rules, decide where the .triage directory will live and who can read it; otherwise the skill is internally consistent and proportional to its purpose.Like a lobster shell, security has layers — review code before you run it.
latestvk973ck0kmen7svrj8td637mqb18335k2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🔀 Clawdis