node-journal
/node-journal
Node journal (octobot.community.node_journal): record-only from outside the package; reads only for export inside node_journal; not a source of truth. Apply when editing node_journal or adding/changing record_* calls elsewhere.
- Author
- drakkar-software ↗
- Repository
- octobot ↗
- Licence
- GPL-3.0
- Last repository change
- 07.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 07.10.2026, without references to retired models or APIs.
GPL-3.0, otwarta.
What it does and when to use it
Node journal (octobot.community.node_journal): record-only from outside the package; reads only for export inside node_journal; not a source of truth. Apply when editing node_journal or adding/changing record_* calls elsewhere.
Original author description
Node journal (octobot.community.node_journal): record-only from outside the package; reads only for export inside node_journal; not a source of truth. Apply when editing node_journal or adding/changing record_* calls elsewhere.
How it works
- Purpose
- Integrators (outside nodejournal/)
- Inside octobot/community/nodejournal/
- Related
SKILL.md preview
--- name: node-journal description: >- Node journal (octobot.community.node_journal): record-only from outside the package; reads only for export inside node_journal; not a source of truth. Apply when editing node_journal or adding/changing record_* calls elsewhere. paths: - octobot/community/node_journal/** --- # Node journal Full rules: [`octobot/community/node_journal/AGENTS.md`](../../../octobot/community/node_journal/AGENTS.md). ## Purpose Append-only **event log** for diagnostics, journey analytics, and **export/sharing** (upload envelope). Not authoritative application state. ## Integrators (outside `node_journal/`) - Import `octobot.community.node_journal` and call Tier-1 **`record_*`** / `record` only. - Do **not** call `read_events`, read journal files on disk, or branch product logic on journal contents. - Do **not** store data in journal payloads to reuse later for non-journal features. Use config, DB, sync collections, or domain stores as source of truth. ## Inside `octobot/community/node_journal/` - **`read_events`**, `build_journey_summary`, and `build_upload_envelope` belong to the **export pipeline** (plus unit tests). - Event and wire literals: extend [`events.py`](../../../octobot/community/node_journal/events.py), [`constants.py`](../../../octobot/community/node_journal/constants.py), [`enums.py`](../../../octobot/community/node_journal/enums.py); do not inline strings in recording code. - Respect import tiers in package [`__init__.py`](../../../octobot/community/node_journal/__init__.py); feature code must not reach into `store` / `state` except via the public API. ## Related - Core app boundaries: [`octobot/AGENTS.md`](../../../octobot/AGENTS.md) - Python conventions (shared literals, imports): [CONTRIBUTING-agent.md](../../../CONTRIBUTING-agent.md) — **Python conventions (agents)**
Versions
The database has no other skills named node-journal.
Database snapshot: 13.11.2026 · package version f21e65929cb0 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 96ds-typescript
Use when changing TypeScript server, database, CLI, or MCP behavior in an existing Node.js package or workspace. - 100comfyui-node-basics
ComfyUI custom node fundamentals - V3 node structure, Schema, inputs/outputs, registration. Use when creating new ComfyUI custom nodes, defining node classes, or setting up a custom node project. - 90working-with-contracts
Rules for changing packages/contracts - zod schemas, config fields, enums, journal event kinds, port contracts, breaking changes and PR order. Use when you add or change anything under packages/contracts/ or review such a diff. Don't use for package boundaries (use working-in-the-monorepo). - 100iam360-habits-journal
Manage requested IAM360 challenges, habit check-ins, life events and private journal entries. Use when the user asks to record, review or correct those records, preserving consent, dates and journal version checks. - 100decision-journal
Extracts and structures development decisions from diffs, manages decision journal entries, and detects human gate triggers. Use when logging decisions during gh-start, gh-commit, or gh-address. Use when summarizing decisions for PR bodies or when checking for gate-triggering… - 100comfyui-node-basics
ComfyUI custom node fundamentals - V3 node structure, Schema, inputs/outputs, registration. Use when creating new ComfyUI custom nodes, defining node classes, or setting up a custom node project.