control-access
Load when deciding who sees or changes app data, or when sharing an app. Says what the node enforces.
- License 许可
- Apache-2.0
- 所属仓库
- gents-ai/gents
- 最近更新
- 2026-11-15
- Stars
- ★ 24
- Forks
- 4
01 前言 Front Matter
- name
- control-access
- description
- Load when deciding who sees or changes app data, or when sharing an app. Says what the node enforces.
03 SKILL.md 正文
Control access
Write the table first
For each collection: who reads, who writes, who must never see it. Use the person's words. Most apps fit one of these:
- Private: only the installer.
- Shared by the app's agents: only those agents read and write.
- Per-record owner: people see their own records.
- Append-only log: members add entries; nobody changes them.
Check what the node can enforce
Before promising a restriction, read schema help collections policy and p2p help scope. A node a person joins can expose more than one app's data. If the request is "share this with my team and nothing else" and the node can't limit that, say so before building and offer what it can do. Never describe a restriction as in place until you have seen it refuse someone. Test the forbidden action from a different identity, next to an allowed one; a success alone proves half.
Next: package-pack.
04 同仓库更多 Skills
write_plugin
暂无简介
use-database
Load before designing an app's data. What DefraDB does for you, and how to shape collections.
plan-work
Load first when asked to build or automate an app for people. Sets the checks and build order.
package-pack
Load when a working app should become a pack, or when installing or changing a pack. Export, check, install, versions.
diagnose-node
Load when a trigger, tool, request or session didn't work as expected. Gives the order of checks.
design_page
暂无简介