map_skill

Overview

This skill applies a specified operation to every Note inside a Collection and returns a Collection of the results. It enforces type contracts so the input target must be a Collection and the operation must be a valid tool or primitive. The returned Collection contains only successful, non-null results by default.

How this skill works

You supply a Collection as target and an operation name or operation descriptor. The skill runs the operation once per Note in the Collection and assembles Notes containing each operation result. By default it filters out null or failed results unless configured otherwise. Some primitives and control-flow or discovery tools are intentionally unsupported because they operate on Collections or external state.

When to use it

• Apply a transformation or analysis to every Note in a Collection (e.g., annotate, summarize, translate).
• Batch-run a Note-level primitive across a set of notes and collect successful outputs.
• Materialize per-note results into a new Collection for downstream processing.
• Filter out failed or null outputs while preserving successful operation results.
• Avoid when the operation expects a Collection or when running discovery/persistence primitives.

Best practices

• Always provide a Collection for target; single Note or other types will violate the contract.
• Choose Note-level primitives (tool/primitive) rather than Collection-only primitives.
• Set explicit parameters required by the chosen operation; missing params cause failures.
• Treat an empty returned Collection as expected: it means no successful results, not an error.
• Avoid using operations like load on already-materialized search results because they return empty by design.

Example use cases

• map a summarization primitive across a Collection to produce a Collection of summaries.
• Apply a language-detection tool to each Note to tag notes by language.
• Run a redaction or PII-scrubbing operation on every Note and gather cleaned results.
• Convert each Note's content format (e.g., HTML→markdown) and collect converted Notes.
• Execute a validation primitive to filter out invalid notes while keeping valid ones.