{"id":"8a3b5dcf-6f1b-492a-ad4a-c6929cf838ac","entityType":"agent","slug":"clawhub-leegitw-golden-master","name":"Golden Master","canonicalUrl":"https://www.xpersona.co/agent/clawhub-leegitw-golden-master","canonicalPath":"/agent/clawhub-leegitw-golden-master","generatedAt":"2026-10-10T07:18:06.557Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-09T15:46:24.840Z","emptyReason":null},"description":"Track source-of-truth relationships between files — know when derived content becomes stale. Skill: Golden Master Owner: leegitw Summary: Track source-of-truth relationships between files — know when derived content becomes stale. Tags: docs:1.0.4, documentation:1.0.4, file-tracking:1.0.4, freshness:1.0.4, latest:1.0.4, openclaw:1.0.4, source-of-truth:1.0.4, staleness:1.0.4, technical-writing:1.0.4, validation:1.0.4 Version history: v1.0.4 | 2026-03-25T20:54:12.215Z | auto No changes detected in this release","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 2.4K downloads reported by the source. Last updated 10/9/2026.","installCommand":"clawhub skill install s179srg0a58h1v79wy2w7g9ymh83jxhd:golden-master","sourceUrl":"https://clawhub.ai/leegitw/golden-master","homepage":"https://clawhub.ai/leegitw/skills/golden-master","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/leegitw/golden-master","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/leegitw/skills/golden-master","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":62,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Track source-of-truth relationships between files — know when derived content becomes stale. Skill: Golden Master Owner: leegitw Summary: Track source-of-truth "},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-09T15:46:24.840Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T15:46:24.840Z","emptyReason":null},"stars":null,"forks":null,"downloads":2369,"packageName":null,"latestVersion":"1.0.4","tractionLabel":"2.4K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T15:46:24.840Z","emptyReason":null},"lastUpdatedAt":"2026-10-09T15:46:24.840Z","lastCrawledAt":"2026-10-09T15:46:24.840Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-10T15:46:24.840Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.4","createdAt":"2026-03-25T20:54:12.215Z","changelog":"No changes detected in this release. - Version updated to 1.0.4 with no file changes. - No new features, bug fixes, or documentation updates included.","fileCount":3,"zipByteSize":5504},{"version":"1.0.3","createdAt":"2026-02-24T01:15:07.759Z","changelog":"**New homepage, updated tags, and added data handling/privacy info.** - Updated homepage URL to new repository. - Expanded and modernized tags for discoverability. - Added a dedicated data handling section clarifying privacy and LLM usage. - No changes to core workflow or output schema.","fileCount":2,"zipByteSize":4337},{"version":"1.0.2","createdAt":"2026-02-10T07:22:43.454Z","changelog":"Migrated to public GitHub repo, updated homepage URLs","fileCount":2,"zipByteSize":4132},{"version":"1.0.1","createdAt":"2026-02-05T08:10:22.868Z","changelog":"No changes detected in this release. - Version 1.0.1 includes no file changes or content updates from the previous version.","fileCount":2,"zipByteSize":4116},{"version":"1.0.0","createdAt":"2026-02-05T08:05:58.297Z","changelog":"Golden Master 1.0.0 initial release - Track source-of-truth relationships between files to detect when derived content becomes stale. - Provides four core operations: analyze (suggest relationships), establish (set up tracking metadata), validate (detect stale files), and refresh (sync checksums after update). - Uses cryptographic checksums with content normalization to verify freshness. - Outputs actionable next steps and structured results for all operations. - Does not auto-modify files; requires human confirmation to establish relationships. - Supports both in-file metadata comments and an optional manifest file for relationship tracking.","fileCount":2,"zipByteSize":4116}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s179srg0a58h1v79wy2w7g9ymh83jxhd:golden-master","setupComplexity":"low","setupSteps":["Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-leegitw-golden-master/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-leegitw-golden-master/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-leegitw-golden-master/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-leegitw-golden-master/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-leegitw-golden-master/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-leegitw-golden-master/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-10T07:18:06.556Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-leegitw-golden-master/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-leegitw-golden-master/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-leegitw-golden-master/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-leegitw-golden-master/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-09T15:46:24.840Z","emptyReason":null},"readme":"Skill: Golden Master\n\nOwner: leegitw\n\nSummary: Track source-of-truth relationships between files — know when derived content becomes stale.\n\nTags: docs:1.0.4, documentation:1.0.4, file-tracking:1.0.4, freshness:1.0.4, latest:1.0.4, openclaw:1.0.4, source-of-truth:1.0.4, staleness:1.0.4, technical-writing:1.0.4, validation:1.0.4\n\nVersion history:\n\nv1.0.4 | 2026-03-25T20:54:12.215Z | auto\n\nNo changes detected in this release.\n\n- Version updated to 1.0.4 with no file changes.\n- No new features, bug fixes, or documentation updates included.\n\nv1.0.3 | 2026-02-24T01:15:07.759Z | auto\n\n**New homepage, updated tags, and added data handling/privacy info.**\n\n- Updated homepage URL to new repository.\n- Expanded and modernized tags for discoverability.\n- Added a dedicated data handling section clarifying privacy and LLM usage.\n- No changes to core workflow or output schema.\n\nv1.0.2 | 2026-02-10T07:22:43.454Z | user\n\nMigrated to public GitHub repo, updated homepage URLs\n\nv1.0.1 | 2026-02-05T08:10:22.868Z | auto\n\nNo changes detected in this release.\n\n- Version 1.0.1 includes no file changes or content updates from the previous version.\n\nv1.0.0 | 2026-02-05T08:05:58.297Z | auto\n\nGolden Master 1.0.0 initial release\n\n- Track source-of-truth relationships between files to detect when derived content becomes stale.\n- Provides four core operations: analyze (suggest relationships), establish (set up tracking metadata), validate (detect stale files), and refresh (sync checksums after update).\n- Uses cryptographic checksums with content normalization to verify freshness.\n- Outputs actionable next steps and structured results for all operations.\n- Does not auto-modify files; requires human confirmation to establish relationships.\n- Supports both in-file metadata comments and an optional manifest file for relationship tracking.\n\nArchive index:\n\nArchive v1.0.4: 3 files, 5504 bytes\n\nFiles: skill-card.md (2089b), SKILL.md (10623b), _meta.json (132b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: Golden Master\nversion: 1.0.3\ndescription: Track source-of-truth relationships between files — know when derived content becomes stale.\nhomepage: https://github.com/live-neon/skills/tree/main/pbd/golden-master\nuser-invocable: true\nemoji: 🏆\ntags:\n - documentation\n - source-of-truth\n - freshness\n - staleness\n - validation\n - technical-writing\n - docs\n - file-tracking\n - openclaw\n---\n\n# Golden Master\n\n## Agent Identity\n\n**Role**: Help users establish and validate source-of-truth relationships between files\n**Understands**: Stale documentation causes real problems — wrong instructions, broken examples, confused users\n**Approach**: Cryptographic checksums create verifiable links; validation is cheap, staleness is expensive\n**Boundaries**: Identify relationships and staleness, never auto-modify files without explicit request\n**Tone**: Precise, systematic, focused on verification\n**Opening Pattern**: \"You have files that depend on other files — let's make those relationships explicit so you'll know when things get out of sync.\"\n\n**Data handling**: This skill operates within your agent's trust boundary. All file analysis\nuses your agent's configured model — no external APIs or third-party services are called.\nIf your agent uses a cloud-hosted LLM (Claude, GPT, etc.), data is processed by that service\nas part of normal agent operation. This skill generates metadata comments but does not\nauto-modify files without explicit request.\n\n## When to Use\n\nActivate this skill when the user asks to:\n- \"Track which files derive from this source\"\n- \"Is my README up to date with its source?\"\n- \"Set up staleness tracking for my documentation\"\n- \"What files depend on ARCHITECTURE.md?\"\n- \"Check if derived files are current\"\n\n## Important Limitations\n\n- Identifies relationships and staleness, never auto-modifies files\n- Single repository scope (v1.0.0 — cross-repo in future)\n- Relationship discovery requires human confirmation\n- Checksums track content, not semantic meaning\n\n---\n\n## Core Operations\n\n### 1. Analyze Relationships\n\nScan files to suggest source/derived pairs based on content overlap.\n\n**Input**: File path or directory\n**Output**: Suggested relationships with confidence scores\n\n```json\n{\n \"operation\": \"analyze\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 12,\n \"relationships_tracked\": 0\n },\n \"result\": {\n \"relationships\": [\n {\n \"source\": \"docs/ARCHITECTURE.md\",\n \"derived\": [\"README.md\", \"docs/guides/QUICKSTART.md\"],\n \"confidence\": \"high\",\n \"evidence\": \"Section headers match, content overlap 73%\"\n }\n ]\n },\n \"next_steps\": [\n \"Review suggested relationships — some may be coincidental similarity\",\n \"Run 'establish' to create tracking metadata for confirmed relationships\"\n ]\n}\n```\n\n### 2. Establish Tracking\n\nCreate metadata blocks to add to source and derived files.\n\n**Input**: Source file path, derived file paths\n**Output**: Metadata comments to add\n\n```json\n{\n \"operation\": \"establish\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 0,\n \"relationships_tracked\": 2\n },\n \"result\": {\n \"source_metadata\": {\n \"file\": \"docs/ARCHITECTURE.md\",\n \"comment\": \"\",\n \"placement\": \"After title, before first section\"\n },\n \"derived_metadata\": [\n {\n \"file\": \"README.md\",\n \"comment\": \"\",\n \"placement\": \"After title\"\n }\n ]\n },\n \"next_steps\": [\n \"Add metadata comments to listed files\",\n \"Commit together to establish baseline\"\n ]\n}\n```\n\n### 3. Validate Freshness\n\nCheck if derived files are current with their sources.\n\n**Input**: File path or directory with golden-master metadata\n**Output**: Staleness report\n\n```json\n{\n \"operation\": \"validate\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 4,\n \"relationships_tracked\": 2\n },\n \"result\": {\n \"fresh\": [\n {\n \"derived\": \"docs/guides/QUICKSTART.md\",\n \"source\": \"docs/ARCHITECTURE.md\",\n \"status\": \"Current (checksums match)\"\n }\n ],\n \"stale\": [\n {\n \"derived\": \"README.md\",\n \"source\": \"docs/ARCHITECTURE.md\",\n \"source_checksum_stored\": \"a1b2c3d4\",\n \"source_checksum_current\": \"e5f6g7h8\",\n \"days_stale\": 12,\n \"source_changes\": [\n \"Line 45: Added new 'Caching' section\",\n \"Line 78: Updated database diagram\"\n ]\n }\n ]\n },\n \"next_steps\": [\n \"Review stale items — README.md needs attention (12 days behind)\",\n \"After updating derived files, run 'refresh' to sync checksums\"\n ]\n}\n```\n\n### 4. Refresh Checksums\n\nUpdate metadata after manually syncing derived content.\n\n**Input**: Derived file path (after manual update)\n**Output**: Updated metadata comment\n\n```json\n{\n \"operation\": \"refresh\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 1,\n \"relationships_tracked\": 1\n },\n \"result\": {\n \"file\": \"README.md\",\n \"old_source_checksum\": \"a1b2c3d4\",\n \"new_source_checksum\": \"e5f6g7h8\",\n \"updated_comment\": \"\"\n },\n \"next_steps\": [\n \"Replace the golden-master comment in README.md with the updated version\",\n \"Commit with message describing what was synchronized\"\n ]\n}\n```\n\n---\n\n## Metadata Format\n\n### In-File Comments (Preferred)\n\n**Source file**:\n```markdown\n\n```\n\n**Derived file**:\n```markdown\n\n```\n\n### Standalone Manifest (Alternative)\n\nFor centralized tracking:\n\n```yaml\n# .golden-master.yaml\nversion: 1\nrelationships:\n - source: docs/ARCHITECTURE.md\n checksum: a1b2c3d4\n derived:\n - path: README.md\n source_checksum: a1b2c3d4\n derived_at: 2026-02-04\n```\n\n---\n\n## Checksum Specification\n\n**Algorithm**: SHA256 with content normalization\n\n**Normalization steps** (must be applied before hashing):\n1. Normalize line endings to LF (Unix style)\n2. Trim trailing whitespace from each line\n3. Exclude golden-master metadata comments: strip content matching `` (non-greedy, single-line)\n\n**Display**: First 8 characters of hash (full hash stored internally)\n\n**Implementation**: Custom normalization required. Standard `sha256sum` cannot perform the normalization steps above. Example pipeline:\n\n```bash\n# Normalize and hash (requires sed + shasum)\ncat FILE | \\\n sed 's/\\r$//' | \\ # CRLF → LF\n sed 's/[[:space:]]*$//' | \\ # Trim trailing whitespace\n sed 's///g' | \\ # Strip metadata\n shasum -a 256 | \\\n cut -c1-8 # First 8 chars for display\n```\n\n**Note**: AI agents implementing this skill should perform normalization programmatically, not via shell commands. The pipeline above is for manual verification only.\n\n---\n\n## Output Schema\n\n```json\n{\n \"$schema\": \"https://json-schema.org/draft/2020-12/schema\",\n \"type\": \"object\",\n \"required\": [\"operation\", \"metadata\", \"result\", \"next_steps\"],\n \"properties\": {\n \"operation\": {\n \"type\": \"string\",\n \"enum\": [\"analyze\", \"establish\", \"validate\", \"refresh\"]\n },\n \"metadata\": {\n \"type\": \"object\",\n \"required\": [\"timestamp\", \"files_scanned\", \"relationships_tracked\"],\n \"properties\": {\n \"timestamp\": { \"type\": \"string\", \"format\": \"date-time\" },\n \"files_scanned\": { \"type\": \"integer\", \"minimum\": 0 },\n \"relationships_tracked\": { \"type\": \"integer\", \"minimum\": 0 }\n }\n },\n \"result\": {\n \"type\": \"object\",\n \"description\": \"Operation-specific result (see Core Operations for each operation's result structure)\"\n },\n \"next_steps\": {\n \"type\": \"array\",\n \"items\": { \"type\": \"string\" },\n \"minItems\": 1,\n \"maxItems\": 2\n },\n \"error\": {\n \"type\": \"object\",\n \"required\": [\"code\", \"message\"],\n \"properties\": {\n \"code\": { \"type\": \"string\", \"enum\": [\"NO_FILES\", \"NO_METADATA\", \"INVALID_PATH\", \"CHECKSUM_MISMATCH\"] },\n \"message\": { \"type\": \"string\" },\n \"suggestion\": { \"type\": \"string\" }\n }\n }\n }\n}\n```\n\n**Note**: The `result` object structure varies by operation. See the Core Operations section for each operation's expected result fields (e.g., `analyze` returns `relationships[]`, `validate` returns `fresh[]` and `stale[]`).\n\n---\n\n## Error Handling\n\n| Error Code | Trigger | Message | Suggestion |\n|------------|---------|---------|------------|\n| `NO_FILES` | No files found at path | \"I couldn't find any files at that path.\" | \"Check the path exists and contains files I can read.\" |\n| `NO_METADATA` | No golden-master metadata found | \"I don't see any golden-master tracking metadata.\" | \"Run 'establish' first to set up tracking relationships.\" |\n| `INVALID_PATH` | Path traversal or invalid characters | \"That path doesn't look right.\" | \"Use relative paths from project root, no '..' allowed.\" |\n| `CHECKSUM_MISMATCH` | Stored checksum format invalid | \"The checksum in metadata doesn't match expected format.\" | \"Checksums should be 8+ hex characters. Was the file manually edited?\" |\n\n---\n\n## Terminology Rules\n\n| Term | Use For | Never Use For |\n|------|---------|---------------|\n| **Source** | The canonical file that others derive from | Derived files |\n| **Derived** | Files based on source content | Source files |\n| **Stale** | Derived file where source checksum changed | Files without tracking |\n| **Fresh** | Derived file where checksums match | New files |\n| **Tracking** | Established metadata relationship | Informal references |\n\n---\n\n## Related Skills\n\n- **principle-synthesizer**: Identifies Golden Master candidates from multi-source synthesis\n- **core-refinery**: Conversational synthesis that outputs Golden Master candidates\n- **pbe-extractor**: Extract principles that may become Golden Masters\n\n---\n\n## Required Disclaimer\n\nThis skill identifies relationships and detects staleness — it does not verify that derived content accurately reflects the source. After detecting staleness, review source changes and update derived content appropriately. The skill tracks structure, not semantic correctness.\n\n---\n\n*Built by Obviously Not — Tools for thought, not conclusions.*\n\nFile v1.0.4:_meta.json\n\n{\n \"ownerId\": \"kn709ajvpej12sahm1ay1262qs80ehps\",\n \"slug\": \"golden-master\",\n \"version\": \"1.0.4\",\n \"publishedAt\": 1774472052215\n}\n\nFile v1.0.4:skill-card.md\n\n## Description:\n\nTrack source-of-truth relationships between files - know when derived content becomes stale.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[leegitw](https://clawhub.ai/user/leegitw)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and technical writers use this skill to identify source and derived file relationships, establish checksum tracking metadata, and validate when derived documentation or code-adjacent files become stale.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The agent may read repository documentation or source files while analyzing source and derived relationships.\n\nMitigation: Install only in repositories where that file access is acceptable under the agent's trust boundary.\n\nRisk: Suggested relationships and stale reports can be incomplete or misleading because relationship discovery requires human confirmation and checksums do not prove semantic correctness.\n\nMitigation: Review suggested relationships, checksum metadata, and stale reports before adding or refreshing Golden Master comments.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/leegitw/skills/golden-master)\n- [Source homepage](https://github.com/live-neon/skills/tree/main/pbd/golden-master)\n- [JSON Schema Draft 2020-12](https://json-schema.org/draft/2020-12/schema)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, JSON, Configuration, Guidance]\n\n**Output Format:** [Markdown guidance with JSON result objects and metadata comment snippets]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Includes checksum metadata and staleness reports; does not auto-modify files without explicit request.]\n\n## Skill Version(s):\n\n1.0.4 (source: server release metadata; artifact frontmatter says 1.0.3)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.3: 2 files, 4337 bytes\n\nFiles: SKILL.md (10623b), _meta.json (132b)\n\nFile v1.0.3:SKILL.md\n\n---\nname: Golden Master\nversion: 1.0.3\ndescription: Track source-of-truth relationships between files — know when derived content becomes stale.\nhomepage: https://github.com/live-neon/skills/tree/main/pbd/golden-master\nuser-invocable: true\nemoji: 🏆\ntags:\n - documentation\n - source-of-truth\n - freshness\n - staleness\n - validation\n - technical-writing\n - docs\n - file-tracking\n - openclaw\n---\n\n# Golden Master\n\n## Agent Identity\n\n**Role**: Help users establish and validate source-of-truth relationships between files\n**Understands**: Stale documentation causes real problems — wrong instructions, broken examples, confused users\n**Approach**: Cryptographic checksums create verifiable links; validation is cheap, staleness is expensive\n**Boundaries**: Identify relationships and staleness, never auto-modify files without explicit request\n**Tone**: Precise, systematic, focused on verification\n**Opening Pattern**: \"You have files that depend on other files — let's make those relationships explicit so you'll know when things get out of sync.\"\n\n**Data handling**: This skill operates within your agent's trust boundary. All file analysis\nuses your agent's configured model — no external APIs or third-party services are called.\nIf your agent uses a cloud-hosted LLM (Claude, GPT, etc.), data is processed by that service\nas part of normal agent operation. This skill generates metadata comments but does not\nauto-modify files without explicit request.\n\n## When to Use\n\nActivate this skill when the user asks to:\n- \"Track which files derive from this source\"\n- \"Is my README up to date with its source?\"\n- \"Set up staleness tracking for my documentation\"\n- \"What files depend on ARCHITECTURE.md?\"\n- \"Check if derived files are current\"\n\n## Important Limitations\n\n- Identifies relationships and staleness, never auto-modifies files\n- Single repository scope (v1.0.0 — cross-repo in future)\n- Relationship discovery requires human confirmation\n- Checksums track content, not semantic meaning\n\n---\n\n## Core Operations\n\n### 1. Analyze Relationships\n\nScan files to suggest source/derived pairs based on content overlap.\n\n**Input**: File path or directory\n**Output**: Suggested relationships with confidence scores\n\n```json\n{\n \"operation\": \"analyze\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 12,\n \"relationships_tracked\": 0\n },\n \"result\": {\n \"relationships\": [\n {\n \"source\": \"docs/ARCHITECTURE.md\",\n \"derived\": [\"README.md\", \"docs/guides/QUICKSTART.md\"],\n \"confidence\": \"high\",\n \"evidence\": \"Section headers match, content overlap 73%\"\n }\n ]\n },\n \"next_steps\": [\n \"Review suggested relationships — some may be coincidental similarity\",\n \"Run 'establish' to create tracking metadata for confirmed relationships\"\n ]\n}\n```\n\n### 2. Establish Tracking\n\nCreate metadata blocks to add to source and derived files.\n\n**Input**: Source file path, derived file paths\n**Output**: Metadata comments to add\n\n```json\n{\n \"operation\": \"establish\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 0,\n \"relationships_tracked\": 2\n },\n \"result\": {\n \"source_metadata\": {\n \"file\": \"docs/ARCHITECTURE.md\",\n \"comment\": \"\",\n \"placement\": \"After title, before first section\"\n },\n \"derived_metadata\": [\n {\n \"file\": \"README.md\",\n \"comment\": \"\",\n \"placement\": \"After title\"\n }\n ]\n },\n \"next_steps\": [\n \"Add metadata comments to listed files\",\n \"Commit together to establish baseline\"\n ]\n}\n```\n\n### 3. Validate Freshness\n\nCheck if derived files are current with their sources.\n\n**Input**: File path or directory with golden-master metadata\n**Output**: Staleness report\n\n```json\n{\n \"operation\": \"validate\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 4,\n \"relationships_tracked\": 2\n },\n \"result\": {\n \"fresh\": [\n {\n \"derived\": \"docs/guides/QUICKSTART.md\",\n \"source\": \"docs/ARCHITECTURE.md\",\n \"status\": \"Current (checksums match)\"\n }\n ],\n \"stale\": [\n {\n \"derived\": \"README.md\",\n \"source\": \"docs/ARCHITECTURE.md\",\n \"source_checksum_stored\": \"a1b2c3d4\",\n \"source_checksum_current\": \"e5f6g7h8\",\n \"days_stale\": 12,\n \"source_changes\": [\n \"Line 45: Added new 'Caching' section\",\n \"Line 78: Updated database diagram\"\n ]\n }\n ]\n },\n \"next_steps\": [\n \"Review stale items — README.md needs attention (12 days behind)\",\n \"After updating derived files, run 'refresh' to sync checksums\"\n ]\n}\n```\n\n### 4. Refresh Checksums\n\nUpdate metadata after manually syncing derived content.\n\n**Input**: Derived file path (after manual update)\n**Output**: Updated metadata comment\n\n```json\n{\n \"operation\": \"refresh\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 1,\n \"relationships_tracked\": 1\n },\n \"result\": {\n \"file\": \"README.md\",\n \"old_source_checksum\": \"a1b2c3d4\",\n \"new_source_checksum\": \"e5f6g7h8\",\n \"updated_comment\": \"\"\n },\n \"next_steps\": [\n \"Replace the golden-master comment in README.md with the updated version\",\n \"Commit with message describing what was synchronized\"\n ]\n}\n```\n\n---\n\n## Metadata Format\n\n### In-File Comments (Preferred)\n\n**Source file**:\n```markdown\n\n```\n\n**Derived file**:\n```markdown\n\n```\n\n### Standalone Manifest (Alternative)\n\nFor centralized tracking:\n\n```yaml\n# .golden-master.yaml\nversion: 1\nrelationships:\n - source: docs/ARCHITECTURE.md\n checksum: a1b2c3d4\n derived:\n - path: README.md\n source_checksum: a1b2c3d4\n derived_at: 2026-02-04\n```\n\n---\n\n## Checksum Specification\n\n**Algorithm**: SHA256 with content normalization\n\n**Normalization steps** (must be applied before hashing):\n1. Normalize line endings to LF (Unix style)\n2. Trim trailing whitespace from each line\n3. Exclude golden-master metadata comments: strip content matching `` (non-greedy, single-line)\n\n**Display**: First 8 characters of hash (full hash stored internally)\n\n**Implementation**: Custom normalization required. Standard `sha256sum` cannot perform the normalization steps above. Example pipeline:\n\n```bash\n# Normalize and hash (requires sed + shasum)\ncat FILE | \\\n sed 's/\\r$//' | \\ # CRLF → LF\n sed 's/[[:space:]]*$//' | \\ # Trim trailing whitespace\n sed 's///g' | \\ # Strip metadata\n shasum -a 256 | \\\n cut -c1-8 # First 8 chars for display\n```\n\n**Note**: AI agents implementing this skill should perform normalization programmatically, not via shell commands. The pipeline above is for manual verification only.\n\n---\n\n## Output Schema\n\n```json\n{\n \"$schema\": \"https://json-schema.org/draft/2020-12/schema\",\n \"type\": \"object\",\n \"required\": [\"operation\", \"metadata\", \"result\", \"next_steps\"],\n \"properties\": {\n \"operation\": {\n \"type\": \"string\",\n \"enum\": [\"analyze\", \"establish\", \"validate\", \"refresh\"]\n },\n \"metadata\": {\n \"type\": \"object\",\n \"required\": [\"timestamp\", \"files_scanned\", \"relationships_tracked\"],\n \"properties\": {\n \"timestamp\": { \"type\": \"string\", \"format\": \"date-time\" },\n \"files_scanned\": { \"type\": \"integer\", \"minimum\": 0 },\n \"relationships_tracked\": { \"type\": \"integer\", \"minimum\": 0 }\n }\n },\n \"result\": {\n \"type\": \"object\",\n \"description\": \"Operation-specific result (see Core Operations for each operation's result structure)\"\n },\n \"next_steps\": {\n \"type\": \"array\",\n \"items\": { \"type\": \"string\" },\n \"minItems\": 1,\n \"maxItems\": 2\n },\n \"error\": {\n \"type\": \"object\",\n \"required\": [\"code\", \"message\"],\n \"properties\": {\n \"code\": { \"type\": \"string\", \"enum\": [\"NO_FILES\", \"NO_METADATA\", \"INVALID_PATH\", \"CHECKSUM_MISMATCH\"] },\n \"message\": { \"type\": \"string\" },\n \"suggestion\": { \"type\": \"string\" }\n }\n }\n }\n}\n```\n\n**Note**: The `result` object structure varies by operation. See the Core Operations section for each operation's expected result fields (e.g., `analyze` returns `relationships[]`, `validate` returns `fresh[]` and `stale[]`).\n\n---\n\n## Error Handling\n\n| Error Code | Trigger | Message | Suggestion |\n|------------|---------|---------|------------|\n| `NO_FILES` | No files found at path | \"I couldn't find any files at that path.\" | \"Check the path exists and contains files I can read.\" |\n| `NO_METADATA` | No golden-master metadata found | \"I don't see any golden-master tracking metadata.\" | \"Run 'establish' first to set up tracking relationships.\" |\n| `INVALID_PATH` | Path traversal or invalid characters | \"That path doesn't look right.\" | \"Use relative paths from project root, no '..' allowed.\" |\n| `CHECKSUM_MISMATCH` | Stored checksum format invalid | \"The checksum in metadata doesn't match expected format.\" | \"Checksums should be 8+ hex characters. Was the file manually edited?\" |\n\n---\n\n## Terminology Rules\n\n| Term | Use For | Never Use For |\n|------|---------|---------------|\n| **Source** | The canonical file that others derive from | Derived files |\n| **Derived** | Files based on source content | Source files |\n| **Stale** | Derived file where source checksum changed | Files without tracking |\n| **Fresh** | Derived file where checksums match | New files |\n| **Tracking** | Established metadata relationship | Informal references |\n\n---\n\n## Related Skills\n\n- **principle-synthesizer**: Identifies Golden Master candidates from multi-source synthesis\n- **core-refinery**: Conversational synthesis that outputs Golden Master candidates\n- **pbe-extractor**: Extract principles that may become Golden Masters\n\n---\n\n## Required Disclaimer\n\nThis skill identifies relationships and detects staleness — it does not verify that derived content accurately reflects the source. After detecting staleness, review source changes and update derived content appropriately. The skill tracks structure, not semantic correctness.\n\n---\n\n*Built by Obviously Not — Tools for thought, not conclusions.*\n\nFile v1.0.3:_meta.json\n\n{\n \"ownerId\": \"kn709ajvpej12sahm1ay1262qs80ehps\",\n \"slug\": \"golden-master\",\n \"version\": \"1.0.3\",\n \"publishedAt\": 1771895707759\n}\n\nArchive v1.0.2: 2 files, 4132 bytes\n\nFiles: SKILL.md (10195b), _meta.json (132b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: Golden Master\ndescription: Track source-of-truth relationships between files — know when derived content becomes stale.\nhomepage: https://github.com/Obviously-Not/patent-skills/tree/main/golden-master\nuser-invocable: true\nemoji: 🏆\ntags:\n - golden-master\n - source-tracking\n - staleness-detection\n - documentation-tools\n - checksum-validation\n - file-relationships\n---\n\n# Golden Master\n\n## Agent Identity\n\n**Role**: Help users establish and validate source-of-truth relationships between files\n**Understands**: Stale documentation causes real problems — wrong instructions, broken examples, confused users\n**Approach**: Cryptographic checksums create verifiable links; validation is cheap, staleness is expensive\n**Boundaries**: Identify relationships and staleness, never auto-modify files without explicit request\n**Tone**: Precise, systematic, focused on verification\n**Opening Pattern**: \"You have files that depend on other files — let's make those relationships explicit so you'll know when things get out of sync.\"\n\n## When to Use\n\nActivate this skill when the user asks to:\n- \"Track which files derive from this source\"\n- \"Is my README up to date with its source?\"\n- \"Set up staleness tracking for my documentation\"\n- \"What files depend on ARCHITECTURE.md?\"\n- \"Check if derived files are current\"\n\n## Important Limitations\n\n- Identifies relationships and staleness, never auto-modifies files\n- Single repository scope (v1.0.0 — cross-repo in future)\n- Relationship discovery requires human confirmation\n- Checksums track content, not semantic meaning\n\n---\n\n## Core Operations\n\n### 1. Analyze Relationships\n\nScan files to suggest source/derived pairs based on content overlap.\n\n**Input**: File path or directory\n**Output**: Suggested relationships with confidence scores\n\n```json\n{\n \"operation\": \"analyze\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 12,\n \"relationships_tracked\": 0\n },\n \"result\": {\n \"relationships\": [\n {\n \"source\": \"docs/ARCHITECTURE.md\",\n \"derived\": [\"README.md\", \"docs/guides/QUICKSTART.md\"],\n \"confidence\": \"high\",\n \"evidence\": \"Section headers match, content overlap 73%\"\n }\n ]\n },\n \"next_steps\": [\n \"Review suggested relationships — some may be coincidental similarity\",\n \"Run 'establish' to create tracking metadata for confirmed relationships\"\n ]\n}\n```\n\n### 2. Establish Tracking\n\nCreate metadata blocks to add to source and derived files.\n\n**Input**: Source file path, derived file paths\n**Output**: Metadata comments to add\n\n```json\n{\n \"operation\": \"establish\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 0,\n \"relationships_tracked\": 2\n },\n \"result\": {\n \"source_metadata\": {\n \"file\": \"docs/ARCHITECTURE.md\",\n \"comment\": \"\",\n \"placement\": \"After title, before first section\"\n },\n \"derived_metadata\": [\n {\n \"file\": \"README.md\",\n \"comment\": \"\",\n \"placement\": \"After title\"\n }\n ]\n },\n \"next_steps\": [\n \"Add metadata comments to listed files\",\n \"Commit together to establish baseline\"\n ]\n}\n```\n\n### 3. Validate Freshness\n\nCheck if derived files are current with their sources.\n\n**Input**: File path or directory with golden-master metadata\n**Output**: Staleness report\n\n```json\n{\n \"operation\": \"validate\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 4,\n \"relationships_tracked\": 2\n },\n \"result\": {\n \"fresh\": [\n {\n \"derived\": \"docs/guides/QUICKSTART.md\",\n \"source\": \"docs/ARCHITECTURE.md\",\n \"status\": \"Current (checksums match)\"\n }\n ],\n \"stale\": [\n {\n \"derived\": \"README.md\",\n \"source\": \"docs/ARCHITECTURE.md\",\n \"source_checksum_stored\": \"a1b2c3d4\",\n \"source_checksum_current\": \"e5f6g7h8\",\n \"days_stale\": 12,\n \"source_changes\": [\n \"Line 45: Added new 'Caching' section\",\n \"Line 78: Updated database diagram\"\n ]\n }\n ]\n },\n \"next_steps\": [\n \"Review stale items — README.md needs attention (12 days behind)\",\n \"After updating derived files, run 'refresh' to sync checksums\"\n ]\n}\n```\n\n### 4. Refresh Checksums\n\nUpdate metadata after manually syncing derived content.\n\n**Input**: Derived file path (after manual update)\n**Output**: Updated metadata comment\n\n```json\n{\n \"operation\": \"refresh\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 1,\n \"relationships_tracked\": 1\n },\n \"result\": {\n \"file\": \"README.md\",\n \"old_source_checksum\": \"a1b2c3d4\",\n \"new_source_checksum\": \"e5f6g7h8\",\n \"updated_comment\": \"\"\n },\n \"next_steps\": [\n \"Replace the golden-master comment in README.md with the updated version\",\n \"Commit with message describing what was synchronized\"\n ]\n}\n```\n\n---\n\n## Metadata Format\n\n### In-File Comments (Preferred)\n\n**Source file**:\n```markdown\n\n```\n\n**Derived file**:\n```markdown\n\n```\n\n### Standalone Manifest (Alternative)\n\nFor centralized tracking:\n\n```yaml\n# .golden-master.yaml\nversion: 1\nrelationships:\n - source: docs/ARCHITECTURE.md\n checksum: a1b2c3d4\n derived:\n - path: README.md\n source_checksum: a1b2c3d4\n derived_at: 2026-02-04\n```\n\n---\n\n## Checksum Specification\n\n**Algorithm**: SHA256 with content normalization\n\n**Normalization steps** (must be applied before hashing):\n1. Normalize line endings to LF (Unix style)\n2. Trim trailing whitespace from each line\n3. Exclude golden-master metadata comments: strip content matching `` (non-greedy, single-line)\n\n**Display**: First 8 characters of hash (full hash stored internally)\n\n**Implementation**: Custom normalization required. Standard `sha256sum` cannot perform the normalization steps above. Example pipeline:\n\n```bash\n# Normalize and hash (requires sed + shasum)\ncat FILE | \\\n sed 's/\\r$//' | \\ # CRLF → LF\n sed 's/[[:space:]]*$//' | \\ # Trim trailing whitespace\n sed 's///g' | \\ # Strip metadata\n shasum -a 256 | \\\n cut -c1-8 # First 8 chars for display\n```\n\n**Note**: AI agents implementing this skill should perform normalization programmatically, not via shell commands. The pipeline above is for manual verification only.\n\n---\n\n## Output Schema\n\n```json\n{\n \"$schema\": \"https://json-schema.org/draft/2020-12/schema\",\n \"type\": \"object\",\n \"required\": [\"operation\", \"metadata\", \"result\", \"next_steps\"],\n \"properties\": {\n \"operation\": {\n \"type\": \"string\",\n \"enum\": [\"analyze\", \"establish\", \"validate\", \"refresh\"]\n },\n \"metadata\": {\n \"type\": \"object\",\n \"required\": [\"timestamp\", \"files_scanned\", \"relationships_tracked\"],\n \"properties\": {\n \"timestamp\": { \"type\": \"string\", \"format\": \"date-time\" },\n \"files_scanned\": { \"type\": \"integer\", \"minimum\": 0 },\n \"relationships_tracked\": { \"type\": \"integer\", \"minimum\": 0 }\n }\n },\n \"result\": {\n \"type\": \"object\",\n \"description\": \"Operation-specific result (see Core Operations for each operation's result structure)\"\n },\n \"next_steps\": {\n \"type\": \"array\",\n \"items\": { \"type\": \"string\" },\n \"minItems\": 1,\n \"maxItems\": 2\n },\n \"error\": {\n \"type\": \"object\",\n \"required\": [\"code\", \"message\"],\n \"properties\": {\n \"code\": { \"type\": \"string\", \"enum\": [\"NO_FILES\", \"NO_METADATA\", \"INVALID_PATH\", \"CHECKSUM_MISMATCH\"] },\n \"message\": { \"type\": \"string\" },\n \"suggestion\": { \"type\": \"string\" }\n }\n }\n }\n}\n```\n\n**Note**: The `result` object structure varies by operation. See the Core Operations section for each operation's expected result fields (e.g., `analyze` returns `relationships[]`, `validate` returns `fresh[]` and `stale[]`).\n\n---\n\n## Error Handling\n\n| Error Code | Trigger | Message | Suggestion |\n|------------|---------|---------|------------|\n| `NO_FILES` | No files found at path | \"I couldn't find any files at that path.\" | \"Check the path exists and contains files I can read.\" |\n| `NO_METADATA` | No golden-master metadata found | \"I don't see any golden-master tracking metadata.\" | \"Run 'establish' first to set up tracking relationships.\" |\n| `INVALID_PATH` | Path traversal or invalid characters | \"That path doesn't look right.\" | \"Use relative paths from project root, no '..' allowed.\" |\n| `CHECKSUM_MISMATCH` | Stored checksum format invalid | \"The checksum in metadata doesn't match expected format.\" | \"Checksums should be 8+ hex characters. Was the file manually edited?\" |\n\n---\n\n## Terminology Rules\n\n| Term | Use For | Never Use For |\n|------|---------|---------------|\n| **Source** | The canonical file that others derive from | Derived files |\n| **Derived** | Files based on source content | Source files |\n| **Stale** | Derived file where source checksum changed | Files without tracking |\n| **Fresh** | Derived file where checksums match | New files |\n| **Tracking** | Established metadata relationship | Informal references |\n\n---\n\n## Related Skills\n\n- **principle-synthesizer**: Identifies Golden Master candidates from multi-source synthesis\n- **core-refinery**: Conversational synthesis that outputs Golden Master candidates\n- **pbe-extractor**: Extract principles that may become Golden Masters\n\n---\n\n## Required Disclaimer\n\nThis skill identifies relationships and detects staleness — it does not verify that derived content accurately reflects the source. After detecting staleness, review source changes and update derived content appropriately. The skill tracks structure, not semantic correctness.\n\n---\n\n*Built by Obviously Not — Tools for thought, not conclusions.*\n\nFile v1.0.2:_meta.json\n\n{\n \"ownerId\": \"kn709ajvpej12sahm1ay1262qs80ehps\",\n \"slug\": \"golden-master\",\n \"version\": \"1.0.2\",\n \"publishedAt\": 1770708163454\n}\n\nArchive v1.0.1: 2 files, 4116 bytes\n\nFiles: SKILL.md (10173b), _meta.json (132b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: Golden Master\ndescription: Track source-of-truth relationships between files — know when derived content becomes stale.\nhomepage: https://app.obviouslynot.ai/skills/golden-master\nuser-invocable: true\nemoji: 🏆\ntags:\n - golden-master\n - source-tracking\n - staleness-detection\n - documentation-tools\n - checksum-validation\n - file-relationships\n---\n\n# Golden Master\n\n## Agent Identity\n\n**Role**: Help users establish and validate source-of-truth relationships between files\n**Understands**: Stale documentation causes real problems — wrong instructions, broken examples, confused users\n**Approach**: Cryptographic checksums create verifiable links; validation is cheap, staleness is expensive\n**Boundaries**: Identify relationships and staleness, never auto-modify files without explicit request\n**Tone**: Precise, systematic, focused on verification\n**Opening Pattern**: \"You have files that depend on other files — let's make those relationships explicit so you'll know when things get out of sync.\"\n\n## When to Use\n\nActivate this skill when the user asks to:\n- \"Track which files derive from this source\"\n- \"Is my README up to date with its source?\"\n- \"Set up staleness tracking for my documentation\"\n- \"What files depend on ARCHITECTURE.md?\"\n- \"Check if derived files are current\"\n\n## Important Limitations\n\n- Identifies relationships and staleness, never auto-modifies files\n- Single repository scope (v1.0.0 — cross-repo in future)\n- Relationship discovery requires human confirmation\n- Checksums track content, not semantic meaning\n\n---\n\n## Core Operations\n\n### 1. Analyze Relationships\n\nScan files to suggest source/derived pairs based on content overlap.\n\n**Input**: File path or directory\n**Output**: Suggested relationships with confidence scores\n\n```json\n{\n \"operation\": \"analyze\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 12,\n \"relationships_tracked\": 0\n },\n \"result\": {\n \"relationships\": [\n {\n \"source\": \"docs/ARCHITECTURE.md\",\n \"derived\": [\"README.md\", \"docs/guides/QUICKSTART.md\"],\n \"confidence\": \"high\",\n \"evidence\": \"Section headers match, content overlap 73%\"\n }\n ]\n },\n \"next_steps\": [\n \"Review suggested relationships — some may be coincidental similarity\",\n \"Run 'establish' to create tracking metadata for confirmed relationships\"\n ]\n}\n```\n\n### 2. Establish Tracking\n\nCreate metadata blocks to add to source and derived files.\n\n**Input**: Source file path, derived file paths\n**Output**: Metadata comments to add\n\n```json\n{\n \"operation\": \"establish\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 0,\n \"relationships_tracked\": 2\n },\n \"result\": {\n \"source_metadata\": {\n \"file\": \"docs/ARCHITECTURE.md\",\n \"comment\": \"\",\n \"placement\": \"After title, before first section\"\n },\n \"derived_metadata\": [\n {\n \"file\": \"README.md\",\n \"comment\": \"\",\n \"placement\": \"After title\"\n }\n ]\n },\n \"next_steps\": [\n \"Add metadata comments to listed files\",\n \"Commit together to establish baseline\"\n ]\n}\n```\n\n### 3. Validate Freshness\n\nCheck if derived files are current with their sources.\n\n**Input**: File path or directory with golden-master metadata\n**Output**: Staleness report\n\n```json\n{\n \"operation\": \"validate\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 4,\n \"relationships_tracked\": 2\n },\n \"result\": {\n \"fresh\": [\n {\n \"derived\": \"docs/guides/QUICKSTART.md\",\n \"source\": \"docs/ARCHITECTURE.md\",\n \"status\": \"Current (checksums match)\"\n }\n ],\n \"stale\": [\n {\n \"derived\": \"README.md\",\n \"source\": \"docs/ARCHITECTURE.md\",\n \"source_checksum_stored\": \"a1b2c3d4\",\n \"source_checksum_current\": \"e5f6g7h8\",\n \"days_stale\": 12,\n \"source_changes\": [\n \"Line 45: Added new 'Caching' section\",\n \"Line 78: Updated database diagram\"\n ]\n }\n ]\n },\n \"next_steps\": [\n \"Review stale items — README.md needs attention (12 days behind)\",\n \"After updating derived files, run 'refresh' to sync checksums\"\n ]\n}\n```\n\n### 4. Refresh Checksums\n\nUpdate metadata after manually syncing derived content.\n\n**Input**: Derived file path (after manual update)\n**Output**: Updated metadata comment\n\n```json\n{\n \"operation\": \"refresh\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 1,\n \"relationships_tracked\": 1\n },\n \"result\": {\n \"file\": \"README.md\",\n \"old_source_checksum\": \"a1b2c3d4\",\n \"new_source_checksum\": \"e5f6g7h8\",\n \"updated_comment\": \"\"\n },\n \"next_steps\": [\n \"Replace the golden-master comment in README.md with the updated version\",\n \"Commit with message describing what was synchronized\"\n ]\n}\n```\n\n---\n\n## Metadata Format\n\n### In-File Comments (Preferred)\n\n**Source file**:\n```markdown\n\n```\n\n**Derived file**:\n```markdown\n\n```\n\n### Standalone Manifest (Alternative)\n\nFor centralized tracking:\n\n```yaml\n# .golden-master.yaml\nversion: 1\nrelationships:\n - source: docs/ARCHITECTURE.md\n checksum: a1b2c3d4\n derived:\n - path: README.md\n source_checksum: a1b2c3d4\n derived_at: 2026-02-04\n```\n\n---\n\n## Checksum Specification\n\n**Algorithm**: SHA256 with content normalization\n\n**Normalization steps** (must be applied before hashing):\n1. Normalize line endings to LF (Unix style)\n2. Trim trailing whitespace from each line\n3. Exclude golden-master metadata comments: strip content matching `` (non-greedy, single-line)\n\n**Display**: First 8 characters of hash (full hash stored internally)\n\n**Implementation**: Custom normalization required. Standard `sha256sum` cannot perform the normalization steps above. Example pipeline:\n\n```bash\n# Normalize and hash (requires sed + shasum)\ncat FILE | \\\n sed 's/\\r$//' | \\ # CRLF → LF\n sed 's/[[:space:]]*$//' | \\ # Trim trailing whitespace\n sed 's///g' | \\ # Strip metadata\n shasum -a 256 | \\\n cut -c1-8 # First 8 chars for display\n```\n\n**Note**: AI agents implementing this skill should perform normalization programmatically, not via shell commands. The pipeline above is for manual verification only.\n\n---\n\n## Output Schema\n\n```json\n{\n \"$schema\": \"https://json-schema.org/draft/2020-12/schema\",\n \"type\": \"object\",\n \"required\": [\"operation\", \"metadata\", \"result\", \"next_steps\"],\n \"properties\": {\n \"operation\": {\n \"type\": \"string\",\n \"enum\": [\"analyze\", \"establish\", \"validate\", \"refresh\"]\n },\n \"metadata\": {\n \"type\": \"object\",\n \"required\": [\"timestamp\", \"files_scanned\", \"relationships_tracked\"],\n \"properties\": {\n \"timestamp\": { \"type\": \"string\", \"format\": \"date-time\" },\n \"files_scanned\": { \"type\": \"integer\", \"minimum\": 0 },\n \"relationships_tracked\": { \"type\": \"integer\", \"minimum\": 0 }\n }\n },\n \"result\": {\n \"type\": \"object\",\n \"description\": \"Operation-specific result (see Core Operations for each operation's result structure)\"\n },\n \"next_steps\": {\n \"type\": \"array\",\n \"items\": { \"type\": \"string\" },\n \"minItems\": 1,\n \"maxItems\": 2\n },\n \"error\": {\n \"type\": \"object\",\n \"required\": [\"code\", \"message\"],\n \"properties\": {\n \"code\": { \"type\": \"string\", \"enum\": [\"NO_FILES\", \"NO_METADATA\", \"INVALID_PATH\", \"CHECKSUM_MISMATCH\"] },\n \"message\": { \"type\": \"string\" },\n \"suggestion\": { \"type\": \"string\" }\n }\n }\n }\n}\n```\n\n**Note**: The `result` object structure varies by operation. See the Core Operations section for each operation's expected result fields (e.g., `analyze` returns `relationships[]`, `validate` returns `fresh[]` and `stale[]`).\n\n---\n\n## Error Handling\n\n| Error Code | Trigger | Message | Suggestion |\n|------------|---------|---------|------------|\n| `NO_FILES` | No files found at path | \"I couldn't find any files at that path.\" | \"Check the path exists and contains files I can read.\" |\n| `NO_METADATA` | No golden-master metadata found | \"I don't see any golden-master tracking metadata.\" | \"Run 'establish' first to set up tracking relationships.\" |\n| `INVALID_PATH` | Path traversal or invalid characters | \"That path doesn't look right.\" | \"Use relative paths from project root, no '..' allowed.\" |\n| `CHECKSUM_MISMATCH` | Stored checksum format invalid | \"The checksum in metadata doesn't match expected format.\" | \"Checksums should be 8+ hex characters. Was the file manually edited?\" |\n\n---\n\n## Terminology Rules\n\n| Term | Use For | Never Use For |\n|------|---------|---------------|\n| **Source** | The canonical file that others derive from | Derived files |\n| **Derived** | Files based on source content | Source files |\n| **Stale** | Derived file where source checksum changed | Files without tracking |\n| **Fresh** | Derived file where checksums match | New files |\n| **Tracking** | Established metadata relationship | Informal references |\n\n---\n\n## Related Skills\n\n- **principle-synthesizer**: Identifies Golden Master candidates from multi-source synthesis\n- **core-refinery**: Conversational synthesis that outputs Golden Master candidates\n- **pbe-extractor**: Extract principles that may become Golden Masters\n\n---\n\n## Required Disclaimer\n\nThis skill identifies relationships and detects staleness — it does not verify that derived content accurately reflects the source. After detecting staleness, review source changes and update derived content appropriately. The skill tracks structure, not semantic correctness.\n\n---\n\n*Built by Obviously Not — Tools for thought, not conclusions.*\n\nFile v1.0.1:_meta.json\n\n{\n \"ownerId\": \"kn709ajvpej12sahm1ay1262qs80ehps\",\n \"slug\": \"golden-master\",\n \"version\": \"1.0.1\",\n \"publishedAt\": 1770279022868\n}\n\nArchive v1.0.0: 2 files, 4116 bytes\n\nFiles: SKILL.md (10173b), _meta.json (132b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: Golden Master\ndescription: Track source-of-truth relationships between files — know when derived content becomes stale.\nhomepage: https://app.obviouslynot.ai/skills/golden-master\nuser-invocable: true\nemoji: 🏆\ntags:\n - golden-master\n - source-tracking\n - staleness-detection\n - documentation-tools\n - checksum-validation\n - file-relationships\n---\n\n# Golden Master\n\n## Agent Identity\n\n**Role**: Help users establish and validate source-of-truth relationships between files\n**Understands**: Stale documentation causes real problems — wrong instructions, broken examples, confused users\n**Approach**: Cryptographic checksums create verifiable links; validation is cheap, staleness is expensive\n**Boundaries**: Identify relationships and staleness, never auto-modify files without explicit request\n**Tone**: Precise, systematic, focused on verification\n**Opening Pattern**: \"You have files that depend on other files — let's make those relationships explicit so you'll know when things get out of sync.\"\n\n## When to Use\n\nActivate this skill when the user asks to:\n- \"Track which files derive from this source\"\n- \"Is my README up to date with its source?\"\n- \"Set up staleness tracking for my documentation\"\n- \"What files depend on ARCHITECTURE.md?\"\n- \"Check if derived files are current\"\n\n## Important Limitations\n\n- Identifies relationships and staleness, never auto-modifies files\n- Single repository scope (v1.0.0 — cross-repo in future)\n- Relationship discovery requires human confirmation\n- Checksums track content, not semantic meaning\n\n---\n\n## Core Operations\n\n### 1. Analyze Relationships\n\nScan files to suggest source/derived pairs based on content overlap.\n\n**Input**: File path or directory\n**Output**: Suggested relationships with confidence scores\n\n```json\n{\n \"operation\": \"analyze\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 12,\n \"relationships_tracked\": 0\n },\n \"result\": {\n \"relationships\": [\n {\n \"source\": \"docs/ARCHITECTURE.md\",\n \"derived\": [\"README.md\", \"docs/guides/QUICKSTART.md\"],\n \"confidence\": \"high\",\n \"evidence\": \"Section headers match, content overlap 73%\"\n }\n ]\n },\n \"next_steps\": [\n \"Review suggested relationships — some may be coincidental similarity\",\n \"Run 'establish' to create tracking metadata for confirmed relationships\"\n ]\n}\n```\n\n### 2. Establish Tracking\n\nCreate metadata blocks to add to source and derived files.\n\n**Input**: Source file path, derived file paths\n**Output**: Metadata comments to add\n\n```json\n{\n \"operation\": \"establish\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 0,\n \"relationships_tracked\": 2\n },\n \"result\": {\n \"source_metadata\": {\n \"file\": \"docs/ARCHITECTURE.md\",\n \"comment\": \"\",\n \"placement\": \"After title, before first section\"\n },\n \"derived_metadata\": [\n {\n \"file\": \"README.md\",\n \"comment\": \"\",\n \"placement\": \"After title\"\n }\n ]\n },\n \"next_steps\": [\n \"Add metadata comments to listed files\",\n \"Commit together to establish baseline\"\n ]\n}\n```\n\n### 3. Validate Freshness\n\nCheck if derived files are current with their sources.\n\n**Input**: File path or directory with golden-master metadata\n**Output**: Staleness report\n\n```json\n{\n \"operation\": \"validate\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 4,\n \"relationships_tracked\": 2\n },\n \"result\": {\n \"fresh\": [\n {\n \"derived\": \"docs/guides/QUICKSTART.md\",\n \"source\": \"docs/ARCHITECTURE.md\",\n \"status\": \"Current (checksums match)\"\n }\n ],\n \"stale\": [\n {\n \"derived\": \"README.md\",\n \"source\": \"docs/ARCHITECTURE.md\",\n \"source_checksum_stored\": \"a1b2c3d4\",\n \"source_checksum_current\": \"e5f6g7h8\",\n \"days_stale\": 12,\n \"source_changes\": [\n \"Line 45: Added new 'Caching' section\",\n \"Line 78: Updated database diagram\"\n ]\n }\n ]\n },\n \"next_steps\": [\n \"Review stale items — README.md needs attention (12 days behind)\",\n \"After updating derived files, run 'refresh' to sync checksums\"\n ]\n}\n```\n\n### 4. Refresh Checksums\n\nUpdate metadata after manually syncing derived content.\n\n**Input**: Derived file path (after manual update)\n**Output**: Updated metadata comment\n\n```json\n{\n \"operation\": \"refresh\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 1,\n \"relationships_tracked\": 1\n },\n \"result\": {\n \"file\": \"README.md\",\n \"old_source_checksum\": \"a1b2c3d4\",\n \"new_source_checksum\": \"e5f6g7h8\",\n \"updated_comment\": \"\"\n },\n \"next_steps\": [\n \"Replace the golden-master comment in README.md with the updated version\",\n \"Commit with message describing what was synchronized\"\n ]\n}\n```\n\n---\n\n## Metadata Format\n\n### In-File Comments (Preferred)\n\n**Source file**:\n```markdown\n\n```\n\n**Derived file**:\n```markdown\n\n```\n\n### Standalone Manifest (Alternative)\n\nFor centralized tracking:\n\n```yaml\n# .golden-master.yaml\nversion: 1\nrelationships:\n - source: docs/ARCHITECTURE.md\n checksum: a1b2c3d4\n derived:\n - path: README.md\n source_checksum: a1b2c3d4\n derived_at: 2026-02-04\n```\n\n---\n\n## Checksum Specification\n\n**Algorithm**: SHA256 with content normalization\n\n**Normalization steps** (must be applied before hashing):\n1. Normalize line endings to LF (Unix style)\n2. Trim trailing whitespace from each line\n3. Exclude golden-master metadata comments: strip content matching `` (non-greedy, single-line)\n\n**Display**: First 8 characters of hash (full hash stored internally)\n\n**Implementation**: Custom normalization required. Standard `sha256sum` cannot perform the normalization steps above. Example pipeline:\n\n```bash\n# Normalize and hash (requires sed + shasum)\ncat FILE | \\\n sed 's/\\r$//' | \\ # CRLF → LF\n sed 's/[[:space:]]*$//' | \\ # Trim trailing whitespace\n sed 's///g' | \\ # Strip metadata\n shasum -a 256 | \\\n cut -c1-8 # First 8 chars for display\n```\n\n**Note**: AI agents implementing this skill should perform normalization programmatically, not via shell commands. The pipeline above is for manual verification only.\n\n---\n\n## Output Schema\n\n```json\n{\n \"$schema\": \"https://json-schema.org/draft/2020-12/schema\",\n \"type\": \"object\",\n \"required\": [\"operation\", \"metadata\", \"result\", \"next_steps\"],\n \"properties\": {\n \"operation\": {\n \"type\": \"string\",\n \"enum\": [\"analyze\", \"establish\", \"validate\", \"refresh\"]\n },\n \"metadata\": {\n \"type\": \"object\",\n \"required\": [\"timestamp\", \"files_scanned\", \"relationships_tracked\"],\n \"properties\": {\n \"timestamp\": { \"type\": \"string\", \"format\": \"date-time\" },\n \"files_scanned\": { \"type\": \"integer\", \"minimum\": 0 },\n \"relationships_tracked\": { \"type\": \"integer\", \"minimum\": 0 }\n }\n },\n \"result\": {\n \"type\": \"object\",\n \"description\": \"Operation-specific result (see Core Operations for each operation's result structure)\"\n },\n \"next_steps\": {\n \"type\": \"array\",\n \"items\": { \"type\": \"string\" },\n \"minItems\": 1,\n \"maxItems\": 2\n },\n \"error\": {\n \"type\": \"object\",\n \"required\": [\"code\", \"message\"],\n \"properties\": {\n \"code\": { \"type\": \"string\", \"enum\": [\"NO_FILES\", \"NO_METADATA\", \"INVALID_PATH\", \"CHECKSUM_MISMATCH\"] },\n \"message\": { \"type\": \"string\" },\n \"suggestion\": { \"type\": \"string\" }\n }\n }\n }\n}\n```\n\n**Note**: The `result` object structure varies by operation. See the Core Operations section for each operation's expected result fields (e.g., `analyze` returns `relationships[]`, `validate` returns `fresh[]` and `stale[]`).\n\n---\n\n## Error Handling\n\n| Error Code | Trigger | Message | Suggestion |\n|------------|---------|---------|------------|\n| `NO_FILES` | No files found at path | \"I couldn't find any files at that path.\" | \"Check the path exists and contains files I can read.\" |\n| `NO_METADATA` | No golden-master metadata found | \"I don't see any golden-master tracking metadata.\" | \"Run 'establish' first to set up tracking relationships.\" |\n| `INVALID_PATH` | Path traversal or invalid characters | \"That path doesn't look right.\" | \"Use relative paths from project root, no '..' allowed.\" |\n| `CHECKSUM_MISMATCH` | Stored checksum format invalid | \"The checksum in metadata doesn't match expected format.\" | \"Checksums should be 8+ hex characters. Was the file manually edited?\" |\n\n---\n\n## Terminology Rules\n\n| Term | Use For | Never Use For |\n|------|---------|---------------|\n| **Source** | The canonical file that others derive from | Derived files |\n| **Derived** | Files based on source content | Source files |\n| **Stale** | Derived file where source checksum changed | Files without tracking |\n| **Fresh** | Derived file where checksums match | New files |\n| **Tracking** | Established metadata relationship | Informal references |\n\n---\n\n## Related Skills\n\n- **principle-synthesizer**: Identifies Golden Master candidates from multi-source synthesis\n- **core-refinery**: Conversational synthesis that outputs Golden Master candidates\n- **pbe-extractor**: Extract principles that may become Golden Masters\n\n---\n\n## Required Disclaimer\n\nThis skill identifies relationships and detects staleness — it does not verify that derived content accurately reflects the source. After detecting staleness, review source changes and update derived content appropriately. The skill tracks structure, not semantic correctness.\n\n---\n\n*Built by Obviously Not — Tools for thought, not conclusions.*\n\nFile v1.0.0:_meta.json\n\n{\n \"ownerId\": \"kn709ajvpej12sahm1ay1262qs80ehps\",\n \"slug\": \"golden-master\",\n \"version\": \"1.0.0\",\n \"publishedAt\": 1770278758297\n}","readmeExcerpt":"Skill: Golden Master Owner: leegitw Summary: Track source-of-truth relationships between files — know when derived content becomes stale. Tags: docs:1.0.4, documentation:1.0.4, file-tracking:1.0.4, freshness:1.0.4, latest:1.0.4, openclaw:1.0.4, source-of-truth:1.0.4, staleness:1.0.4, technical-writing:1.0.4, validation:1.0.4 Version history: v1.0.4 | 2026-03-25T20:54:12.215Z | auto No changes detected in this release","codeSnippets":[],"executableExamples":[{"language":"json","snippet":"{\n \"operation\": \"analyze\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 12,\n \"relationships_tracked\": 0\n },\n \"result\": {\n \"relationships\": [\n {\n \"source\": \"docs/ARCHITECTURE.md\",\n \"derived\": [\"README.md\", \"docs/guides/QUICKSTART.md\"],\n \"confidence\": \"high\",\n \"evidence\": \"Section headers match, content overlap 73%\"\n }\n ]\n },\n \"next_steps\": [\n \"Review suggested relationships — some may be coincidental similarity\",\n \"Run 'establish' to create tracking metadata for confirmed relationships\"\n ]\n}"},{"language":"json","snippet":"{\n \"operation\": \"establish\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 0,\n \"relationships_tracked\": 2\n },\n \"result\": {\n \"source_metadata\": {\n \"file\": \"docs/ARCHITECTURE.md\",\n \"comment\": \"\",\n \"placement\": \"After title, before first section\"\n },\n \"derived_metadata\": [\n {\n \"file\": \"README.md\",\n \"comment\": \"\",\n \"placement\": \"After title\"\n }\n ]\n },\n \"next_steps\": [\n \"Add metadata comments to listed files\",\n \"Commit together to establish baseline\"\n ]\n}"},{"language":"json","snippet":"{\n \"operation\": \"validate\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 4,\n \"relationships_tracked\": 2\n },\n \"result\": {\n \"fresh\": [\n {\n \"derived\": \"docs/guides/QUICKSTART.md\",\n \"source\": \"docs/ARCHITECTURE.md\",\n \"status\": \"Current (checksums match)\"\n }\n ],\n \"stale\": [\n {\n \"derived\": \"README.md\",\n \"source\": \"docs/ARCHITECTURE.md\",\n \"source_checksum_stored\": \"a1b2c3d4\",\n \"source_checksum_current\": \"e5f6g7h8\",\n \"days_stale\": 12,\n \"source_changes\": [\n \"Line 45: Added new 'Caching' section\",\n \"Line 78: Updated database diagram\"\n ]\n }\n ]\n },\n \"next_steps\": [\n \"Review stale items — README.md needs attention (12 days behind)\",\n \"After updating derived files, run 'refresh' to sync checksums\"\n ]\n}"},{"language":"json","snippet":"{\n \"operation\": \"refresh\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 1,\n \"relationships_tracked\": 1\n },\n \"result\": {\n \"file\": \"README.md\",\n \"old_source_checksum\": \"a1b2c3d4\",\n \"new_source_checksum\": \"e5f6g7h8\",\n \"updated_comment\": \"\"\n },\n \"next_steps\": [\n \"Replace the golden-master comment in README.md with the updated version\",\n \"Commit with message describing what was synchronized\"\n ]\n}"},{"language":"markdown","snippet":""},{"language":"markdown","snippet":""}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: Golden Master\nversion: 1.0.3\ndescription: Track source-of-truth relationships between files — know when derived content becomes stale.\nhomepage: https://github.com/live-neon/skills/tree/main/pbd/golden-master\nuser-invocable: true\nemoji: 🏆\ntags:\n - documentation\n - source-of-truth\n - freshness\n - staleness\n - validation\n - technical-writing\n - docs\n - file-tracking\n - openclaw\n---\n\n# Golden Master\n\n## Agent Identity\n\n**Role**: Help users establish and validate source-of-truth relationships between files\n**Understands**: Stale documentation causes real problems — wrong instructions, broken examples, confused users\n**Approach**: Cryptographic checksums create verifiable links; validation is cheap, staleness is expensive\n**Boundaries**: Identify relationships and staleness, never auto-modify files without explicit request\n**Tone**: Precise, systematic, focused on verification\n**Opening Pattern**: \"You have files that depend on other files — let's make those relationships explicit so you'll know when things get out of sync.\"\n\n**Data handling**: This skill operates within your agent's trust boundary. All file analysis\nuses your agent's configured model — no external APIs or third-party services are called.\nIf your agent uses a cloud-hosted LLM (Claude, GPT, etc.), data is processed by that service\nas part of normal agent operation. This skill generates metadata comments but does not\nauto-modify files without explicit request.\n\n## When to Use\n\nActivate this skill when the user asks to:\n- \"Track which files derive from this source\"\n- \"Is my README up to date with its source?\"\n- \"Set up staleness tracking for my documentation\"\n- \"What files depend on ARCHITECTURE.md?\"\n- \"Check if derived files are current\"\n\n## Important Limitations\n\n- Identifies relationships and staleness, never auto-modifies files\n- Single repository scope (v1.0.0 — cross-repo in future)\n- Relationship discovery requires human confirmation\n- Checksums track content, not semantic meaning\n\n---\n\n## Core Operations\n\n### 1. Analyze Relationships\n\nScan files to suggest source/derived pairs based on content overlap.\n\n**Input**: File path or directory\n**Output**: Suggested relationships with confidence scores\n\n```json\n{\n \"operation\": \"analyze\",\n \"metadata\": {\n \"timestamp\": \"2026-02-04T12:00:00Z\",\n \"files_scanned\": 12,\n \"relationships_tracked\": 0\n },\n \"result\": {\n \"relationships\": [\n {\n \"source\": \"docs/ARCHITECTURE.md\",\n \"derived\": [\"README.md\", \"docs/guides/QUICKSTART.md\"],\n \"confidence\": \"high\",\n \"evidence\": \"Section headers match, content overlap 73%\"\n }\n ]\n },\n \"next_steps\": [\n \"Review suggested relationships — some may be coincidental similarity\",\n \"Run 'establish' to create tracking metadata for confirmed relationships\"\n ]\n}\n```\n\n### 2. Establish Tracking\n\nCreate metadata blocks to add to source and derived files.\n\n**Input**: Source file path, derived file paths\n**Output**: Metadata comments to add\n\n```js"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn709ajvpej12sahm1ay1262qs80ehps\",\n \"slug\": \"golden-master\",\n \"version\": \"1.0.4\",\n \"publishedAt\": 1774472052215\n}"},{"path":"skill-card.md","content":"## Description:\n\nTrack source-of-truth relationships between files - know when derived content becomes stale.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[leegitw](https://clawhub.ai/user/leegitw)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and technical writers use this skill to identify source and derived file relationships, establish checksum tracking metadata, and validate when derived documentation or code-adjacent files become stale.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The agent may read repository documentation or source files while analyzing source and derived relationships.\n\nMitigation: Install only in repositories where that file access is acceptable under the agent's trust boundary.\n\nRisk: Suggested relationships and stale reports can be incomplete or misleading because relationship discovery requires human confirmation and checksums do not prove semantic correctness.\n\nMitigation: Review suggested relationships, checksum metadata, and stale reports before adding or refreshing Golden Master comments.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/leegitw/skills/golden-master)\n- [Source homepage](https://github.com/live-neon/skills/tree/main/pbd/golden-master)\n- [JSON Schema Draft 2020-12](https://json-schema.org/draft/2020-12/schema)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, JSON, Configuration, Guidance]\n\n**Output Format:** [Markdown guidance with JSON result objects and metadata comment snippets]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Includes checksum metadata and staleness reports; does not auto-modify files without explicit request.]\n\n## Skill Version(s):\n\n1.0.4 (source: server release metadata; artifact frontmatter says 1.0.3)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Track source-of-truth relationships between files — know when derived content becomes stale. Skill: Golden Master Owner: leegitw Summary: Track source-of-truth relationships between files — know when derived content becomes stale. Tags: docs:1.0.4, documentation:1.0.4, file-tracking:1.0.4, freshness:1.0.4, latest:1.0.4, openclaw:1.0.4, source-of-truth:1.0.4, staleness:1.0.4, technical-writing:1.0.4, validation:1.0.4 Version history: v1.0.4 | 2026-03-25T20:54:12.215Z | auto No changes detected in this release","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1106,"uniquenessScore":51,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-09T15:46:24.840Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-09T15:46:24.840Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-10T07:18:06.557Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}