cx-internal-vs-external-knowledge

SKILLWorkflowcommunity
v0.0.0rulebase-coMITUpdated 1mo agoSource →

Use to separate customer help centre content from internal agent wiki, define what belongs where, and stop wrong internal docs from leaking into customer-facing answers. Trigger for "help centre vs internal wiki", agent documentation duplication, what should be public KB, internal SOP leaking to cus

Community-submitted skill. Not yet reviewed by the Forge team. Full prompt content may not be available.Request review →
1Repo stars
1Clients
1Formats
1mo agoLast update
Skill
Authorrulebase-co
Version0.0.0
LicenseMIT
CategoryWorkflow
Formatsskill.md
PromptNot published
Compatibility
Claude✓ Supported
Cursor—
Copilot—
ChatGPT—
Gemini—
About

Use to separate customer help centre content from internal agent wiki, define what belongs where, and stop wrong internal docs from leaking into customer-facing answers. Trigger for "help centre vs internal wiki", agent documentation duplication, what should be public KB, internal SOP leaking to customers, policy vs procedure split, or grounding AI on the wrong knowledge base.

Keywords
skillclaude

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.