analyticalmonk
UserAn agentic skills framework for creating interactive explainers for a topic, documents or codebase
Categories
Indexed Skills (3)
creating-explainers
Use when creating an interactive educational article, explainer, or distill-style essay - a single self-contained HTML page with hand-built canvas figures the reader can interact with. Covers articles built from user-provided files (paper, blog post, transcript, research report), topic-driven articles needing web research, and the mix of both. Trigger phrases include "make an explainer", "turn this paper into an interactive article", "build a distill-style essay", "explain X visually", or any request to produce an interactive HTML walkthrough with hand-rendered canvas figures. For explaining a codebase or source files, use explaining-codebases instead. Use even when the user describes the goal without naming the format - if they want an interactive, narrative article with figures the reader can play with, this skill applies.
explaining-codebases
Use when creating an interactive explainer about a codebase, repository, or set of source files - an onboarding guide to how a project is structured, or a deep-dive on how a specific algorithm or mechanism is implemented in real code. Trigger phrases include "explain this codebase", "interactive guide to this repo", "walk through how X works in the code", "onboarding explainer for this project", "visualize this architecture". Produces the same single self-contained HTML explainer as creating-explainers, but with code navigation and code-specific figures (architecture diagrams, data-flow, execution traces, annotated code walkthroughs). For a paper, topic, or non-code source, use creating-explainers instead.
fact-checking-explainers
Use before delivering any explainer, and whenever asked to fact-check, verify, or audit an explainer or article against its sources. Trigger phrases include "fact-check this explainer", "verify the claims", "check this article against its sources", "is this accurate", or reaching the end of researching or drafting an explainer. Applies both at research-time (are the gathered sources real and on-point?) and post-draft (does every claim trace to its cited source or, for code, the actual implementation?). Invoked directly or as a required gate by creating-explainers and explaining-codebases.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.