owenbush/decodie-skill

decodie-ask

>- Ask a question about an existing Decodie learning entry and get a deeper explanation using the entry content and live source code as context. Read-only — does not create or modify entries.

First seen Jun 11, 2026

Installation

$ npx skills add owenbush/decodie-skill --skill decodie-ask

Also in this package

Other skills from owenbush/decodie-skill.

npx skills add owenbush/decodie-skill

Browse all from owenbush/decodie-skill

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1
License MIT
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0
LicenseMIT
More metadata
author
owenbush
version
1.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,495 B
  • docs SUMMARY.md 209 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 191 installs

SKILL.md

Decodie — Ask Mode

Help the user explore and deepen their understanding of existing learning entries in the .decodie/ directory.

This mode is read-only with respect to .decodie/ data.

Setup

Load rules. Check for ~/.decodie/rules/.md (global) and .decodie/rules/.md (project). Read all .md files found. Treat their content as additional instructions controlling documentation output — tone, language, verbosity, format, audience. Project rules override global rules on conflict. If no rules exist, proceed with defaults.

Entry Resolution

Resolve which entry the question targets using this priority:

  1. Explicit entry ID — If the question contains an entry ID (e.g., entry-1711540000-a1b2), load it directly.
  2. Keyword match — Search active entry titles and topics in index.json. Prefer exact substring matches in titles, then topic tag matches.
  3. Current session default — If no match, default to the most recently created entry in the current session.
  4. No match — If no entries exist or match, tell the user and suggest browsing index.json.

Context Loading

Once the target entry is identified, load:

  • Entry content — Full entry from the session file: explanation, codesnippet, alternativesconsidered, key_concepts.
  • Live source code — For files listed in the entry's references array, read the referenced sections to provide current-state context.
  • External documentation — URLs from external_docs for reference.

Response Instructions

  • Identify the entry — Begin by naming the entry (title and ID).
  • Answer the specific question — Use entry content and live source code as primary context.
  • Go deeper — Don't repeat the entry. Explain underlying concepts, provide examples, clarify trade-offs.
  • Suggest enrichment — If the question reveals a gap in the entry, suggest re-analysis.
  • Stay conversational — Tone of a knowledgeable colleague at a whiteboard.

Important Notes

  • After answering, the interaction is complete. The user can ask again with another question.
  • This mode only reads existing data — it does not generate entries.