openclaw-flowstate-plugin Package Skill

Package: @epicdm/openclaw-flowstate-plugin Repository: epic-flowstate-community Path: packages/openclaw-flowstate-plugin Version: 0.2.2

Use this published Dojo skill as the package-level entrypoint. For detailed workflows, use the package-local skills listed below.

Primary Package Workflow

FlowState OpenClaw FlowState Adapters

Status: Active Purpose: Guide provider adapter/source changes. Scope: src/sync/adapters and src/sync/sources. Trigger: Need to update Discord, Slack, Teams, MCP polling, account mapping, or capability behavior. Input: Provider API client, adapter capabilities, FlowState snapshot changes, and mapping store state. Output: Adapter behavior that preserves reconciliation semantics.

Adapter Rules

1. Keep adapter capabilities() accurate; manifest drift checks depend on it.
2. Preserve provider-specific naming helpers, such as Slack handle/channel conversion.
3. Update provider tests with mocked API clients before touching live integration assumptions.
4. Keep MCP poll source collection fetch behavior compatible with FlowState collection contracts.

Verification

yarn workspace @epicdm/openclaw-flowstate-plugin test --runInBand src/sync/adapters src/sync/__tests__/McpPollSource.test.ts
yarn workspace @epicdm/openclaw-flowstate-plugin typecheck

Created: 2026-06-29

Package Skill Inventory

@epicdm/openclaw-flowstate-plugin Skill Inventory

Review Gate

@epicdm/openclaw-flowstate-plugin Skills Review

Verdict: Pass with follow-ups.

Skills cover plugin entry, staged sync runtime, adapters, manifest capability checks, and verification commands.

Verification

• ASCII and skill frontmatter checks passed.
• yarn workspace @epicdm/openclaw-flowstate-plugin test --runInBand --no-cache passed: 10 suites, 77 tests.
• yarn workspace @epicdm/openclaw-flowstate-plugin typecheck passed.
• yarn workspace @epicdm/openclaw-flowstate-plugin lint passed with 1 existing non-null assertion warning.
• yarn workspace @epicdm/openclaw-flowstate-plugin build could not run because the package has no build script.

Follow-Ups

• Decide whether the package should define a no-op or real build script.
• Rebuild generated .flowstate/dojo content from the reviewed local skills before publishing.

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/openclaw-flowstate-plugin/package.json. Do not treat generated feature lists as lessons; use workflow evidence from CODE-REVIEW.md, SKILL-INVENTORY.md, and REVIEW.md.