Menu
Guidelines for maintaining single sources of truth and using signposting to connect documentation without duplication
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Helps users connect and use a service in Rebel when it isn't already in the built-in connector catalog. Acts as an expert advisor — runs the full build-vs-buy check (catalog, MCP Registry, community) before scaffolding a custom MCP server and guiding research, implementation, security review, and contribution.
Guides users through adding new tools or capabilities to an existing connector (MCP server). Handles eligibility, workspace setup, connector research, implementation via Software Engineer workflow, local testing, and PR submission with an extension-specific template.
Capture citable sources (meetings, documents, files, media, web content) as structured files in memory/sources/ with provenance metadata for traceability.
Help users celebrate impactful wins and surface important learnings by analyzing their recent communications and activities.
Evaluate a finalised meeting transcript and distribute relevant content to other spaces, deciding per space whether to copy the full transcript, write a sanitised summary, or skip.
Semi-autonomous maintenance skill that identifies stale content, consolidates duplicated information, safely keeps Chief-of-Staff README concise, and maintains source file hygiene in any space's memory system.
| name | signposting-to-single-source-of-truth |
| description | Guidelines for maintaining single sources of truth and using signposting to connect documentation without duplication |
| last_updated | "2025-10-30T00:00:00.000Z" |
| tools_required | [] |
| dependencies | [] |
| agent_type | main_agent |
Core rule: Each piece of information should have one canonical location. Link to it rather than duplicating content.
Benefits: Reduces maintenance burden, prevents inconsistencies, improves navigation.
documentation-update.md - keeping documentation current../../help-for-humans/terminology.md - includes wikilink syntax and cross-referencing examplesInclude locally: Essential context, brief summaries (2-3 sentences max), critical frequently-needed information
Signpost instead: Detailed specifications, implementation details, frequently-changing content, deep technical details
Memory example (v3):
README.md: high-frequency facts and brief summaries that should auto-load (50%+ utility).memory/topics/ rather than duplicating.Chief-of-Staff/memory/topics/ and are linked from the top-level README.md.<Space Name>/memory/topics/ and are linked from that space's README.md.memory/sources/) are canonical — like code; topics and summaries are derived from them.Use bullet lists with 1-sentence context:
Documentation:
- [write-planning-doc](write-planning-doc/SKILL.md) - for writing ephemeral decision/planning docs
- [reference/AUTHENTICATION_SECURITY](../reference/AUTHENTICATION_SECURITY/SKILL.md) - security implementation details
Format: Use filestem (without .md extension) as link text. Include relative path in link text when it adds useful context.
Code:
- `src/utils/auth.ts` - see `validateToken()` function for validation logic
External:
- [React Hook Form docs](https://react-hook-form.com/) - for advanced form patterns
When creating new documentation or signposts: