Public-Private Boundary Review
Review both content and provenance. Renaming an internal identifier does not make proprietary logic, data, or operational knowledge public.
Workflow
- Define the intended public artifact, audience, license, and source repositories.
- Inventory copied, adapted, generated, and independently authored material.
- Check license and authorization for every non-original source. Treat absent permission as a blocker, not an invitation to sanitize.
- Scan content and history in scope for:
- credentials, tokens, keys, cookies, connection strings, and personal data
- private repository URLs, absolute local paths, account IDs, project IDs, hostnames, emails, and internal ticket references
- client names, proprietary schemas, business rules, architecture contracts, incidents, logs, screenshots, and production configuration
- claims that confuse repository code with testing, deployment, availability, or outcomes
- Recommend a disposition. Replace only ordinary incidental identifiers. For proprietary substance, remove it and independently author from public sources or keep it in a private overlay. Edit files only when the request asks for redaction.
- After an authorized redaction, re-run tests and documentation checks so safety edits do not leave broken artifacts.
- Report blockers, safe-to-publish items, and facts requiring owner or counsel confirmation.
Output
Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.
Use BLOCK, REVIEW, or CLEAR per finding, with location, risk, evidence, and disposition. A CLEAR verdict means no issue was found in the reviewed scope; it is not a legal opinion or proof that unreviewed history is safe. Never quote a secret in a finding: give its type and location, and mask the value.
Example
Synthetic example; not an observed client result.
Input: A draft guide includes an internal dataset identifier.
Output: Remove or generalize the private identifier before public exposure. Keep any needed operational detail in its owning private context.
1---2name: review-public-boundary3description: "Reviews material before public exposure when asked to check for secrets, private identifiers, proprietary text, or unsupported claims; keeps private context out of public artifacts."4license: MIT5metadata:6 source: https://skillmd.com/skills/jovanipink/review-public-boundary7 author: "Measured Studios"8 version: "0.19.0"9 plugin: "measured-quality"10 invocation: "implicit"11 provenance: "original"12 risk_class: "read-only"13---1415# Public-Private Boundary Review1617Review both content and provenance. Renaming an internal identifier does not make proprietary logic, data, or operational knowledge public.1819## Workflow20211. Define the intended public artifact, audience, license, and source repositories.222. Inventory copied, adapted, generated, and independently authored material.233. Check license and authorization for every non-original source. Treat absent permission as a blocker, not an invitation to sanitize.244. Scan content and history in scope for:25 - credentials, tokens, keys, cookies, connection strings, and personal data26 - private repository URLs, absolute local paths, account IDs, project IDs, hostnames, emails, and internal ticket references27 - client names, proprietary schemas, business rules, architecture contracts, incidents, logs, screenshots, and production configuration28 - claims that confuse repository code with testing, deployment, availability, or outcomes295. Recommend a disposition. Replace only ordinary incidental identifiers. For proprietary substance, remove it and independently author from public sources or keep it in a private overlay. Edit files only when the request asks for redaction.306. After an authorized redaction, re-run tests and documentation checks so safety edits do not leave broken artifacts.317. Report blockers, safe-to-publish items, and facts requiring owner or counsel confirmation.3233## Output3435Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.3637Use `BLOCK`, `REVIEW`, or `CLEAR` per finding, with location, risk, evidence, and disposition. A `CLEAR` verdict means no issue was found in the reviewed scope; it is not a legal opinion or proof that unreviewed history is safe. Never quote a secret in a finding: give its type and location, and mask the value.3839## Example4041Synthetic example; not an observed client result.4243Input: A draft guide includes an internal dataset identifier.4445Output: Remove or generalize the private identifier before public exposure. Keep any needed operational detail in its owning private context.