Public content policy

September 18, 2026 · View on GitHub

Note

📘 ClickUp Companion, last synced 2026-08-27

This document is mirrored in the NaNLABS internal ClickUp workspace for cross-team discovery and execution logging.

ClickUp is the cross-team discovery + execution-log surface. This repo doc is the co-located implementation reference (close to the code). When you update one, sync the other and bump the last synced date above.

Public content policy — nanlabs/agent-toolkit

This repository is public. Anything merged here is visible on the internet.

Allowed

  • Generic skills, agents, plugins, and official hosted MCP configs that help NaNLABS (and the community) work with AI clients.
  • Documentation that does not expose private process, client names under NDA, or internal URLs.
  • Generic ClickUp integration guidance is allowed, but direct internal workspace/document URLs are forbidden.
  • Env-var names and placeholder contracts (for example ${CLICKUP_API_TOKEN}).
  • Open-source licenses and attributed third-party excerpts that are redistribution-safe.

Forbidden

  • Secrets: API keys, PATs, passwords, private keys, session cookies.
  • Private hostnames, bastion addresses, internal IP ranges, or non-public VPN endpoints.
  • Client-confidential workflows, credentials, or data samples.
  • Unredacted screenshots or logs containing tokens or PII.
  • Copying internal-only workstation content without a scrub review.

Review gate

validate-public-content.py uses an intentionally empty allowlist. Any reviewed exception must name the exact tracked path and forbidden pattern and include a documented reason in the validator source.

Before merging content migrated from internal-workstation:

  1. Run bash scripts/secret-scan.sh, python3 scripts/validate-skills.py, and python3 scripts/validate-public-content.py.
  2. Confirm GitHub secret scanning / push protection remain enabled.
  3. Mark the skill/plugin as public: true in catalogs/skill-catalog.yaml only after scrub.
  4. If content must stay private, keep it on workstation, L2 packs, or a private project marketplace — not in this public repository.

Companion marketplace (decision)

Decision (2026-07-30): do not create a private companion marketplace yet.

Keep private content inWhen
internal-workstation (L1 AI home)Internal-only skills/procedures still dual-railed
L2 / project overlaysClient or initiative-specific packs
Future private marketplace repoOnly if private corpus volume or sharing needs exceed workstation + L2

Revisit when cutover (#23) or enterprise packs force multi-team distribution of non-public skills. Until then, scrub-or-exclude is enough for agent-toolkit.

Reporting

If you find sensitive material in this repo, follow SECURITY.md — do not discuss exploit details in a public issue.