Copy one prompt into Cursor, Copilot, Kilo, or any agent with web access.
Install the Neexo skill "Agent Session Diary" (agent-session-diary) in this repository.
Manifest: https://awesome.neexo.dk/api/install-manifest?ids=skills%2Fagent-session-diary
Catalog: https://awesome.neexo.dk/skills/agent-session-diary
Steps:
1. Fetch https://awesome.neexo.dk/api/install-manifest?ids=skills%2Fagent-session-diary and read the file list.
2. Fetch https://awesome.neexo.dk/api/skills/agent-session-diary/bundle and write every file to the correct project skill folder.
3. Detect IDE from this repo (.cursor → Cursor, .kilo → Kilo).
4. Preserve subdirectory structure (references/, agents/, scripts/, assets/).
5. Confirm which files you wrote.
Copilot — full plugincopilot plugin install neexo-planning@awesome-neexo
Bundle API (JSON)https://awesome.neexo.dk/api/skills/agent-session-diary/bundle
Overview
Use docs/AI_SESSION.md to record what the agent did, decided, and left unfinished.
When to use
Multi-session features
Handoff between agents or developers
HIGH-risk work where decisions must be traceable
Format
# AI Session Log
## YYYY-MM-DD — short title
**Goal:** …
**Stack playbook:** saas-multi-tenant (if applicable)
**Files touched:** …
**Decisions:** …
**Validation run:** …
**Open items:** …
**Next session:** …
Rules
Append new entries; do not rewrite history
Keep entries under 40 lines
Link to PRs or issues when they exist
Do not store secrets or PII in the diary
Raw content
Copy into your project — e.g. .instructions.md, .agent.md, or SKILL.md
## Overview
Use `docs/AI_SESSION.md` to record what the agent did, decided, and left unfinished.
## When to use
- Multi-session features
- Handoff between agents or developers
- HIGH-risk work where decisions must be traceable
## Format
```markdown
# AI Session Log
## YYYY-MM-DD — short title
**Goal:** …
**Stack playbook:** saas-multi-tenant (if applicable)
**Files touched:** …
**Decisions:** …
**Validation run:** …
**Open items:** …
**Next session:** …
```
## Rules
- Append new entries; do not rewrite history
- Keep entries under 40 lines
- Link to PRs or issues when they exist
- Do not store secrets or PII in the diary