flowstate-connector-bluebubbles Package Skill

Package: @epicdm/flowstate-connector-bluebubbles Repository: epic-flowstate-community Path: packages/flowstate-connector-bluebubbles Version: 1.0.0

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

Primary Package Workflow

FlowState Connector BlueBubbles Document Mapping

Status: Active Purpose: Teach agents how BlueBubbles responses map into FlowState documents. Scope: connector.yaml collections mappings. Trigger: A task changes result mappings, document types, metadata paths, source IDs, or FlowState collection targets. Input: Endpoint response shape, JSONPath source, target document fields. Output: Correct document mapping changes.

Common Defaults

Every mapping targets documents and sets:

documentVersion: 1
approved: false
projectId: ''

BlueBubbles-specific fields live under:

metadata.bluebubbles.*

Mapping Table

Metadata Fields

Server info:

• metadata.bluebubbles.guid
• metadata.bluebubbles.version

Chats:

• metadata.bluebubbles.guid
• metadata.bluebubbles.firstParticipant

Messages:

• metadata.bluebubbles.guid
• metadata.bluebubbles.chatGuid
• metadata.bluebubbles.isFromMe
• metadata.bluebubbles.dateCreated for message-query
• metadata.bluebubbles.handle for message-query

Webhooks:

• metadata.bluebubbles.webhookId
• metadata.bluebubbles.url

Change Rules

1. Keep sourcePath aligned with endpoint resultPath.
2. Use stable BlueBubbles IDs as sourceIdPath when possible.
3. Preserve existing documentType values unless a migration is planned.
4. Add tests when endpoint IDs or mapping assumptions change.
5. Keep connector-core bundled copy synchronized.

Verification

yarn workspace @epicdm/flowstate-connector-bluebubbles test --runInBand

For runtime mapping behavior, run relevant connector-core sync/manifest tests too.

Composition Notes

• Use flowstate-connector-bluebubbles-endpoints for endpoint shapes.
• Use flowstate-connector-bluebubbles-maintenance for bundled manifest sync.

Created: 2026-06-29

Package Skill Inventory

@epicdm/flowstate-connector-bluebubbles Skill Inventory

Repository: epic-flowstate-community Package path: packages/flowstate-connector-bluebubbles

Skill Map

Composition Guidance

Use this package as a connector manifest, not a TypeScript API library.

• Start with flowstate-connector-bluebubbles for routing.
• Use flowstate-connector-bluebubbles-manifest for setup/auth.
• Use flowstate-connector-bluebubbles-endpoints for REST passthrough behavior.
• Use flowstate-connector-bluebubbles-document-mapping for FlowState document records.
• Use flowstate-connector-bluebubbles-maintenance for tests, bundled copy, and plugin publication.

Baseline Failure Cases Addressed

Review Gate

Publish-ready only after:

• local manifest tests pass
• build/no-op behavior is recorded
• connector-core bundled copy drift is checked
• generated Dojo content is rebuilt from reviewed skills

Review Gate

@epicdm/flowstate-connector-bluebubbles Skill Review

Review Summary

Created package-local operating skills for the BlueBubbles connector under packages/flowstate-connector-bluebubbles/.flowstate/skills.

The skillset is manifest-oriented because this package has no TypeScript source exports. It teaches:

• connector setup and auth
• REST endpoint contracts
• document mapping behavior
• manifest/bundled-copy maintenance
• plugin publish readiness

Evidence Reviewed

• package.json
• README.md
• connector.yaml
• flowstate.plugin.json
• __tests__/connector.test.ts
• .flowstate/feature-matrix/inventory.md
• .flowstate/dojo/agent-skillset.md
• packages/connector-core/manifests/bluebubbles.yaml
• packages/connector-core/src/manifest/__tests__/bundled-manifests.test.ts
• packages/connector-core/src/runtime/__tests__/manifest-fetch.test.ts
• packages/connector-core/src/manifest/schema.ts
• packages/flowstate-cli/src/templates/compose/services.ts

Quality Notes

The generated Dojo artifact only split the package into connector.yaml and flowstate.plugin.json skilllets. The reviewed skillset instead teaches the connector's operational shape: setup, endpoint calls, mapping into documents, and maintenance.

Known Drift Preserved

• No TypeScript source exports exist.
• Package is private and manifest-driven.
• build intentionally performs no build.
• Connector-core keeps a bundled copy of the manifest that must stay synchronized.
• CLI compose templates expose BLUEBUBBLES_PASSWORD, so the connector is operationally referenced even without package imports.
• Feature inventory reports no inbound package import; this is expected for plugin manifests.
• Generated Dojo course content assumes src/index.ts and normal TypeScript entry points; that is not valid for this package.

Verification Status

Completed after authoring:

• ASCII scan: passed.
• Frontmatter scan: passed.
• Manifest bundled-copy diff against packages/connector-core/manifests/bluebubbles.yaml: passed, no differences.
• yarn workspace @epicdm/flowstate-connector-bluebubbles test --runInBand: passed, 1 suite and 3 tests; watchman emitted an existing recrawl warning.
• yarn workspace @epicdm/flowstate-connector-bluebubbles build: passed; printed no-build message by design.
• yarn nx build @epicdm/flowstate-connector-bluebubbles: passed with cached dependencies and the connector no-build target; Nx Cloud reported existing unconnected-workspace 401.

Dojo publication remains deferred until local skills pass verification and review.

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