narrative-io/narrative-skills-marketplace / plugins/narrative-common/skills/generate-rosetta-stone-mappings
generate-rosetta-stone-mappings
VerifiedGenerate, evaluate, and improve Rosetta Stone attribute mappings for a Narrative dataset. Use when: "map this dataset to Rosetta Stone", "suggest normalized attributes for dataset N", "evaluate the mappings on dataset N", "why is this mapping low confidence", "fix this expression", "improve this NQL mapping expression". (narrative-common)
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 16.1 KB |
| SKILL.md.tmpl | other | 13.6 KB |
| references/DATASET_DESCRIBE.md | markdown | 2.6 KB |
| references/HARNESS_FALLBACK.md | markdown | 1.4 KB |
| references/HARNESS_FALLBACK.md.tmpl | other | 937 B |
| references/MODES.md | markdown | 3.2 KB |
references/HARNESS_FALLBACK.md
View on GitHub<!-- AUTO-GENERATED from HARNESS_FALLBACK.md.tmpl — do not edit directly -->
<!-- Regenerate: bun run gen:skill-docs -->
# Harness fallbacks
What to do when `narrative-mcp` is unavailable and when the harness
doesn't expose `AskUserQuestion`.
Never silently degrade. If a tool is unavailable, say so explicitly
in the summary and reduce confidence accordingly.
## `narrative-mcp` unavailable
- Ask the user to paste the dataset's schema + 10-25 sample rows +
the Rosetta Stone attribute IDs they're considering (or to run
`curl https://api.narrative.io/datasets/<id>` and paste the
response).
- With that context pasted in, apply step 4 (the mapping rules) and
step 5 of the procedure manually — you can't validate NQL syntactically without the
server, so add a global warning saying expressions were not
server-validated and confidence is reduced by 10 points across
the board.
- Never silently degrade. If you can't validate, say so explicitly
in the summary.
## "AskUserQuestion" not available
If the harness does not expose `AskUserQuestion` as a named tool
(Claude Code does; most others don't), ask the user the same question
in plain prose — **one question per turn**, never batched — and wait
for a reply before continuing. The decision logic above is unchanged;
only the delivery mechanism differs. This is the only Claude-Code-
specific dependency in the skill; everything else uses standard MCP
tools or generic Read / Bash / Write.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |