hashgraph-online/awesome-codex-plugins / plugins/boshu2/agentops/skills/research
research
VerifiedAnswer one cited question on code, history, claims or patterns. Use when: asked how it works, why it changed, if a claim or done/shipped report holds, or a pattern warrants a rule.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 17.4 KB |
| references/adoption-and-lineage.md | markdown | 2.4 KB |
| references/codebase-recon/codebase-recon.feature | other | 1.8 KB |
| references/codebase-recon/pack-contract.md | markdown | 3.3 KB |
| references/goals.md | markdown | 1.2 KB |
| references/pattern-mining/pack-contract.md | markdown | 2.2 KB |
| references/pattern-mining/pattern-mining.feature | other | 824 B |
| references/research.feature | other | 530 B |
| references/status.md | markdown | 2.0 KB |
| schemas/findings.json | config | 3.3 KB |
| schemas/reality-check-report.v1.schema.json | config | 1.5 KB |
| scripts/claim-audit/validate-output.shexecutable | script | 1.6 KB |
| scripts/codebase-recon/validate-output.shexecutable | script | 19.0 KB |
| scripts/pattern-mining/validate-output.shexecutable | script | 2.1 KB |
| scripts/validate.shexecutable | script | 2.9 KB |
references/goals.md
View on GitHub# Goal measurement
Loaded by [Research](../SKILL.md) in a claimed-state audit when the caller asks
to measure declared goals.
Inspect the declared goals source; prefer `GOALS.md` when it and legacy YAML
both exist (`ao goals` auto-detects `GOALS.md` first). Preserve directive and
gate identities and report each executable check with its actual outcome. Run
the requested `ao goals` command once: `measure --json`, `validate --json`,
`drift`, `history`, `export`, `meta --json`, `scenarios` or `render`.
Inspecting the source needs no `ao`; if `ao` is not on PATH (the plugin does
not ship it), report the command as not run (tool unavailable).
These commands do not edit the goals source, but `measure`, `drift` and
`export` may write best-effort derived snapshots under
`.agents/ao/goals/baselines/`. `render --out <file>` writes a caller-selected
spec; never target the goals source or another non-derived file. Use stdout
when no output file is requested.
Return the command, exit code, goal-level results, aggregate measurement,
missing evidence and checked/not-checked scope. Do not add, remove, prioritize,
migrate or repair goals, or turn a measurement gap into assigned work.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |