Knowledge layer
Use e11-knowledge to read the E11 platform documentation selected by your project’s alloy pin. The corpus manifest defines categories, paths, and views. Read the manifest’s vocabulary before requesting a package or category.
Ask for a document
Use e11-knowledge to resolve sdk:auth.
Use e11-knowledge to resolve sdk:auth:backend-using.
Use e11-knowledge to resolve matrix:unit.The skill returns content with a Cite as: path. Copy this path into the decision or implementation record. Use list:<category> with a category from the manifest to list available units.
What is in scope
What e11 init set up decides what the skill can read. The This codebase answer gives the repository its own corpus; the Engineering11 platform adds the Engineering11 knowledge as a declared dependency; the fourth answer adds the repositories and packages you picked.
The skill composes one scope per session from the open knowledge-base roots:
| Part | Source |
|---|---|
| Primary | This repository's own corpus under .alloy/corpus. |
| Peers | Other knowledge-base roots open beside this one. |
| Declared dependencies | What the manifest declares and .alloy/corpus.lock pins, read from the local cache. |
Every answer carries a [scope] line naming the primary root, the peers, the pinned dependencies and anything unavailable. A key outside the scope is reported as out of scope; nothing is fetched at read time. e11 doctor names an open peer this repository does not yet declare, with the alloy add --pick command that declares it.
Query grammar
| Key | Purpose |
|---|---|
sdk:<name>[:<subdoc>] | Read an SDK, with the documented tier fallback. |
api:<name>[:<subdoc>] | Read the backend-api category explicitly. |
<category>:<name>[:<subdoc>] | Resolve a category from the manifest. |
meta:<name> | Read corpus metadata. |
matrix:<name> | Read a selection matrix. |
list:<category> | List units in a category. |
Citations and overrides
Cite the returned alloy:// path. Reserved generator material uses sdks-nodejs-skill://. Keep .alloy/corpus.lock committed. Configure corpus_root and extra_query_keys in your e11-knowledge override when your team stores another corpus.
Query alloy directly provides a short procedure.