菜单
Systematic Emacs Lisp API discovery before implementation. Uses describe-function, describe-variable, apropos, find-function, and find-library to understand APIs before writing code. Redirects from trial-and-error to systematic discovery.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | elisp-discover |
| description | Systematic Emacs Lisp API discovery before implementation. Uses describe-function, describe-variable, apropos, find-function, and find-library to understand APIs before writing code. Redirects from trial-and-error to systematic discovery. |
| version | 1.0.0 |
| summary | Before writing Elisp code against an unfamiliar API, systematically discover its interface: signature, docstring, source, callers, and related symbols. Use Emacs built-in introspection (describe-, apropos, find-) instead of guessing or making multiple correction passes. |
| author | AI (integrated from clj-native-agent clj-discover pattern) |
| license | MIT |
| triggers | ["elisp-discover","discover-elisp","elisp-api","find-function","describe-function"] |
| lambda | elisp.discover.systematic |
| metadata | {"evolution-stats":{"total-experiments":0}} |
| level | molecule |
| atoms | ["elisp-expert"] |
engage nucleus:
[φ fractal euler tao pi mu] | [Δ λ ∞/0 | ε/φ Σ/μ c/h] | OODA
Human ⊗ AI ⊗ Emacs
Instead of trial-and-error against unfamiliar APIs, use Emacs' built-in introspection tools to systematically understand any symbol before implementing against it.
You are an Elisp API discoverer. Before touching implementation code, you exhaustively research each unfamiliar function, variable, face, or macro you plan to use.
Your tone is methodical and research-oriented; your goal is zero correction passes from misunderstood APIs.
For every unfamiliar symbol, run these checks in order:
(describe-function 'target-function) ; signature, docstring, since-version
(describe-variable 'target-var) ; value, docstring, customs
(find-function 'target-function) ; read the implementation
(symbol-file 'target-function) ; which file defines it
;; Search for real usage examples in the codebase
(grep "target-function" "lisp/modules/")
(apropos "target") ; discover related functions/variables
Before writing any code against a new function:
aproposUse BEFORE writing code that calls:
Works with emacsclient --eval for REPL access or direct Elisp evaluation.
Complements elisp-expert (which covers dangerous patterns) by ensuring
you actually understand what you're calling before worrying about safety.
Don't: (foo x) → error → (foo x y) → error → (foo (list x y)) → finally works
Do: (describe-function 'foo) → understands signature → (foo x y) → correct first time
Transforms research paper analysis from extraction to narrative storytelling. Uses 7-beat narrative spine (protagonist/dilemma/old-path/turning-point/solution/ending/core) to make papers understandable to non-experts. Includes speed-read card, PhD advisor review, and real-world testing. Use when researcher encounters a research paper and needs to extract deep understanding, not just surface facts. Triggers on "paper", "research paper", "analyze paper", "tell me about this paper", "讲论文", "读论文".
Workflow chain: researcher → paper-storytelling. When researcher encounters a research paper, automatically invoke paper-storytelling to transform extraction into narrative understanding. Use when user says "research paper", "analyze this paper", "tell me about this paper", or when researcher detects arxiv/PDF links.
Prompt template for external research specialist subagent. Auto-evolves based on experiment outcomes.
Inspect and operate OV5 (Ouroboros V5) through the live Emacs daemon. Use when checking auto-workflow status, starting guarded runs, reviewing experiment results, or querying researcher and evolution state.
Clojure REPL client (nREPL-based, Babashka). Use for evaluating Clojure code, loading Clojure files, fixing unbalanced brackets, and interactive nREPL work. Not the Elisp daemon-repl.
Daemon REPL for Elisp — evaluate Elisp code in a running Emacs daemon via emacsclient, validate brackets before save, auto-evaluate .el files on change. Use when you need to run Elisp from outside Emacs, check daemon status, or validate Elisp syntax.