Skip to content

Add zo-mengram-setup and zo-mengram-memory skills#26

Open
Zenlyte wants to merge 6 commits intozocomputer:mainfrom
Zenlyte:add-zo-mengram-setup-and-memory-skills
Open

Add zo-mengram-setup and zo-mengram-memory skills#26
Zenlyte wants to merge 6 commits intozocomputer:mainfrom
Zenlyte:add-zo-mengram-setup-and-memory-skills

Conversation

@Zenlyte
Copy link
Copy Markdown
Contributor

@Zenlyte Zenlyte commented Mar 4, 2026

Description

Adds two complementary community skills for self-hosted memory on Zo:

  1. zo-mengram-setup: installation, baseline configuration, auth hardening, and verification.
  2. zo-mengram-memory: daily runtime workflows with gated recall/search defaults and break-glass raw fallback.

This split keeps beginner onboarding simple while allowing faster iteration on runtime workflows.

Features

  • self-hosted Mengram setup and security baseline
  • gated endpoint-first runtime guidance (/api/recall/gated, /api/search/gated)
  • break-glass troubleshooting path (/api/recall, /api/search)
  • references for API, security, architecture, and operational overview

Validation

  • Ran bun install and bun validate in the skills repo.
  • Existing warnings from unrelated External skills remain unchanged.

Checklist

  • SKILL frontmatter valid and names match directories
  • No secrets or personal credentials included
  • Uses placeholders for author and user-specific values
  • Structure follows allowed directories (scripts, references, assets)

@Zenlyte Zenlyte mentioned this pull request Mar 10, 2026
6 tasks
@skeletor-js
Copy link
Copy Markdown
Collaborator

@Zenlyte A few things to address before merge.

Pin the git clone.
setup.py clones from github.com/alibaizhanov/mengram at HEAD with no tag or commit pin. Please pin to a specific release tag or commit SHA so users aren't pulling arbitrary code that can change after merge.

Author placeholder.
Both SKILL.md files still have YOUR_HANDLE.zo.computer as the author. Please fill in your actual handle.

Deduplicate.
41% of this PR is identical content across the two skills. The reference docs (api.md, architecture.md, security.md) are copied verbatim in both directories, and mengram_memory.py exists in both. Pick one canonical location for the shared docs (probably setup) and remove the duplicate mengram_memory.py from setup since it belongs in the memory skill.

Happy to re-review once updated.

- Pin git clone to v2.6.1 tag in setup.py (--branch v2.6.1 --depth 1)
- Replace YOUR_HANDLE.zo.computer with Zenlyte.zo.computer in both SKILL.md files
- Remove duplicated reference docs (api.md, architecture.md, security.md) from zo-mengram-memory, canonical copies stay in zo-mengram-setup/references/
- Remove duplicate mengram_memory.py from zo-mengram-setup, canonical copy stays in zo-mengram-memory/scripts/
- Add cross-reference notes in both SKILL.md files pointing to shared resources
@Zenlyte
Copy link
Copy Markdown
Contributor Author

Zenlyte commented Mar 21, 2026

All three items addressed in c8b668d:

  1. Pinned git clone - setup.py now clones with --branch v2.6.1 --depth 1, pinning to the latest Mengram release tag.

  2. Author placeholder - Both SKILL.md files now use Zenlyte.zo.computer.

  3. Deduplicated shared content - Removed 1,029 lines of duplicated content:

    • Reference docs (api.md, architecture.md, security.md) are now canonical in zo-mengram-setup/references/ only.
    • mengram_memory.py is canonical in zo-mengram-memory/scripts/ only.
    • Both SKILL.md files now include a "Shared resources/references" section cross-referencing the canonical locations.
    • overview.md remains in both since its content is skill-specific.

Ready for re-review.

@Zenlyte
Copy link
Copy Markdown
Contributor Author

Zenlyte commented Mar 22, 2026

Fixed the author handles back to curtastrophe.zo.computer per my actual Zo handle.

1 similar comment
@Zenlyte
Copy link
Copy Markdown
Contributor Author

Zenlyte commented Mar 22, 2026

Fixed the author handles back to curtastrophe.zo.computer per my actual Zo handle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants