# Sjel

> Operates Sjel and guides work on its repository through dynamic discovery, bounded self-context, capability APIs, architecture placement, focused branches, and proportionate verification. Use when operating Sjel or Sjel services or feeds, diagnosing them, planning or coding inside the Sjel repository (~/Developer/Sjel), deciding where code belongs there, or handling its branches and PRs. Do not use for unrelated repositories, direct Home Assistant or device control, or generic prose and skill authoring with no Sjel decision.

- Skill: `larsboes/sjel` (Agent Skill, multi-file: 13 files)
- Install (CLI): `npx get-skill add larsboes/sjel`
- Raw SKILL.md: https://api.skillmd.com/api/skills/larsboes/sjel/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: larsboes (https://skillmd.com/u/larsboes)
- Updated: 2026-11-16
- Page: https://skillmd.com/skills/larsboes/sjel

---


# Sjel

Route first, then load only the selected reference. Derive changing facts at runtime; never
substitute a remembered port, inventory, issue state, service status, or graph count.

## Resolve context

Run one bounded context command before reading broadly:

```bash
tools/sjel-context with [capability]
tools/sjel-context on [unit-or-path]
```

The path is repository-relative: run it from the Sjel checkout. The installed `sjel` CLI
exposes the same surface as `sjel context with|on`. Read `references/shared-failure-policy.md`
when any expected tool, overlay, service, graph, or remote is unavailable.

## Select one mode

### Work with Sjel

Use this mode to discover or operate running capabilities, feeds, APIs, and health surfaces.

1. Read `references/with-discovery.md`.
2. For reads, writes, ingestion, or operator actions, also read
   `references/with-operations.md`. When the session exposes Sjel's MCP tools
   (`mcp__sjel__*`), use them in preference to the shell and read that file's MCP section:
   it carries the agent token, and a raw capability payload is far too large to return.
3. Read `references/shared-data-boundaries.md` before handling personal, vault, or
   cross-capability data.

### Work on Sjel

Use this mode to understand, review, plan, or change the repository.

1. Read `references/on-orientation.md`.
2. Load only the additional leaf matching the task:

| Task | Read |
| --- | --- |
| Architecture or ownership boundary | `references/shared-architecture.md` |
| Data, secrets, provenance, or trust | `references/shared-data-boundaries.md` |
| Decide where code or configuration belongs | `references/on-placement.md` |
| Dependencies, language, shell, or the build | `references/on-dependencies-and-build.md` |
| README, generated docs, manifests, Packs, or skills | `references/on-documentation.md` |
| Tests, gates, review, or completion claims | `references/on-verification.md` |
| Branch, commit, PR, or session handoff | `references/on-changes.md` |
| Approved unattended or overnight local work | `references/on-unattended.md` |

## Invariants

- Preserve unrelated worktree changes and resolve the exact target before editing.
- Keep public code and doctrine in Sjel; keep private values and state in the active overlay.
- Never generate, reveal, move, or overwrite secrets without explicit authorization.
- Prefer manifests, registry output, self-model queries, and GitHub metadata over duplicated
  prose.
- Report failed or unavailable checks exactly; do not turn missing optional context into a
  successful validation claim.

