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.
Resolution order
| Rung | Source |
|---|---|
| 0 | The enclosing repository’s spoke corpus under .alloy/corpus. Routing follows category vocabulary. |
| 1 | The alloy MCP service. |
| 2 | The local cache. |
| 3 | The installed corpus package. |
| 4 | Stop with the missing prerequisite. |
The skill advances only when a source is unavailable. A reachable source’s NOT FOUND answer ends the lookup. A lower source does not override the selected corpus’s answer. Missing SDK documentation also supports a source-code pointer within the selected lookup rules.
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.