ocas-praxis
Praxis enhances behavioral refinement by recording outcomes, extracting lessons, and applying behavior shifts for continuous improvement.
Install this skill
or
75/100
Security score
The ocas-praxis skill was audited on Sep 25, 2026 and we found 1 security issue across 1 threat category, including 1 critical. Review the findings below before installing.
Categories Tested
Security Issues
critical line 261
Eval function call
SourceSKILL.md
| 259 | - **Large gap backfill (80+ entries) is normal at steady-state** — cron pipelines write ~10 journals/minute. Between dispatch waves (7-8 min apart), expect 50-80 gap entries. This is expected, not a failure. See `references/session-20260629-dispatch-1030Z-praxis-second-wave-gap-backfill.md` |
| 260 | - Cold-start: initialize state with CURRENT timestamp, not epoch |
| 261 | - **Pure eval-registration dispatch (confirmed 2026-06-30T11:25Z):** When ALL `new_files` are already in praxis eval (just missing from dispatch eval) or are prior-wave artifacts, the Praxis pipeline does NOT need to run. Register directly from the dispatch pipeline, advance `last_ingest_run`, do NOT increment `journals_evaluated_count`. See `references/session-20260630-dispatch-1125Z-praxis.md`. |
| 262 | - **CAPTURED_TS calibration (verified 2026-07-10, Mentor 2.8.23):** The light heartbeat did NOT advance `ingest_state.json:last_ingest_run` in this deployment. Before applying the CAPTURED_TS override, check `last_ingest_run` AFTER Mentor runs. If it is unchanged from the pre-Mentor value, run the ingest WITHOUT CAPTURED_TS — mtime discovery still finds the new journals (the override is only needed when the state timestamp actually moved forward). Applying CAPTURED_TS unnecessarily is harmless but adds an avoidable env-var step and a date-format footgun. |
| 263 | - **No `praxis-dispatch` journal from the template (verified 2026-07-10):** `templates/dispatch_ingest_template.py` does not write a `praxis-dispatch-*.json` journal (unlike older production pipelines). The dispatch-output journals to bridge into the DISPATCH eval during third-wave mitigation are therefore: every journal the ingest just evaluated (all of them — the forge-scan output, the mentor-light heartbeat output, and any other cross-skill journals it registered) PLUS the `dispatch-wave-*` journal you write. Do NOT look for or fabricate a `praxis-dispatch` journal; bridge the full set of ingest-evaluated journal_ids instead. |
Scanned on Sep 25, 2026
View Security Dashboard