Agent skill
data-store
(ePost) Use when an agent needs to persist or retrieve project-level data across sessions via .epost-data/
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/data-store
SKILL.md
Agent Data Store Convention
Defines how agents store and access persistent project-level data across sessions.
Directory Layout
.epost-data/ ← gitignored, project-level runtime state
{domain}/
{domain}.json ← primary DB (required)
artifacts/ ← generated patches, diffs, temp files (optional)
a11y Domain Layout
.epost-data/a11y/
├── fixes/
│ ├── findings/ ← audit-a11y JSON reports (audit-YYMMDD-HHMM.json)
│ ├── patches/ ← fix-a11y unified diffs (finding-{id}-YYMMDD.diff)
│ └── reviews/ ← review-a11y JSON reports (review-YYMMDD-HHMM.json)
├── README.md ← structure guide
├── analysis.md ← trend summary
└── known-findings.json ← findings DB
Rules
| Rule | Detail |
|---|---|
Always (if exists) |
Never hard-fail on missing file — gracefully absent on first run |
| Gitignored | Runtime state, not source-tracked; must be in .gitignore |
| One agent = one domain | Agent owns its domain exclusively; never reads another agent's |
| Schema in source | Schema lives at packages/{pkg}/assets/{domain}-schema.json, tracked in git |
Agent Declaration Template
Paste into the agent's system prompt body under a Data Store section:
## Data Store
- **DB:** `.epost-data/{domain}/{domain}.json` (if exists)
- **Artifacts:** `.epost-data/{domain}/artifacts/` (if exists)
- **Schema:** `.claude/assets/{domain}-schema.json`
Domain Registry
| Domain | Owner Agent | Primary File | Package |
|---|---|---|---|
a11y |
epost-a11y-specialist | known-findings.json |
packages/a11y |
Add a row here when introducing a new agent data domain.
Schema Conventions
Minimum required fields for any {domain}.json:
{
"version": "1.0",
"created_date": "YYYY-MM-DD",
"last_reviewed_date": "YYYY-MM-DD",
"entries": [
{
"id": 1,
"resolved": false,
"resolved_date": null
}
]
}
- Bump
versionstring on schema changes (new fields = minor, breaking = major) - All commands check
resolvedbefore operating on an entry last_reviewed_dateupdated any time the DB is written
Adopting the Pattern (New Domain)
- Create schema:
packages/{pkg}/assets/{domain}-schema.json - Add domain row to the registry table above
- Add "Data Store" section to agent body using the template
- Reference paths in commands with
(if exists)guards - Add
.epost-data/to project.gitignore(if not already present)
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?