templates/skill/SKILL.md
Describe what this skill does, when it should be used, and the kinds of user requests that should trigger it.
npx skillsauth add zoheth/vidya example-skillInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Briefly explain the purpose of the skill in one or two sentences.
Use this skill when:
Describe the first step.
Describe the second step.
references/: optional supporting documentationscripts/: optional helper scriptsassets/: optional templates or static resourcesdevelopment
Explain code through the lens of Naur's "Programming as Theory Building" — deliver the theory, not a behavioral narration. Use when the user says "explain this in non-code terms", "what's the theory here", or invokes /theory explicitly.
development
Co-read research papers with the user using a Socratic, multi-pass methodology. The agent handles all mechanical work — extracting structure, looking up terms, tracing references, generating probing questions, maintaining layered notes — while the user retains all interpretive and critical work (understanding, judgment, "if I were writing this..."). Trigger this skill whenever the user shares a research paper (PDF, arXiv link/ID, or paper title) and signals they want to engage with it deeply — phrases like "help me read this paper", "let's go through this paper", "walk me through [paper]", "I want to understand [paper]", or simply uploads a paper without specifying what they want. Especially well-suited to AI infrastructure, reinforcement learning, and embodied intelligence papers, but the methodology generalizes. Do NOT trigger when the user clearly only wants a one-shot summary or has a single specific factual question about a paper — this skill is for sustained co-reading sessions, not quick lookups.
development
Use this skill when the user wants to genuinely understand unfamiliar code in any of three modes — **orienting** (building a working theory of a codebase, library, project, commit, or PR), **debugging** (tracing a bug or unexpected behavior through unfamiliar code), or **extending** (planning a modification, feature addition, or refactor in code they don't fully own yet). Trigger phrases include "help me understand this code", "walk me through this codebase", "why does this commit do X", "something's broken in this module", "I need to add X to this library", "help me figure out where this bug lives", "explain the design of this library", and similar. **The user's goal is NOT a code summary — it's to grow a working theory in their own head, structured both as an adjudicated set of claims AND as a felt sense of the system's overall shape.** Trigger any time the user wants to "understand", "figure out", "debug", "fix", "extend", "modify", "trace", or "make sense of" some code, project, commit, PR, or bug — even when they don't say "theory". Do NOT use for queries answerable by a single docstring or README line.
development
Extract important questions from GitHub repositories, including issues, pull requests, discussions, and code reviews, and generate Markdown question cards for deep study. Use this skill when the user wants to extract key questions from a repo, mine important technical problems from GitHub threads, or build a study set of high-value questions from open-source projects.