Skip to content
Agentmart
Submit a tool

engram-business-rules

Product and business-rule guardrails for Engram.

Skill by gentleman-programming

IndexedApache-2.0★ 7,588
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/gentleman-programming-engram-business-rules

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Product and business-rule guardrails for Engram. Trigger: Any change that affects sync behavior, project controls, permissions, or memory semantics.

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/engram-business-rules

What's inside

Skill name
engram-business-rules
Description
Product and business-rule guardrails for Engram. Trigger: Any change that affects sync behavior, project controls, permissions, or memory semantics.
License
Apache-2.0
Metadata
author: gentleman-programming · version: 1.0
Instructions
27 lines in SKILL.md · view on GitHub

Agent Skills spec issues

  • name: "engram-business-rules" does not match folder "business-rules"

Files (1)

  • SKILL.md

SKILL.md (first lines)

## When to Use

Use this skill when:
- Changing enrollment, sync, auth, admin controls, or cloud behavior
- Implementing project-level or org-level policy
- Adjusting what data appears locally vs remotely

---

## Product Rules

1. Local-first remains the default mental model.
2. Org-wide security controls belong in cloud, not only in local clients.
3. Project sync policy must be enforceable server-side if it is meant for admins.
4. UI controls must map to real business rules, never fake toggles.
5. Data visibility and sync permissions must be deterministic and testable.

---

## Sync Rules

- Enrollment controls what may sync from local.
- Cloud pause controls what the organization currently allows.
- When a policy blocks sync, fail loudly rather than dropping data silently.
- Preserve auditability whenever admin policy changes behavior.

From Gentleman-Programming/engram, Apache-2.0.

More from Gentleman-Programming/engram

Signals

Stars
7,588
Forks
791
Open issues
73
Last commit (this folder)
Mar 7, 2026 (7 months ago)
Last release
Oct 23, 2026 (4 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Version
1.0
License
Apache-2.0
Repository
github.com/Gentleman-Programming/engram
Website
engram.gentlemanprogramming.com/
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from gentleman-programming

Cite this page

engram-business-rules skill. Agent Mart. https://agentmart.dev/skills/gentleman-programming-engram-business-rules (last updated 2026-10-24)