flowstate-epic-flowstate-community-epicdm-flowstate-agents-memory-client
Package-local agent skill for @epicdm/flowstate-agents-memory-client.
Tags
Publisher
Versions
1 version published — latest: 1.0.7
- 1.0.7publishedInvalid Date
Skill
flowstate-agents-memory-client Package Skill
Package: @epicdm/flowstate-agents-memory-client
Repository: epic-flowstate-community
Path: packages/flowstate-agents-memory-client
Version: 1.0.7
Use this published Dojo skill as the package-level entrypoint. For detailed workflows, use the package-local skills listed below.
Primary Package Workflow
Agents Memory Client Contract Reference
Status: Active
Purpose: Provide dense lookup for AMS client contracts.
Scope: src/index.ts, src/types.ts, src/constants.ts.
Trigger: Public API review, docs repair, caller integration, Dojo rebuild.
Input: Source files and intended caller behavior.
Output: Accurate endpoint/type/return-contract understanding.
Authority
Use source as authority:
src/AgentMemoryClient.tssrc/types.tssrc/constants.ts
Return Semantics
Common fallbacks:
healthCheck()->falsereadWorkingMemory()->nulladdMessage()->null- search methods -> empty result objects or arrays depending on method
Invalid empty sessionId throws in several methods.
Drift Notes
PACKAGE_INFO.versionis stale.- README overclaims client-side summarization/truncation.
- Generated Dojo labels constants as skills and marks package privacy incorrectly.
Done When
- The caller knows whether a method throws, returns null, false, or an empty result.
- Docs/skills use source behavior rather than generated Dojo text.
Package Skill Inventory
Package Skill Inventory: @epicdm/flowstate-agents-memory-client
Package Context
Package path: /Users/sthornock/code/epic/epic-flowstate-community/packages/flowstate-agents-memory-client
This package is a typed HTTP client for AMS. The skillset should teach safe integration with an external memory server, not pretend constants or enums are independent skills.
Skill Map
| Skill | Type | Trigger | Teaches | Evidence | Depends On | Dojo |
|---|---|---|---|---|---|---|
flowstate-agents-memory-client | orchestrator | Use when touching or importing the AMS memory client | Routes setup, working memory, memory prompt, search, contracts, troubleshooting, maintenance | src/index.ts, AgentMemoryClient.ts | package docs, feature matrix | ready-after-review |
flowstate-agents-memory-client-setup | workflow | Use when configuring AMS base URLs, auth, health, retries, or timeouts | Constructor config, authToken, healthCheck, retry/timeout behavior | AgentMemoryClient.ts, constants.ts, app-framework hook | AMS runtime | ready-after-review |
flowstate-agents-memory-client-working-memory | workflow | Use when adding, reading, replacing, clearing, or formatting conversation memory | addMessage, working memory CRUD, summaries, buildContextPrompt | AgentMemoryClient.ts | setup | ready-after-review |
flowstate-agents-memory-client-memory-prompt | workflow | Use when preparing LLM messages with AMS context windows | getMemoryPrompt, context window params, summarized responses | memory prompt method/types | LLM client skills | ready-after-review |
flowstate-agents-memory-client-search-and-retention | workflow | Use when creating, searching, forgetting, deleting, or unified-searching memory | Long-term memory methods, unified search, delete warning | AgentMemoryClient.ts | MCP memory tools | ready-after-review |
flowstate-agents-memory-client-contract-reference | reference | Use when checking endpoints, types, constants, return semantics, or version drift | Endpoint map, exported types, failure returns, PACKAGE_INFO | constants.ts, types.ts | none | local-only |
flowstate-agents-memory-client-troubleshooting | troubleshooting | Use when AMS calls fail, return empty results, or downstream memory appears missing | Null/empty semantics, retries, health, session pitfalls, false-success risks | fetchWithRetry, tests, downstream refs | setup/reference | ready-after-review |
flowstate-agents-memory-client-maintenance | maintenance | Use before release, docs, Dojo, or public contract changes | Tests, reverse refs, docs/matrix/Dojo drift, package version authority | package scripts, docs, downstream refs | package docs sync | local-only |
Anti-Sprawl Decision
Eight skills are justified because setup, working memory, memory prompt, long-term search/retention, contracts, troubleshooting, and maintenance each have distinct triggers and failure modes. Constants and endpoint names stay in a reference skill.
Feature Coverage
| Feature Group | Source Evidence | Covered By | Notes |
|---|---|---|---|
| Client construction/config/auth | AgentMemoryClient, DEFAULT_CONFIG | setup, contract-reference | baseUrl required |
| Health/retry/failure behavior | healthCheck, fetchWithRetry | setup, troubleshooting | Boolean/null/empty semantics matter |
| Working memory | read/replace/remove/addMessage | working-memory | Include read-modify-write race risk |
| Summaries/context windows | contextWindowMax, summary | working-memory, memory-prompt | AMS performs summarization |
| Memory Prompt API | getMemoryPrompt | memory-prompt | LLM-ready messages |
| Sessions | listSessions, AmsSession | contract-reference, troubleshooting | Session id parsing risk |
| Long-term/unified memory | create/search/forget/delete/searchAll | search-and-retention | Delete is policy-based |
| Downstream integrations | MCP, workers, app-framework | orchestrator, troubleshooting, maintenance | Critical for contract changes |
Composition Model
Start with the orchestrator. New integrations use setup, then working-memory or memory-prompt, then search-and-retention if long-term memory is involved. Debugging starts with troubleshooting and contract-reference. Release/docs work starts with maintenance.
Deferred Skills
- React hook skill belongs to
flowstate-app-framework. - MCP memory tools skill belongs to
flowstate-mcp. - AMS server operations skill is deferred until server source/API is reviewed.
- Dojo publish skill is deferred until generated content is rebuilt from reviewed local skills.
Review Questions
- Should
PACKAGE_INFO.versionbe removed or synchronized? - Should
deleteLongTermMemorybe documented as unsafe/deferred? - Should downstream MCP tools inspect null/empty results before success responses?
- Should the README be replaced with
.flowstate/docsquick-start/API content?
Review Gate
Package Skills Review: @epicdm/flowstate-agents-memory-client
Verdict
Pass with fixes.
The local skillset teaches actual AMS client workflows and captures the key risk: null/empty best-effort return semantics can be hidden by downstream wrappers. Existing generated Dojo content must be rebuilt before publication.
Findings
| Severity | Skill | Issue | Evidence | Required Fix |
|---|---|---|---|---|
| Important | all | Existing Dojo content is generated and teaches constants as skills | .flowstate/dojo/* | Rebuild Dojo from reviewed skills |
| Important | troubleshooting/search | Downstream wrappers may report success on null/empty results | MCP reverse references | Track/repair downstream false-success behavior |
| Minor | reference | PACKAGE_INFO.version drift remains | constants.ts, package.json | Track maintenance issue |
| Minor | all | Verification passed after authoring; keep this evidence current before Dojo publish | test, typecheck, build passed in this pass | Re-run before final Dojo publish if source changes |
Coverage
| Feature Group | Status | Skill | Notes |
|---|---|---|---|
| Setup/auth/health/retry | Covered | setup | Includes baseUrl and boolean health |
| Working memory | Covered | working-memory | Includes read-modify-write caveat |
| Memory Prompt API | Covered | memory-prompt | Server-side context preparation |
| Long-term/unified search | Covered | search-and-retention | Includes delete warning |
| Types/endpoints/contracts | Covered | contract-reference | Includes return semantics |
| Failures/downstream risks | Covered | troubleshooting | Includes false-success risk |
| Maintenance/docs/Dojo | Covered | maintenance | Rebuild before publish |
Drift and Contract Risks
| Area | Risk | Evidence | Decision |
|---|---|---|---|
| Summarization | Docs imply client-owned summarization | README vs source | Teach AMS-side summarization |
| Version | PACKAGE_INFO.version stale | constants.ts | Track maintenance |
| Dojo | Generated skilllets for constants | .flowstate/dojo/* | Do not publish as-is |
| Downstream wrappers | Success may hide null/empty returns | MCP references | Warn and track repair |
Dojo Publication Decision
Do not publish existing generated Dojo files. Reviewed local skills are eligible for Dojo conversion after verification passes and manifests are rebuilt.
Follow-Up Work
- Package verification passed:
yarn workspace @epicdm/flowstate-agents-memory-client testyarn workspace @epicdm/flowstate-agents-memory-client typecheckyarn workspace @epicdm/flowstate-agents-memory-client build
- Rebuild
.flowstate/dojofiles. - Fix or document downstream false-success behavior.
- Synchronize package version metadata and README.
Usage
Start with this skill to understand the package purpose, then use the package-local focused skills for specific workflows. Keep this Dojo version aligned with packages/flowstate-agents-memory-client/package.json. Do not treat generated feature lists as lessons; use workflow evidence from CODE-REVIEW.md, SKILL-INVENTORY.md, and REVIEW.md.
Install
Run this in your project to install via CLI:
fscloud dojo skill install flowstate-epic-flowstate-community-epicdm-flowstate-agents-memory-client --target <target> --out ./skillsReplace <target> with your agent target identifier. See the CLI docs for details.