How to use @owlmeans/context — the context every OwlMeans app looks things up on, context.service() and resource lookups, typed entrypoint protocol references, and entitySlug vs entityId addressing. Auto-invoked when importing from @owlmeans/context or obtaining a service, resource or entrypoint from a context.
Scanned 9/22/2026
Install to Claude Code
npx -y skills add owlmeans/common --skill owlmeans-context --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Owlmeans Context?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/owlmeans-owlmeans-context)More formats (shields.io, HTML) on the badges page.
---
name: owlmeans-context
description: How to use @owlmeans/context — the context every OwlMeans app looks things up on, context.service() and resource lookups, typed entrypoint protocol references, and entitySlug vs entityId addressing. Auto-invoked when importing from @owlmeans/context or obtaining a service, resource or entrypoint from a context.
---
# Context lookups
**Install:** `bun add @owlmeans/context@^0.1.18-rc.26`
Use a protocol declaration directly when obtaining an entrypoint. The declaration supplies the
registered entrypoint’s request and response types.
```ts
const project = await context.entrypoint(projectProtocols.get).call({
params: { id },
})
```
Use `context.service(alias)` for registered services and context resource APIs for data access.
Protocol declarations are shared immutable values; context registration receives local server or
client entrypoints created with `bind()`, `bindAll()` or `bindScreen()`.
Keep organization entity addressing on the wire as `entitySlug`. Resolve the stable `entityId`
inside the context before persisting relations or calling third parties.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!