radar-init

Included with Lifetime

$97 forever

Scaffold radar/freshness sidecars for research-corpus REFs. Pulls title/authors from the citation sidecar and GRADE from the analysis doc, defaults the refresh cadence from GRADE and the cluster from a corpus-local map, and stamps documentation/radar/REF-XXX-radar.md. Runs via `aiwg corpus radar-init`.

Writing & Docs

What this skill does


# Radar Init

Scaffold a radar/freshness sidecar for a REF. The radar sidecar tracks GRADE
re-assessment, refresh cadence, and signal-gathering history for a paper —
the read side (`by-grade`, `radar-stale-queue`, `by-trajectory` views) is
rendered by `aiwg index build` (#1492); this skill creates the sidecars those
views consume.

## How to run

```bash
aiwg corpus radar-init --ref REF-614                 # dry-run (prints what it would write)
aiwg corpus radar-init --ref REF-614 --write         # actually write the sidecar
aiwg corpus radar-init --ref REF-614 --cadence annual --cluster vla-robotics --write
aiwg corpus radar-init --all-missing --write         # every REF with a citation sidecar but no radar
```

- **Dry-run by default.** Add `--write` to create files. Existing radars are skipped.
- **Cadence** defaults from the analysis doc's GRADE: A→quarterly, B/C→biannual,
  D→on-demand. Override with `--cadence monthly|quarterly|biannual|annual|on-demand`.
- **GRADE** is read from the analysis doc (`documentation/references/REF-XXX-*.md`):
  the `**Quality**: A-` form the canonical/expanded reference templates use, or a
  `**GRADE:** A` form. The +/- sign is preserved.
- **Cluster** is resolved from the corpus-local cluster map (below). Override with `--cluster`.

## Cluster map (corpus-local, no hardcoded ranges)

Cluster tagging is data-driven: create `documentation/radar/clusters.yaml` in the
corpus mapping cluster tags to REF-number singletons and inclusive ranges:

```yaml
self-evolving-agents:
  - "599"
  - "615-619"
pid-control:
  - "600-605"
vla-robotics:
  - "629-635"
```

If the file is absent, scaffolded radars get no cluster (you can set `--cluster`
explicitly). The literal REF ranges live in the corpus, never in AIWG.

## Corpus root

The corpus root resolves as `AIWG_CORPUS_ROOT` env > `research.corpusRoot` in
`.aiwg/aiwg.config` > the current directory (#1497) — same as `aiwg index build`.

## Triggers

- "scaffold a radar for REF-XXX"
- "create radar sidecars for all missing refs"
- "init the freshness tracker for this paper"
- `/radar-init`

## References

- @$AIWG_ROOT/src/artifacts/corpus-tools/radar-init.ts — implementation
- @$AIWG_ROOT/agentic/code/frameworks/research-complete/templates/radar-sidecar.md — sidecar template
- radar-status / radar-report skills — the report side

Files: 1

Size: 2.8 KB

Complexity: 13/100

Category: Writing & Docs

Source: https://github.com/jmagly/aiwg/tree/main/agentic/code/frameworks/research-complete/skills/radar-init

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts