commory-msglayer

Standardize personal communication exports into a canonical MsgLayer schema.

Updated May 11, 2026
One-click install
npx skills add https://github.com/IsKenKenYa/Commory --skill commory-msglayer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commory-msglayer
Source: https://github.com/IsKenKenYa/Commory/tree/main/.agents/skills/commory-msglayer
Command: npx skills add https://github.com/IsKenKenYa/Commory --skill commory-msglayer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It standardizes how personal communication data (SMS, calls, and related snapshots) is represented so Android exports, the Go backend validator, and future agents can interoperate reliably.

Core Features & Use Cases

  • Canonical interchange format: Defines the MsgLayer event and identity structure as a shared contract across Android, backend, and web.
  • Schema-driven validation: Enforces allowed fields, additionalProperties rules, and event/content type constraints via the Go validator.
  • Extensible evolution with guardrails: Establishes versioning (v0.1) and a workflow for updating both Kotlin mappers and Go constants together when the schema changes.
  • Use case: You add a new Android mapping for an event type, then update the Go validator and schema so the backend can import and query the new records safely.

Quick Start

Use the commory-msglayer skill to align the MsgLayer schema, examples, Kotlin mapping, and Go validator to support a new or updated event type for v0.1 exports.

Frequently Asked Questions about commory-msglayer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize Android SMS and call exports for a Go backend?

To standardize Android SMS and call exports for a Go backend, define a canonical MsgLayer JSON schema that enforces event and identity structure constraints. This ensures Android exports, the Go backend validator, and future agents interoperate reliably.

How does schema-driven validation work for Android-to-backend import pipelines?

Schema-driven validation for Android-to-backend import pipelines works by enforcing allowed fields, additionalProperties rules, and event or content type constraints via the Go validator. This ensures only deterministic, structured message interchanges are imported and queried safely.

Can I use this to synchronize Kotlin mappers and Go constants when updating a JSON schema?

Yes, you can synchronize Kotlin mappers and Go constants when updating a JSON schema. The canonical MsgLayer schema establishes a versioned workflow requiring coordinated updates to both Kotlin mapping code and Go validator constants to support new event types safely.

What is the best way to add a new event type to a v0.1 message schema?

The best way to add a new event type to a v0.1 message schema is to align the MsgLayer schema, examples, Kotlin mapping, and Go validator together. This coordinated update workflow ensures the backend can import and query the new records deterministically.

Does the MsgLayer schema support web and agent integrations for personal communication data?

Yes, the MsgLayer schema supports web and agent integrations for personal communication data. It defines a canonical interchange format acting as a shared contract across Android, backend, and web platforms for deterministic message interchange.