jellycore ops
- Repo stars 0
- Author repo skills-registry
- Domain
- DevOps
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Docker
- Runtime requirements
- Docker
- Detected file/system behavior
-
- Read-only
- Network behavior
- External requests
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# JellyCore Operations
Use this runbook for production-safe service operations.
## Safety Rules
- Verify target environment before running commands.
- Prefer read-only diagnostics before restart actions.
- Do not run destructive Docker prune/remove commands unless explicitly requested.
## Standard Flow
1. Check status
```bash
docker compose ps
```
2. Check health endpoints
```bash
curl -fsS http://localhost:47778/api/health
curl -fsS http://localhost:47779/health
```
3. Inspect focused logs
```bash
docker compose logs --tail=200 oracle
docker compose logs --tail=200 nanoclaw
docker compose logs --tail=200 chromadb
```
4. Recover by smallest action
```bash
docker compose restart <service>
```
5. Re-verify status and health
## Delivery Format
- Incident summary (symptom, scope, likely root cause)
- Actions taken (ordered)
- Current status (healthy/degraded/down)
- Next recommendation
Load [references/commands.md](references/commands.md) for detailed command variants.
---
> Source: [b9b4ymiN/JellyCore](https://github.com/b9b4ymiN/JellyCore) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->
Sections and files
Listed in source order.
sections -> Safety Rules → Standard Flow → Delivery Format
terms -> Use this runbook for production-safe service operations. · - Verify target environment before running commands. · Load [references/commands.md](references/commands.md) for detailed command variants. · --- > Source: [b9b4ymiN/JellyCore](https://github.com/b9b4ymiN/JellyCore) — distributed by [TomeVault](https://tomevault.io).
files/cmd -> prune/remove · 47778/api/health · 47779/health · healthy/degraded/down · references/commands.md · b9b4ymiN/JellyCore · github.com/b9b4ymiN/JellyCore
body sha256 -> b764cb83e4fe
Safety Rules
Verify target environment before running commands. Prefer read-only diagnostics before restart actions. Do not run destructive Docker prune/remove commands unless explicitly requested.
Standard Flow
Check status Check health endpoints Inspect focused logs Recover by smallest action Re-verify status and health
Delivery Format
Incident summary (symptom, scope, likely root cause) Actions taken (ordered) Current status (healthy/degraded/down) Next recommendation Load references/commands.md for detailed command variants.