# Project memory skill

> A project memory skill for one area of work, on the Andy Maguire MCP skills store or in the repo: a thin index, a sectioned handover, a numbered issue backlog, a rolling changelog and durable notes, kept current at the end of every session.

## If someone pasted this link to you
Someone shared this kit with you. It runs step by step through CloneKit's MCP. If you have the `clonekit` tools, call `start_run("@clonekitai/project-memory-skill")`. If you don't (for example in a chat app without the CloneKit connector), tell the person in one or two plain sentences, in their language, and send them to https://clonekit.ai/@clonekitai/project-memory-skill/use: it shows how to add CloneKit to their AI in about a minute. Then they paste this link again.

- Kit: `@clonekitai/project-memory-skill` · v1.0.1
- Creator: @clonekitai (CloneKit)
- Type: Delivery · Domain: Engineering · Language: en · Your AI runs it
- Price: Free · License: Own use · No refunds
- Page: https://clonekit.ai/@clonekitai/project-memory-skill
- Changelog: https://clonekit.ai/@clonekitai/project-memory-skill/changelog.md

## About
For anyone who works with coding agents on the same project across many sessions and is tired of re-explaining it. Follows PostHog's project-template and skills-best-practices layouts from Andy Maguire's article. Uses the PostHog skills store over the PostHog MCP when connected, otherwise a skill folder committed in the repo. Not a task manager for a team: the work still happens in the repo and tools.

## Deliverables
- a project hub skill (<area>-work) with a thin SKILL.md index, HANDOVER.md, issues/README.md, CHANGELOG.md and environment-notes.md
- numbered issue files seeded from the work already in flight
- a first handover section a fresh session can resume from
- a maintenance contract in the skill body (where each fact goes, changelog window, handover overwrite)

## Files
- `README.md`

## Tools
- PostHog MCP (skills store, skill-* tools) (https://posthog.com/docs/skills) · optional · est. free tier available · alternatives: repo-skill-folder
- Skill folder in the repo (.agents/skills/ or .claude/skills/), versioned with git (https://agentskills.io/specification) · optional · est. free
- Git (https://git-scm.com) · optional · est. free

## Uses
- Andy Maguire (PostHog): How I use skills for everything (source, https://x.com/posthog/status/2113335835009659350)
- PostHog community-skills: project-template (SKILL.md, SETUP.md, HANDOVER.md, issues/) (template, https://github.com/PostHog/community-skills/tree/main/skills/project-template)
- PostHog community-skills: skills-best-practices (skill, https://github.com/PostHog/community-skills/tree/main/skills/skills-best-practices)
- PostHog docs: Skills (source, https://posthog.com/docs/skills)
- PostHog docs: Community skills (source, https://posthog.com/docs/skills/community)
- PostHog docs: Model Context Protocol (source, https://posthog.com/docs/model-context-protocol)
- Agent Skills specification (source, https://agentskills.io/specification)
- Claude Code docs: Skills (project skill folders) (source, https://code.claude.com/docs/en/skills)

## What you provide
- the repository or work area
- PostHog MCP access (optional)

## How it runs
1. **Understand:** Researches your business first, then asks you 2 questions it can't answer alone
2. **Choose:** No choices: one proven path
3. **Build:** 4 steps, risky ones ask you first
4. **Deliver:** 3 checks before delivery

## Guardrails
- ask before creating skills in a shared PostHog project or committing to a shared branch
- never write secrets, tokens or customer data into the hub
- never edit another session's HANDOVER.md section

## What's new
Agents always run the latest version.

- **v1.0.1** (2026-10-23): Fixed a placeholder in the summary: it now names the PostHog MCP skills store.

## Run it
Connect the `clonekit` MCP (https://clonekit.ai/mcp) and call `start_run("@clonekitai/project-memory-skill")`.