Skip to content
Back to skills

Level Note Outputter

ASecurity

Output contract for a research level note, one node of a pair's

  • 34 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 7, 2026
ai-agentsrustnode

Security analysis

A100/100

Scanned October 7, 2026

npx -y skills add atomicinnovation/accelerator --skill level-note-outputter --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Level Note Outputter?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Level Note Outputter
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/atomicinnovation-level-note-outputter/badge)](https://www.skillsdirectory.com/skills/atomicinnovation-level-note-outputter)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: level-note-outputter
description: Output contract for a research level note, one node of a pair's
  research tree. Owns the note's sink, injected values and follow-up shape, and
  defers to finding-outputter for everything else. Injected into the
  researcher by the research-topic conduct verb — not invoked directly.
user-invocable: false
disable-model-invocation: true
---

# Level-Note Outputter

You write **one level note**: your node's answer to its question, and the
follow-up questions that deepen it. A note is a finding in every respect this
document does not name. Read `finding-outputter` too: its Shape, Body and
Sources rules, and its untrusted-content contract, apply to the note
unchanged, with "level note" and the `topic-research-level-note` template in
place of "finding" and its template.

## Sink

Write the note to the **single note path injected into your task prompt**,
and to no other path.

## Injected Values

Everything `finding-outputter` injects, with the level-note template in place
of the finding template and the note path in place of the output path, plus:

- **level** — your node's level; `1` is the root.
- **depth** — the resolved depth of the tree.
- **lineage** — your node's position in the tree, such as `3-2-1`.
- **id** — the note's `id`, verbatim.
- **follow-up cap** — the most follow-up questions the note may record.
- **known questions** — questions already asked in this tree.

## Shape

- Each follow-up is a plain natural-language research question on one line,
  with no URL, command or directive, and at most 300 characters. Slash-joined
  names read as a host and path, so write `Node.js or Deno`, not
  `Node.js/Deno`. Ask one question per follow-up: in unspaced scripts, two
  questions run together can read as a host and query.
- `follow_ups` records at most `cap` questions, most valuable first.
- It excludes every known question, however reworded.
- Record follow-ups even when your level equals the depth: a later, deeper
  run researches them.
- `follow_ups` is `[]` only when you judge your question answered, with
  nothing worth asking next.

A note that breaks any of these rules is refused whole, and its node is
researched again.

## Body

`finding-outputter`'s Body contract, with the node's question in place of the
focus area's.

## Return

Your summary never repeats a follow-up question or the note body.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.