{"id":"e0192883-8b89-49fd-ac4b-8b60b4409310","entityType":"agent","slug":"clawhub-athola-nm-sanctum-update-readme","name":"update-readme","canonicalUrl":"https://www.xpersona.co/agent/clawhub-athola-nm-sanctum-update-readme","canonicalPath":"/agent/clawhub-athola-nm-sanctum-update-readme","generatedAt":"2026-10-10T10:49:58.913Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-10T07:24:19.464Z","emptyReason":null},"description":"Refreshes README structure and content using repo context and exemplar research Skill: update-readme Owner: athola Summary: Refreshes README structure and content using repo context and exemplar research Tags: latest:1.9.19 Version history: v1.9.19 | 2026-08-26T13:21:22.309Z | user Release v1.9.19 v1.9.17 | 2026-07-30T05:41:22.501Z | user Release v1.9.17 v1.9.16 | 2026-07-14T19:58:10.077Z | user Release v1.9.16 v1.9.14 | 2026-06-30T18:05:59.607Z | user Release v1.9.14 v1.9.13 | 2026-06-27T16:23:","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.6K downloads reported by the source. Last updated 10/10/2026.","installCommand":"clawhub skill install s17emme0e2m3cpf7k2jvp3a84984b8z9:nm-sanctum-update-readme","sourceUrl":"https://clawhub.ai/athola/nm-sanctum-update-readme","homepage":"https://clawhub.ai/athola/skills/nm-sanctum-update-readme","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/athola/nm-sanctum-update-readme","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/athola/skills/nm-sanctum-update-readme","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":64,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Refreshes README structure and content using repo context and exemplar research Skill: update-readme Owner: athola Summary: Refreshes README structure and conte"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-10T07:24:19.464Z","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-10T07:24:19.464Z","emptyReason":null},"stars":null,"forks":null,"downloads":1593,"packageName":null,"latestVersion":"1.9.19","tractionLabel":"1.6K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T07:24:19.464Z","emptyReason":null},"lastUpdatedAt":"2026-10-10T07:24:19.464Z","lastCrawledAt":"2026-10-10T07:24:19.464Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-11T07:24:19.464Z","lastVerifiedAt":null,"highlights":[{"version":"1.9.19","createdAt":"2026-08-26T13:21:22.309Z","changelog":"Release v1.9.19","fileCount":5,"zipByteSize":7403},{"version":"1.9.17","createdAt":"2026-07-30T05:41:22.501Z","changelog":"Release v1.9.17","fileCount":5,"zipByteSize":7319},{"version":"1.9.16","createdAt":"2026-07-14T19:58:10.077Z","changelog":"Release v1.9.16","fileCount":5,"zipByteSize":7446},{"version":"1.9.14","createdAt":"2026-06-30T18:05:59.607Z","changelog":"Release v1.9.14","fileCount":5,"zipByteSize":7473},{"version":"1.9.13","createdAt":"2026-06-27T16:23:45.526Z","changelog":"Release v1.9.13","fileCount":5,"zipByteSize":7580},{"version":"1.9.12","createdAt":"2026-06-19T03:19:19.566Z","changelog":"Release v1.9.12","fileCount":5,"zipByteSize":7515},{"version":"1.0.3","createdAt":"2026-06-18T15:21:55.164Z","changelog":"Release v1.9.12","fileCount":5,"zipByteSize":7412},{"version":"1.0.2","createdAt":"2026-05-09T02:20:12.005Z","changelog":"Release v1.9.5","fileCount":5,"zipByteSize":7448}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17emme0e2m3cpf7k2jvp3a84984b8z9:nm-sanctum-update-readme","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","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-athola-nm-sanctum-update-readme/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-update-readme/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-update-readme/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-update-readme/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-update-readme/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-update-readme/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-10T10:49:58.910Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-update-readme/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-update-readme/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-update-readme/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-athola-nm-sanctum-update-readme/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-10T07:24:19.464Z","emptyReason":null},"readme":"Skill: update-readme\n\nOwner: athola\n\nSummary: Refreshes README structure and content using repo context and exemplar research\n\nTags: latest:1.9.19\n\nVersion history:\n\nv1.9.19 | 2026-08-26T13:21:22.309Z | user\n\nRelease v1.9.19\n\nv1.9.17 | 2026-07-30T05:41:22.501Z | user\n\nRelease v1.9.17\n\nv1.9.16 | 2026-07-14T19:58:10.077Z | user\n\nRelease v1.9.16\n\nv1.9.14 | 2026-06-30T18:05:59.607Z | user\n\nRelease v1.9.14\n\nv1.9.13 | 2026-06-27T16:23:45.526Z | user\n\nRelease v1.9.13\n\nv1.9.12 | 2026-06-19T03:19:19.566Z | user\n\nRelease v1.9.12\n\nv1.0.3 | 2026-06-18T15:21:55.164Z | user\n\nRelease v1.9.12\n\nv1.0.2 | 2026-05-09T02:20:12.005Z | user\n\nRelease v1.9.5\n\nv1.0.1 | 2026-05-06T14:21:37.994Z | user\n\nRelease v1.9.4\n\nv1.0.0 | 2026-04-20T12:01:46.848Z | auto\n\n- Initial release of the update-readme skill: streamlines structural and content refreshes for repository READMEs.\n- Establishes a multi-step workflow including language audit, exemplar research, outline alignment, edits, AI slop detection, and verification/reporting.\n- Integrates with related skills such as git-workspace-review for repo context, scribe for slop detection and document generation, and leyline for markdown formatting.\n- Emphasizes research-backed recommendations, specific command usage, and explicit references to both internal documents and external exemplars.\n- Includes troubleshooting tips for common README and documentation issues.\n\nArchive index:\n\nArchive v1.9.19: 5 files, 7403 bytes\n\nFiles: modules/exemplar-research.md (4022b), modules/language-audit.md (2375b), skill-card.md (2065b), SKILL.md (5813b), _meta.json (144b)\n\nFile v1.9.19:SKILL.md\n\n---\nname: update-readme\ndescription: Refreshes README structure and content using repo context and exemplar research\nversion: 1.9.8\ntriggers:\n  - readme\n  - documentation\n  - exemplars\n  - research\n  - structure\n  - README needs a structural update after significant project changes\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.sanctum:git-workspace-review\", \"night-market.imbue:proof-of-work\", \"night-market.scribe:slop-detector\", \"night-market.scribe:doc-generator\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# README Update Workflow\n\n## When To Use\nUse this skill whenever the README requires a structural refresh.\nRun `Skill(sanctum:git-workspace-review)` first to capture repo context and diffs.\n\n## When NOT To Use\n\n- Updating inline docs: use doc-updates\n- Consolidating ephemeral reports: use doc-consolidation\n\n## Required TodoWrite Items\n1. `update-readme:language-audit`\n2. `update-readme:exemplar-research`\n3. `update-readme:outline-aligned`\n4. `update-readme:edits-applied`\n5. `update-readme:slop-scanned` - AI marker detection via scribe\n6. `update-readme:verification-reporting`\n\n## Step 1 - Language Audit (`update-readme:language-audit`)\n- Confirm `pwd`, `git status -sb`, and the baseline branch for reference.\n- Detect dominant languages using repository heuristics (manifest files, file counts).\n- Note secondary languages that influence documentation (e.g., a TypeScript frontend and a Rust backend) so the README can surface both.\n- Record the method and findings.\n\nSee `modules/language-audit.md` for detailed detection patterns and commands.\n\n## Step 2 - Exemplar Research (`update-readme:exemplar-research`)\n- For each primary and secondary language, use web search to locate high-quality READMEs (star count, recency, maintainer activity).\n- Capture 2-3 exemplar repositories per language and summarize why each is relevant (section order, visuals, quickstart clarity, governance messaging, math exposition, etc.).\n- Store citations for every exemplar so the final summary references them explicitly.\n\nSee `modules/exemplar-research.md` for search query patterns and evaluation criteria.\n\n## Step 3 - Outline Alignment (`update-readme:outline-aligned`)\n- Compare current README headings (`rg -n '^#' README.md`) against patterns observed in exemplars.\n- Draft a target outline covering: value proposition, installation, quickstart, deeper usage/configuration, architecture/feature highlights, performance or math guarantees, documentation links, contribution/governance, roadmap/status, and licensing/security notes.\n- validate internal documents (docs/, specs/, wiki, commands/) are mapped to the relevant sections so the README anchors them with context-sensitive links.\n\n## Step 4 - Apply Edits (`update-readme:edits-applied`)\n- Implement the new structure directly in `README.md`\n  (or the specified file).\n- Follow `Skill(leyline:markdown-formatting)` conventions:\n  wrap prose at 80 chars (prefer sentence/clause boundaries),\n  blank lines around headings, ATX headings only, blank line\n  before lists, reference-style links for long URLs.\n- Maintain concise, evidence-based prose; avoid marketing fluff.\n- Add comparison tables, feature lists, or diagrams only if\n  they originate from current repository assets (no speculative\n  content).\n- When referencing algorithms or performance claims, point to\n  benchmarks or tests within the repository or documented math\n  reviews.\n\n## Step 4.5 - AI Slop Detection (`update-readme:slop-scanned`)\n\nRun `Skill(scribe:slop-detector)` on the updated README to detect AI-generated content markers.\n\n### Scribe Integration\n\nThe scribe plugin provides AI slop detection:\n\n```\nSkill(scribe:slop-detector) --target README.md\n```\n\nThis detects:\n- **Tier 1 words**: delve, tapestry, comprehensive, leveraging, etc.\n- **Phrase patterns**: \"In today's fast-paced world\", \"cannot be overstated\"\n- **Structural markers**: Excessive em dashes, bullet overuse, sentence uniformity\n- **Marketing language**: \"enterprise-ready\", \"cutting-edge\", \"seamless\"\n\n### Remediation\n\nIf slop score exceeds 2.0 (moderate), apply `Skill(scribe:doc-generator)` principles:\n\n1. Ground every claim with specifics\n2. Remove formulaic openers/closers\n3. Use numbers, commands, filenames over adjectives\n4. Balance bullets with narrative prose\n5. Show authorial perspective (trade-offs, reasoning)\n\nFor significant cleanup needs, use:\n\n```\nAgent(scribe:doc-editor) --target README.md\n```\n\n## Step 5 - Verification & Reporting (`update-readme:verification-reporting`)\n- Re-read the updated README for clarity, accessibility (section lengths, bullet balance), and accurate links.\n- Run `git diff README.md` (or the edited file) and capture snippets for the final report.\n- Summarize detected languages, exemplar sources (with citations), key structural decisions, and follow-up TODOs (e.g., add badges, upload diagrams).\n\n## Exit Criteria\n- All `TodoWrite` items are complete.\n- The README reflects a modern, language-aware structure, referencing both internal docs and external inspiration with citations.\n- Research notes and command references are captured so future reviewers can reproduce the process.\n## Troubleshooting\n\n### Common Issues\n\n**Documentation out of sync**\nRun `make docs-update` to regenerate from code\n\n**Build failures**\nCheck that all required dependencies are installed\n\n**Links broken**\nVerify relative paths in documentation files\n\nFile v1.9.19:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-sanctum-update-readme\",\n  \"version\": \"1.9.19\",\n  \"publishedAt\": 1787750482309\n}\n\nFile v1.9.19:modules/exemplar-research.md\n\n# Exemplar Research Patterns\n\nDetailed patterns for finding, evaluating, and documenting high-quality README exemplars.\n\n## Web Search Query Patterns\n\n### Language-Specific Queries\n\n```\n\"GitHub [language] README best practices\"\n\"[language] framework README examples\"\n\"[language] project README badges\"\n\"[language] library documentation structure\"\n\"awesome [language] README\"\n```\n\n### Framework/Domain-Specific Queries\n\n```\n\"[framework] README structure\"\n\"[domain] project README examples\" (e.g., \"CLI tool README examples\")\n\"[language] [project-type] documentation\" (e.g., \"Rust async library documentation\")\n```\n\n### Quality Indicators\n\n```\n\"high star count [language] README\"\n\"well-maintained [language] project README\"\n\"[language] project documentation best practices 2024\"\n```\n\n## Exemplar Evaluation Criteria\n\nAssess each candidate README using these dimensions:\n\n### Structure & Organization\n- **Section order**: Does it follow a logical progression (value → quickstart → details)?\n- **Progressive disclosure**: Are complex topics deferred until after basics?\n- **Table of contents**: Is it present and well-structured?\n- **Visual hierarchy**: Clear heading levels, spacing, readability?\n\n### Content Quality\n- **Value proposition**: Clear statement of what the project does and why it matters?\n- **Quickstart clarity**: Can a new user get started in <5 minutes?\n- **Code examples**: Are they runnable, realistic, well-commented?\n- **Installation steps**: Clear, tested, platform-aware?\n\n### Technical Communication\n- **Accuracy**: Does it match the actual codebase capabilities?\n- **Completeness**: Coverage of installation, usage, configuration, troubleshooting?\n- **Governance messaging**: Clear contribution guidelines, roadmap, support channels?\n- **Math/algorithm exposition**: For technical projects, is the theory well-explained?\n\n### Maintenance Signals\n- **Recency**: Last commit within 6 months?\n- **Star count**: Indicator of community validation (>500 stars preferred)\n- **Maintainer activity**: Active issue responses, recent releases?\n- **CI/CD badges**: Evidence of automated quality checks?\n\n## Citation Format\n\nRecord each exemplar with full attribution:\n\n```markdown\n### Exemplar: [Project Name]\n- **URL**: https://github.com/[org]/[repo]\n- **Language**: [Primary language]\n- **Stars**: [count] (as of [date])\n- **Last Updated**: [date]\n- **Relevant Patterns**:\n  - [Pattern 1]: [Description and why it's relevant]\n  - [Pattern 2]: [Description and why it's relevant]\n  - [Pattern 3]: [Description and why it's relevant]\n- **Specific Elements to Adapt**:\n  - [Element]: [How it applies to this project]\n```\n\n## Storage Recommendations\n\n### Temporary Research Notes\nStore research findings in a temporary file during the session:\n\n```bash\n# Create research notes file\ncat > /tmp/readme-research.md << 'EOF'\n# README Exemplar Research\n\n## [Language 1] Exemplars\n[Citations...]\n\n## [Language 2] Exemplars\n[Citations...]\nEOF\n```\n\n### Final Report Integration\nInclude exemplar citations in the final verification report so future maintainers can:\n- Understand the design decisions\n- Revisit the sources for updates\n- Validate the approach against current best practices\n\n## Example Multi-Language Research\n\nFor a project with Rust backend and TypeScript frontend:\n\n1. **Rust Exemplars** (2-3 projects)\n   - Focus on: CLI tool patterns, installation via cargo, feature flags, performance claims\n\n2. **TypeScript Exemplars** (2-3 projects)\n   - Focus on: npm installation, dev environment setup, API documentation, framework integration\n\n3. **Full-Stack Exemplars** (1-2 projects)\n   - Focus on: How to structure README for multiple runtimes, quickstart for both components, architecture diagrams\n\n## Quality Threshold\n\nMinimum criteria for an exemplar to be useful:\n- Must have >100 stars OR be from a recognized organization\n- README must be >200 lines (substantial content)\n- Must have been updated in the last year\n- Must demonstrate at least 3 structural patterns relevant to the target project\n\nFile v1.9.19:modules/language-audit.md\n\n# Language Audit Patterns\n\nDetailed patterns and commands for detecting project languages and their documentation implications.\n\n## Manifest File Detection\n\nCheck for language-specific manifest files to identify the primary language(s):\n\n```bash\n# Rust\nls -1 Cargo.toml 2>/dev/null\n\n# Node.js/TypeScript\nls -1 package.json 2>/dev/null\n\n# Go\nls -1 go.mod 2>/dev/null\n\n# Python\nls -1 pyproject.toml setup.py requirements.txt 2>/dev/null\n\n# Java/Kotlin\nls -1 pom.xml build.gradle build.gradle.kts 2>/dev/null\n\n# Ruby\nls -1 Gemfile 2>/dev/null\n\n# PHP\nls -1 composer.json 2>/dev/null\n```\n\n## File Count Analysis\n\nCount source files by extension to determine language distribution:\n\n```bash\n# Rust\ngit ls-files | rg '\\.rs$' | wc -l\n# or for preview\nrg --files -g '*.rs' | head -10\n\n# Python\ngit ls-files | rg '\\.py$' | wc -l\nrg --files -g '*.py' | head -10\n\n# Go\ngit ls-files | rg '\\.go$' | wc -l\nrg --files -g '*.go' | head -10\n\n# TypeScript/JavaScript\ngit ls-files | rg '\\.(ts|tsx|js|jsx)$' | wc -l\nrg --files -g '*.ts' -g '*.tsx' | head -10\n\n# Java\ngit ls-files | rg '\\.java$' | wc -l\nrg --files -g '*.java' | head -10\n```\n\n## Language Priority Heuristics\n\nDetermine primary language using these priority rules:\n\n1. **Manifest presence**: If a language-specific manifest exists, it's a strong signal\n2. **File count dominance**: Language with >60% of source files is primary\n3. **Directory structure**: Check for language-specific directories (src/, lib/, pkg/)\n4. **Build configuration**: Presence of Makefile, CMakeLists.txt, or build scripts\n\n## Secondary Language Handling\n\nDocument secondary languages when they:\n\n- Represent >20% of codebase\n- Serve distinct architectural roles (e.g., Rust backend + TypeScript frontend)\n- Have their own build/test infrastructure\n- Require separate installation or runtime considerations\n\n### Example Multi-Language Documentation Strategy\n\n```markdown\n## Installation\n\n### Backend (Rust)\n[Rust-specific instructions]\n\n### Frontend (TypeScript)\n[Node/npm-specific instructions]\n```\n\n## Recording Findings\n\nCapture the audit results in a structured format:\n\n```\nLanguage Audit Results:\n- Primary: [Language] ([count] files, [manifest])\n- Secondary: [Language] ([count] files, [manifest])\n- Method: [manifest detection | file count | directory structure]\n- Documentation implications: [single-language | multi-language sections needed]\n```\n\nFile v1.9.19:skill-card.md\n\n## Description:\n\nRefreshes README structure and content using repo context and exemplar research.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[athola](https://clawhub.ai/user/athola)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and documentation maintainers use this skill to audit a repository, research relevant README examples, and restructure README content with clearer installation, usage, governance, and verification sections.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: README edits could introduce inaccurate or misleading project guidance.\n\nMitigation: Review the documentation diff, verify links and claims against repository files, and scan the final README before release.\n\nRisk: The workflow uses web-based exemplar research and references external plugin dependencies.\n\nMitigation: Review cited exemplar sources and external plugin dependencies separately before relying on their recommendations.\n\nRisk: Some trigger words are broader than the README update workflow itself.\n\nMitigation: Invoke the skill explicitly for README refresh tasks rather than relying only on broad trigger matching.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-sanctum-update-readme)\n- [Metadata homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)\n\n## Skill Output:\n\n**Output Type(s):** [markdown, shell commands, guidance]\n\n**Output Format:** [Markdown documentation edits with command snippets and verification notes]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include citations for researched README exemplars and summaries of repository language findings.]\n\n## Skill Version(s):\n\n1.9.19 (source: server release metadata)\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.9.17: 5 files, 7319 bytes\n\nFiles: modules/exemplar-research.md (4022b), modules/language-audit.md (2375b), skill-card.md (1933b), SKILL.md (5813b), _meta.json (144b)\n\nFile v1.9.17:SKILL.md\n\n---\nname: update-readme\ndescription: Refreshes README structure and content using repo context and exemplar research\nversion: 1.9.8\ntriggers:\n  - readme\n  - documentation\n  - exemplars\n  - research\n  - structure\n  - README needs a structural update after significant project changes\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.sanctum:git-workspace-review\", \"night-market.imbue:proof-of-work\", \"night-market.scribe:slop-detector\", \"night-market.scribe:doc-generator\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# README Update Workflow\n\n## When To Use\nUse this skill whenever the README requires a structural refresh.\nRun `Skill(sanctum:git-workspace-review)` first to capture repo context and diffs.\n\n## When NOT To Use\n\n- Updating inline docs: use doc-updates\n- Consolidating ephemeral reports: use doc-consolidation\n\n## Required TodoWrite Items\n1. `update-readme:language-audit`\n2. `update-readme:exemplar-research`\n3. `update-readme:outline-aligned`\n4. `update-readme:edits-applied`\n5. `update-readme:slop-scanned` - AI marker detection via scribe\n6. `update-readme:verification-reporting`\n\n## Step 1 - Language Audit (`update-readme:language-audit`)\n- Confirm `pwd`, `git status -sb`, and the baseline branch for reference.\n- Detect dominant languages using repository heuristics (manifest files, file counts).\n- Note secondary languages that influence documentation (e.g., a TypeScript frontend and a Rust backend) so the README can surface both.\n- Record the method and findings.\n\nSee `modules/language-audit.md` for detailed detection patterns and commands.\n\n## Step 2 - Exemplar Research (`update-readme:exemplar-research`)\n- For each primary and secondary language, use web search to locate high-quality READMEs (star count, recency, maintainer activity).\n- Capture 2-3 exemplar repositories per language and summarize why each is relevant (section order, visuals, quickstart clarity, governance messaging, math exposition, etc.).\n- Store citations for every exemplar so the final summary references them explicitly.\n\nSee `modules/exemplar-research.md` for search query patterns and evaluation criteria.\n\n## Step 3 - Outline Alignment (`update-readme:outline-aligned`)\n- Compare current README headings (`rg -n '^#' README.md`) against patterns observed in exemplars.\n- Draft a target outline covering: value proposition, installation, quickstart, deeper usage/configuration, architecture/feature highlights, performance or math guarantees, documentation links, contribution/governance, roadmap/status, and licensing/security notes.\n- validate internal documents (docs/, specs/, wiki, commands/) are mapped to the relevant sections so the README anchors them with context-sensitive links.\n\n## Step 4 - Apply Edits (`update-readme:edits-applied`)\n- Implement the new structure directly in `README.md`\n  (or the specified file).\n- Follow `Skill(leyline:markdown-formatting)` conventions:\n  wrap prose at 80 chars (prefer sentence/clause boundaries),\n  blank lines around headings, ATX headings only, blank line\n  before lists, reference-style links for long URLs.\n- Maintain concise, evidence-based prose; avoid marketing fluff.\n- Add comparison tables, feature lists, or diagrams only if\n  they originate from current repository assets (no speculative\n  content).\n- When referencing algorithms or performance claims, point to\n  benchmarks or tests within the repository or documented math\n  reviews.\n\n## Step 4.5 - AI Slop Detection (`update-readme:slop-scanned`)\n\nRun `Skill(scribe:slop-detector)` on the updated README to detect AI-generated content markers.\n\n### Scribe Integration\n\nThe scribe plugin provides AI slop detection:\n\n```\nSkill(scribe:slop-detector) --target README.md\n```\n\nThis detects:\n- **Tier 1 words**: delve, tapestry, comprehensive, leveraging, etc.\n- **Phrase patterns**: \"In today's fast-paced world\", \"cannot be overstated\"\n- **Structural markers**: Excessive em dashes, bullet overuse, sentence uniformity\n- **Marketing language**: \"enterprise-ready\", \"cutting-edge\", \"seamless\"\n\n### Remediation\n\nIf slop score exceeds 2.0 (moderate), apply `Skill(scribe:doc-generator)` principles:\n\n1. Ground every claim with specifics\n2. Remove formulaic openers/closers\n3. Use numbers, commands, filenames over adjectives\n4. Balance bullets with narrative prose\n5. Show authorial perspective (trade-offs, reasoning)\n\nFor significant cleanup needs, use:\n\n```\nAgent(scribe:doc-editor) --target README.md\n```\n\n## Step 5 - Verification & Reporting (`update-readme:verification-reporting`)\n- Re-read the updated README for clarity, accessibility (section lengths, bullet balance), and accurate links.\n- Run `git diff README.md` (or the edited file) and capture snippets for the final report.\n- Summarize detected languages, exemplar sources (with citations), key structural decisions, and follow-up TODOs (e.g., add badges, upload diagrams).\n\n## Exit Criteria\n- All `TodoWrite` items are complete.\n- The README reflects a modern, language-aware structure, referencing both internal docs and external inspiration with citations.\n- Research notes and command references are captured so future reviewers can reproduce the process.\n## Troubleshooting\n\n### Common Issues\n\n**Documentation out of sync**\nRun `make docs-update` to regenerate from code\n\n**Build failures**\nCheck that all required dependencies are installed\n\n**Links broken**\nVerify relative paths in documentation files\n\nFile v1.9.17:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-sanctum-update-readme\",\n  \"version\": \"1.9.17\",\n  \"publishedAt\": 1785390082501\n}\n\nFile v1.9.17:modules/exemplar-research.md\n\n# Exemplar Research Patterns\n\nDetailed patterns for finding, evaluating, and documenting high-quality README exemplars.\n\n## Web Search Query Patterns\n\n### Language-Specific Queries\n\n```\n\"GitHub [language] README best practices\"\n\"[language] framework README examples\"\n\"[language] project README badges\"\n\"[language] library documentation structure\"\n\"awesome [language] README\"\n```\n\n### Framework/Domain-Specific Queries\n\n```\n\"[framework] README structure\"\n\"[domain] project README examples\" (e.g., \"CLI tool README examples\")\n\"[language] [project-type] documentation\" (e.g., \"Rust async library documentation\")\n```\n\n### Quality Indicators\n\n```\n\"high star count [language] README\"\n\"well-maintained [language] project README\"\n\"[language] project documentation best practices 2024\"\n```\n\n## Exemplar Evaluation Criteria\n\nAssess each candidate README using these dimensions:\n\n### Structure & Organization\n- **Section order**: Does it follow a logical progression (value → quickstart → details)?\n- **Progressive disclosure**: Are complex topics deferred until after basics?\n- **Table of contents**: Is it present and well-structured?\n- **Visual hierarchy**: Clear heading levels, spacing, readability?\n\n### Content Quality\n- **Value proposition**: Clear statement of what the project does and why it matters?\n- **Quickstart clarity**: Can a new user get started in <5 minutes?\n- **Code examples**: Are they runnable, realistic, well-commented?\n- **Installation steps**: Clear, tested, platform-aware?\n\n### Technical Communication\n- **Accuracy**: Does it match the actual codebase capabilities?\n- **Completeness**: Coverage of installation, usage, configuration, troubleshooting?\n- **Governance messaging**: Clear contribution guidelines, roadmap, support channels?\n- **Math/algorithm exposition**: For technical projects, is the theory well-explained?\n\n### Maintenance Signals\n- **Recency**: Last commit within 6 months?\n- **Star count**: Indicator of community validation (>500 stars preferred)\n- **Maintainer activity**: Active issue responses, recent releases?\n- **CI/CD badges**: Evidence of automated quality checks?\n\n## Citation Format\n\nRecord each exemplar with full attribution:\n\n```markdown\n### Exemplar: [Project Name]\n- **URL**: https://github.com/[org]/[repo]\n- **Language**: [Primary language]\n- **Stars**: [count] (as of [date])\n- **Last Updated**: [date]\n- **Relevant Patterns**:\n  - [Pattern 1]: [Description and why it's relevant]\n  - [Pattern 2]: [Description and why it's relevant]\n  - [Pattern 3]: [Description and why it's relevant]\n- **Specific Elements to Adapt**:\n  - [Element]: [How it applies to this project]\n```\n\n## Storage Recommendations\n\n### Temporary Research Notes\nStore research findings in a temporary file during the session:\n\n```bash\n# Create research notes file\ncat > /tmp/readme-research.md << 'EOF'\n# README Exemplar Research\n\n## [Language 1] Exemplars\n[Citations...]\n\n## [Language 2] Exemplars\n[Citations...]\nEOF\n```\n\n### Final Report Integration\nInclude exemplar citations in the final verification report so future maintainers can:\n- Understand the design decisions\n- Revisit the sources for updates\n- Validate the approach against current best practices\n\n## Example Multi-Language Research\n\nFor a project with Rust backend and TypeScript frontend:\n\n1. **Rust Exemplars** (2-3 projects)\n   - Focus on: CLI tool patterns, installation via cargo, feature flags, performance claims\n\n2. **TypeScript Exemplars** (2-3 projects)\n   - Focus on: npm installation, dev environment setup, API documentation, framework integration\n\n3. **Full-Stack Exemplars** (1-2 projects)\n   - Focus on: How to structure README for multiple runtimes, quickstart for both components, architecture diagrams\n\n## Quality Threshold\n\nMinimum criteria for an exemplar to be useful:\n- Must have >100 stars OR be from a recognized organization\n- README must be >200 lines (substantial content)\n- Must have been updated in the last year\n- Must demonstrate at least 3 structural patterns relevant to the target project\n\nFile v1.9.17:modules/language-audit.md\n\n# Language Audit Patterns\n\nDetailed patterns and commands for detecting project languages and their documentation implications.\n\n## Manifest File Detection\n\nCheck for language-specific manifest files to identify the primary language(s):\n\n```bash\n# Rust\nls -1 Cargo.toml 2>/dev/null\n\n# Node.js/TypeScript\nls -1 package.json 2>/dev/null\n\n# Go\nls -1 go.mod 2>/dev/null\n\n# Python\nls -1 pyproject.toml setup.py requirements.txt 2>/dev/null\n\n# Java/Kotlin\nls -1 pom.xml build.gradle build.gradle.kts 2>/dev/null\n\n# Ruby\nls -1 Gemfile 2>/dev/null\n\n# PHP\nls -1 composer.json 2>/dev/null\n```\n\n## File Count Analysis\n\nCount source files by extension to determine language distribution:\n\n```bash\n# Rust\ngit ls-files | rg '\\.rs$' | wc -l\n# or for preview\nrg --files -g '*.rs' | head -10\n\n# Python\ngit ls-files | rg '\\.py$' | wc -l\nrg --files -g '*.py' | head -10\n\n# Go\ngit ls-files | rg '\\.go$' | wc -l\nrg --files -g '*.go' | head -10\n\n# TypeScript/JavaScript\ngit ls-files | rg '\\.(ts|tsx|js|jsx)$' | wc -l\nrg --files -g '*.ts' -g '*.tsx' | head -10\n\n# Java\ngit ls-files | rg '\\.java$' | wc -l\nrg --files -g '*.java' | head -10\n```\n\n## Language Priority Heuristics\n\nDetermine primary language using these priority rules:\n\n1. **Manifest presence**: If a language-specific manifest exists, it's a strong signal\n2. **File count dominance**: Language with >60% of source files is primary\n3. **Directory structure**: Check for language-specific directories (src/, lib/, pkg/)\n4. **Build configuration**: Presence of Makefile, CMakeLists.txt, or build scripts\n\n## Secondary Language Handling\n\nDocument secondary languages when they:\n\n- Represent >20% of codebase\n- Serve distinct architectural roles (e.g., Rust backend + TypeScript frontend)\n- Have their own build/test infrastructure\n- Require separate installation or runtime considerations\n\n### Example Multi-Language Documentation Strategy\n\n```markdown\n## Installation\n\n### Backend (Rust)\n[Rust-specific instructions]\n\n### Frontend (TypeScript)\n[Node/npm-specific instructions]\n```\n\n## Recording Findings\n\nCapture the audit results in a structured format:\n\n```\nLanguage Audit Results:\n- Primary: [Language] ([count] files, [manifest])\n- Secondary: [Language] ([count] files, [manifest])\n- Method: [manifest detection | file count | directory structure]\n- Documentation implications: [single-language | multi-language sections needed]\n```\n\nFile v1.9.17:skill-card.md\n\n## Description: <br>\nRefreshes README structure and content using repo context and exemplar research. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[athola](https://clawhub.ai/user/athola) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and maintainers use this skill to restructure and refresh a repository README after project changes, using language detection, exemplar research, outline alignment, README edits, and final verification. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill may edit README.md based on broad documentation triggers. <br>\nMitigation: Use it only for intended README restructuring work and review the resulting diff before committing. <br>\nRisk: The workflow may use web research for public README examples. <br>\nMitigation: Check exemplar citations and ensure adopted README patterns are supported by repository evidence. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-sanctum-update-readme) <br>\n- [Clawdis homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Markdown, Shell commands, Guidance] <br>\n**Output Format:** [Markdown guidance with command snippets and README edits] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Produces a revised README workflow output and a verification summary; installers should review the resulting diff before committing.] <br>\n\n## Skill Version(s): <br>\n1.9.17 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\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. <br>\n\nArchive v1.9.16: 5 files, 7446 bytes\n\nFiles: modules/exemplar-research.md (4022b), modules/language-audit.md (2375b), skill-card.md (2182b), SKILL.md (5813b), _meta.json (144b)\n\nFile v1.9.16:SKILL.md\n\n---\nname: update-readme\ndescription: Refreshes README structure and content using repo context and exemplar research\nversion: 1.9.8\ntriggers:\n  - readme\n  - documentation\n  - exemplars\n  - research\n  - structure\n  - README needs a structural update after significant project changes\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.sanctum:git-workspace-review\", \"night-market.imbue:proof-of-work\", \"night-market.scribe:slop-detector\", \"night-market.scribe:doc-generator\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# README Update Workflow\n\n## When To Use\nUse this skill whenever the README requires a structural refresh.\nRun `Skill(sanctum:git-workspace-review)` first to capture repo context and diffs.\n\n## When NOT To Use\n\n- Updating inline docs: use doc-updates\n- Consolidating ephemeral reports: use doc-consolidation\n\n## Required TodoWrite Items\n1. `update-readme:language-audit`\n2. `update-readme:exemplar-research`\n3. `update-readme:outline-aligned`\n4. `update-readme:edits-applied`\n5. `update-readme:slop-scanned` - AI marker detection via scribe\n6. `update-readme:verification-reporting`\n\n## Step 1 - Language Audit (`update-readme:language-audit`)\n- Confirm `pwd`, `git status -sb`, and the baseline branch for reference.\n- Detect dominant languages using repository heuristics (manifest files, file counts).\n- Note secondary languages that influence documentation (e.g., a TypeScript frontend and a Rust backend) so the README can surface both.\n- Record the method and findings.\n\nSee `modules/language-audit.md` for detailed detection patterns and commands.\n\n## Step 2 - Exemplar Research (`update-readme:exemplar-research`)\n- For each primary and secondary language, use web search to locate high-quality READMEs (star count, recency, maintainer activity).\n- Capture 2-3 exemplar repositories per language and summarize why each is relevant (section order, visuals, quickstart clarity, governance messaging, math exposition, etc.).\n- Store citations for every exemplar so the final summary references them explicitly.\n\nSee `modules/exemplar-research.md` for search query patterns and evaluation criteria.\n\n## Step 3 - Outline Alignment (`update-readme:outline-aligned`)\n- Compare current README headings (`rg -n '^#' README.md`) against patterns observed in exemplars.\n- Draft a target outline covering: value proposition, installation, quickstart, deeper usage/configuration, architecture/feature highlights, performance or math guarantees, documentation links, contribution/governance, roadmap/status, and licensing/security notes.\n- validate internal documents (docs/, specs/, wiki, commands/) are mapped to the relevant sections so the README anchors them with context-sensitive links.\n\n## Step 4 - Apply Edits (`update-readme:edits-applied`)\n- Implement the new structure directly in `README.md`\n  (or the specified file).\n- Follow `Skill(leyline:markdown-formatting)` conventions:\n  wrap prose at 80 chars (prefer sentence/clause boundaries),\n  blank lines around headings, ATX headings only, blank line\n  before lists, reference-style links for long URLs.\n- Maintain concise, evidence-based prose; avoid marketing fluff.\n- Add comparison tables, feature lists, or diagrams only if\n  they originate from current repository assets (no speculative\n  content).\n- When referencing algorithms or performance claims, point to\n  benchmarks or tests within the repository or documented math\n  reviews.\n\n## Step 4.5 - AI Slop Detection (`update-readme:slop-scanned`)\n\nRun `Skill(scribe:slop-detector)` on the updated README to detect AI-generated content markers.\n\n### Scribe Integration\n\nThe scribe plugin provides AI slop detection:\n\n```\nSkill(scribe:slop-detector) --target README.md\n```\n\nThis detects:\n- **Tier 1 words**: delve, tapestry, comprehensive, leveraging, etc.\n- **Phrase patterns**: \"In today's fast-paced world\", \"cannot be overstated\"\n- **Structural markers**: Excessive em dashes, bullet overuse, sentence uniformity\n- **Marketing language**: \"enterprise-ready\", \"cutting-edge\", \"seamless\"\n\n### Remediation\n\nIf slop score exceeds 2.0 (moderate), apply `Skill(scribe:doc-generator)` principles:\n\n1. Ground every claim with specifics\n2. Remove formulaic openers/closers\n3. Use numbers, commands, filenames over adjectives\n4. Balance bullets with narrative prose\n5. Show authorial perspective (trade-offs, reasoning)\n\nFor significant cleanup needs, use:\n\n```\nAgent(scribe:doc-editor) --target README.md\n```\n\n## Step 5 - Verification & Reporting (`update-readme:verification-reporting`)\n- Re-read the updated README for clarity, accessibility (section lengths, bullet balance), and accurate links.\n- Run `git diff README.md` (or the edited file) and capture snippets for the final report.\n- Summarize detected languages, exemplar sources (with citations), key structural decisions, and follow-up TODOs (e.g., add badges, upload diagrams).\n\n## Exit Criteria\n- All `TodoWrite` items are complete.\n- The README reflects a modern, language-aware structure, referencing both internal docs and external inspiration with citations.\n- Research notes and command references are captured so future reviewers can reproduce the process.\n## Troubleshooting\n\n### Common Issues\n\n**Documentation out of sync**\nRun `make docs-update` to regenerate from code\n\n**Build failures**\nCheck that all required dependencies are installed\n\n**Links broken**\nVerify relative paths in documentation files\n\nFile v1.9.16:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-sanctum-update-readme\",\n  \"version\": \"1.9.16\",\n  \"publishedAt\": 1784059090077\n}\n\nFile v1.9.16:modules/exemplar-research.md\n\n# Exemplar Research Patterns\n\nDetailed patterns for finding, evaluating, and documenting high-quality README exemplars.\n\n## Web Search Query Patterns\n\n### Language-Specific Queries\n\n```\n\"GitHub [language] README best practices\"\n\"[language] framework README examples\"\n\"[language] project README badges\"\n\"[language] library documentation structure\"\n\"awesome [language] README\"\n```\n\n### Framework/Domain-Specific Queries\n\n```\n\"[framework] README structure\"\n\"[domain] project README examples\" (e.g., \"CLI tool README examples\")\n\"[language] [project-type] documentation\" (e.g., \"Rust async library documentation\")\n```\n\n### Quality Indicators\n\n```\n\"high star count [language] README\"\n\"well-maintained [language] project README\"\n\"[language] project documentation best practices 2024\"\n```\n\n## Exemplar Evaluation Criteria\n\nAssess each candidate README using these dimensions:\n\n### Structure & Organization\n- **Section order**: Does it follow a logical progression (value → quickstart → details)?\n- **Progressive disclosure**: Are complex topics deferred until after basics?\n- **Table of contents**: Is it present and well-structured?\n- **Visual hierarchy**: Clear heading levels, spacing, readability?\n\n### Content Quality\n- **Value proposition**: Clear statement of what the project does and why it matters?\n- **Quickstart clarity**: Can a new user get started in <5 minutes?\n- **Code examples**: Are they runnable, realistic, well-commented?\n- **Installation steps**: Clear, tested, platform-aware?\n\n### Technical Communication\n- **Accuracy**: Does it match the actual codebase capabilities?\n- **Completeness**: Coverage of installation, usage, configuration, troubleshooting?\n- **Governance messaging**: Clear contribution guidelines, roadmap, support channels?\n- **Math/algorithm exposition**: For technical projects, is the theory well-explained?\n\n### Maintenance Signals\n- **Recency**: Last commit within 6 months?\n- **Star count**: Indicator of community validation (>500 stars preferred)\n- **Maintainer activity**: Active issue responses, recent releases?\n- **CI/CD badges**: Evidence of automated quality checks?\n\n## Citation Format\n\nRecord each exemplar with full attribution:\n\n```markdown\n### Exemplar: [Project Name]\n- **URL**: https://github.com/[org]/[repo]\n- **Language**: [Primary language]\n- **Stars**: [count] (as of [date])\n- **Last Updated**: [date]\n- **Relevant Patterns**:\n  - [Pattern 1]: [Description and why it's relevant]\n  - [Pattern 2]: [Description and why it's relevant]\n  - [Pattern 3]: [Description and why it's relevant]\n- **Specific Elements to Adapt**:\n  - [Element]: [How it applies to this project]\n```\n\n## Storage Recommendations\n\n### Temporary Research Notes\nStore research findings in a temporary file during the session:\n\n```bash\n# Create research notes file\ncat > /tmp/readme-research.md << 'EOF'\n# README Exemplar Research\n\n## [Language 1] Exemplars\n[Citations...]\n\n## [Language 2] Exemplars\n[Citations...]\nEOF\n```\n\n### Final Report Integration\nInclude exemplar citations in the final verification report so future maintainers can:\n- Understand the design decisions\n- Revisit the sources for updates\n- Validate the approach against current best practices\n\n## Example Multi-Language Research\n\nFor a project with Rust backend and TypeScript frontend:\n\n1. **Rust Exemplars** (2-3 projects)\n   - Focus on: CLI tool patterns, installation via cargo, feature flags, performance claims\n\n2. **TypeScript Exemplars** (2-3 projects)\n   - Focus on: npm installation, dev environment setup, API documentation, framework integration\n\n3. **Full-Stack Exemplars** (1-2 projects)\n   - Focus on: How to structure README for multiple runtimes, quickstart for both components, architecture diagrams\n\n## Quality Threshold\n\nMinimum criteria for an exemplar to be useful:\n- Must have >100 stars OR be from a recognized organization\n- README must be >200 lines (substantial content)\n- Must have been updated in the last year\n- Must demonstrate at least 3 structural patterns relevant to the target project\n\nFile v1.9.16:modules/language-audit.md\n\n# Language Audit Patterns\n\nDetailed patterns and commands for detecting project languages and their documentation implications.\n\n## Manifest File Detection\n\nCheck for language-specific manifest files to identify the primary language(s):\n\n```bash\n# Rust\nls -1 Cargo.toml 2>/dev/null\n\n# Node.js/TypeScript\nls -1 package.json 2>/dev/null\n\n# Go\nls -1 go.mod 2>/dev/null\n\n# Python\nls -1 pyproject.toml setup.py requirements.txt 2>/dev/null\n\n# Java/Kotlin\nls -1 pom.xml build.gradle build.gradle.kts 2>/dev/null\n\n# Ruby\nls -1 Gemfile 2>/dev/null\n\n# PHP\nls -1 composer.json 2>/dev/null\n```\n\n## File Count Analysis\n\nCount source files by extension to determine language distribution:\n\n```bash\n# Rust\ngit ls-files | rg '\\.rs$' | wc -l\n# or for preview\nrg --files -g '*.rs' | head -10\n\n# Python\ngit ls-files | rg '\\.py$' | wc -l\nrg --files -g '*.py' | head -10\n\n# Go\ngit ls-files | rg '\\.go$' | wc -l\nrg --files -g '*.go' | head -10\n\n# TypeScript/JavaScript\ngit ls-files | rg '\\.(ts|tsx|js|jsx)$' | wc -l\nrg --files -g '*.ts' -g '*.tsx' | head -10\n\n# Java\ngit ls-files | rg '\\.java$' | wc -l\nrg --files -g '*.java' | head -10\n```\n\n## Language Priority Heuristics\n\nDetermine primary language using these priority rules:\n\n1. **Manifest presence**: If a language-specific manifest exists, it's a strong signal\n2. **File count dominance**: Language with >60% of source files is primary\n3. **Directory structure**: Check for language-specific directories (src/, lib/, pkg/)\n4. **Build configuration**: Presence of Makefile, CMakeLists.txt, or build scripts\n\n## Secondary Language Handling\n\nDocument secondary languages when they:\n\n- Represent >20% of codebase\n- Serve distinct architectural roles (e.g., Rust backend + TypeScript frontend)\n- Have their own build/test infrastructure\n- Require separate installation or runtime considerations\n\n### Example Multi-Language Documentation Strategy\n\n```markdown\n## Installation\n\n### Backend (Rust)\n[Rust-specific instructions]\n\n### Frontend (TypeScript)\n[Node/npm-specific instructions]\n```\n\n## Recording Findings\n\nCapture the audit results in a structured format:\n\n```\nLanguage Audit Results:\n- Primary: [Language] ([count] files, [manifest])\n- Secondary: [Language] ([count] files, [manifest])\n- Method: [manifest detection | file count | directory structure]\n- Documentation implications: [single-language | multi-language sections needed]\n```\n\nFile v1.9.16:skill-card.md\n\n## Description: <br>\nRefreshes README structure and content using repo context and exemplar research. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[athola](https://clawhub.ai/user/athola) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and documentation maintainers use this skill to restructure a README after meaningful project changes, using repository context, language detection, exemplar research, and review steps to guide edits. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Broad documentation and research triggers may activate the workflow for requests that are not intended to update a README. <br>\nMitigation: Confirm the target file and README scope before allowing edits. <br>\nRisk: README restructuring can introduce inaccurate claims, stale links, or misleading guidance. <br>\nMitigation: Review the README diff, verify links and citations, and keep claims grounded in repository evidence before relying on the output. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-sanctum-update-readme) <br>\n- [Sanctum plugin homepage from metadata](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum) <br>\n- [Language Audit Patterns](modules/language-audit.md) <br>\n- [Exemplar Research Patterns](modules/exemplar-research.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [markdown, code, shell commands, guidance] <br>\n**Output Format:** [Markdown prose, README edits, command snippets, and verification notes] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May edit README.md or a specified documentation file and may include citations from exemplar research.] <br>\n\n## Skill Version(s): <br>\n1.9.16 (source: server release metadata; artifact frontmatter lists 1.9.8) <br>\n\n## Ethical Considerations: <br>\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. <br>\n\nArchive v1.9.14: 5 files, 7473 bytes\n\nFiles: modules/exemplar-research.md (4022b), modules/language-audit.md (2375b), skill-card.md (2275b), SKILL.md (5813b), _meta.json (144b)\n\nFile v1.9.14:SKILL.md\n\n---\nname: update-readme\ndescription: Refreshes README structure and content using repo context and exemplar research\nversion: 1.9.8\ntriggers:\n  - readme\n  - documentation\n  - exemplars\n  - research\n  - structure\n  - README needs a structural update after significant project changes\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.sanctum:git-workspace-review\", \"night-market.imbue:proof-of-work\", \"night-market.scribe:slop-detector\", \"night-market.scribe:doc-generator\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# README Update Workflow\n\n## When To Use\nUse this skill whenever the README requires a structural refresh.\nRun `Skill(sanctum:git-workspace-review)` first to capture repo context and diffs.\n\n## When NOT To Use\n\n- Updating inline docs: use doc-updates\n- Consolidating ephemeral reports: use doc-consolidation\n\n## Required TodoWrite Items\n1. `update-readme:language-audit`\n2. `update-readme:exemplar-research`\n3. `update-readme:outline-aligned`\n4. `update-readme:edits-applied`\n5. `update-readme:slop-scanned` - AI marker detection via scribe\n6. `update-readme:verification-reporting`\n\n## Step 1 - Language Audit (`update-readme:language-audit`)\n- Confirm `pwd`, `git status -sb`, and the baseline branch for reference.\n- Detect dominant languages using repository heuristics (manifest files, file counts).\n- Note secondary languages that influence documentation (e.g., a TypeScript frontend and a Rust backend) so the README can surface both.\n- Record the method and findings.\n\nSee `modules/language-audit.md` for detailed detection patterns and commands.\n\n## Step 2 - Exemplar Research (`update-readme:exemplar-research`)\n- For each primary and secondary language, use web search to locate high-quality READMEs (star count, recency, maintainer activity).\n- Capture 2-3 exemplar repositories per language and summarize why each is relevant (section order, visuals, quickstart clarity, governance messaging, math exposition, etc.).\n- Store citations for every exemplar so the final summary references them explicitly.\n\nSee `modules/exemplar-research.md` for search query patterns and evaluation criteria.\n\n## Step 3 - Outline Alignment (`update-readme:outline-aligned`)\n- Compare current README headings (`rg -n '^#' README.md`) against patterns observed in exemplars.\n- Draft a target outline covering: value proposition, installation, quickstart, deeper usage/configuration, architecture/feature highlights, performance or math guarantees, documentation links, contribution/governance, roadmap/status, and licensing/security notes.\n- validate internal documents (docs/, specs/, wiki, commands/) are mapped to the relevant sections so the README anchors them with context-sensitive links.\n\n## Step 4 - Apply Edits (`update-readme:edits-applied`)\n- Implement the new structure directly in `README.md`\n  (or the specified file).\n- Follow `Skill(leyline:markdown-formatting)` conventions:\n  wrap prose at 80 chars (prefer sentence/clause boundaries),\n  blank lines around headings, ATX headings only, blank line\n  before lists, reference-style links for long URLs.\n- Maintain concise, evidence-based prose; avoid marketing fluff.\n- Add comparison tables, feature lists, or diagrams only if\n  they originate from current repository assets (no speculative\n  content).\n- When referencing algorithms or performance claims, point to\n  benchmarks or tests within the repository or documented math\n  reviews.\n\n## Step 4.5 - AI Slop Detection (`update-readme:slop-scanned`)\n\nRun `Skill(scribe:slop-detector)` on the updated README to detect AI-generated content markers.\n\n### Scribe Integration\n\nThe scribe plugin provides AI slop detection:\n\n```\nSkill(scribe:slop-detector) --target README.md\n```\n\nThis detects:\n- **Tier 1 words**: delve, tapestry, comprehensive, leveraging, etc.\n- **Phrase patterns**: \"In today's fast-paced world\", \"cannot be overstated\"\n- **Structural markers**: Excessive em dashes, bullet overuse, sentence uniformity\n- **Marketing language**: \"enterprise-ready\", \"cutting-edge\", \"seamless\"\n\n### Remediation\n\nIf slop score exceeds 2.0 (moderate), apply `Skill(scribe:doc-generator)` principles:\n\n1. Ground every claim with specifics\n2. Remove formulaic openers/closers\n3. Use numbers, commands, filenames over adjectives\n4. Balance bullets with narrative prose\n5. Show authorial perspective (trade-offs, reasoning)\n\nFor significant cleanup needs, use:\n\n```\nAgent(scribe:doc-editor) --target README.md\n```\n\n## Step 5 - Verification & Reporting (`update-readme:verification-reporting`)\n- Re-read the updated README for clarity, accessibility (section lengths, bullet balance), and accurate links.\n- Run `git diff README.md` (or the edited file) and capture snippets for the final report.\n- Summarize detected languages, exemplar sources (with citations), key structural decisions, and follow-up TODOs (e.g., add badges, upload diagrams).\n\n## Exit Criteria\n- All `TodoWrite` items are complete.\n- The README reflects a modern, language-aware structure, referencing both internal docs and external inspiration with citations.\n- Research notes and command references are captured so future reviewers can reproduce the process.\n## Troubleshooting\n\n### Common Issues\n\n**Documentation out of sync**\nRun `make docs-update` to regenerate from code\n\n**Build failures**\nCheck that all required dependencies are installed\n\n**Links broken**\nVerify relative paths in documentation files\n\nFile v1.9.14:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-sanctum-update-readme\",\n  \"version\": \"1.9.14\",\n  \"publishedAt\": 1782842759607\n}\n\nFile v1.9.14:modules/exemplar-research.md\n\n# Exemplar Research Patterns\n\nDetailed patterns for finding, evaluating, and documenting high-quality README exemplars.\n\n## Web Search Query Patterns\n\n### Language-Specific Queries\n\n```\n\"GitHub [language] README best practices\"\n\"[language] framework README examples\"\n\"[language] project README badges\"\n\"[language] library documentation structure\"\n\"awesome [language] README\"\n```\n\n### Framework/Domain-Specific Queries\n\n```\n\"[framework] README structure\"\n\"[domain] project README examples\" (e.g., \"CLI tool README examples\")\n\"[language] [project-type] documentation\" (e.g., \"Rust async library documentation\")\n```\n\n### Quality Indicators\n\n```\n\"high star count [language] README\"\n\"well-maintained [language] project README\"\n\"[language] project documentation best practices 2024\"\n```\n\n## Exemplar Evaluation Criteria\n\nAssess each candidate README using these dimensions:\n\n### Structure & Organization\n- **Section order**: Does it follow a logical progression (value → quickstart → details)?\n- **Progressive disclosure**: Are complex topics deferred until after basics?\n- **Table of contents**: Is it present and well-structured?\n- **Visual hierarchy**: Clear heading levels, spacing, readability?\n\n### Content Quality\n- **Value proposition**: Clear statement of what the project does and why it matters?\n- **Quickstart clarity**: Can a new user get started in <5 minutes?\n- **Code examples**: Are they runnable, realistic, well-commented?\n- **Installation steps**: Clear, tested, platform-aware?\n\n### Technical Communication\n- **Accuracy**: Does it match the actual codebase capabilities?\n- **Completeness**: Coverage of installation, usage, configuration, troubleshooting?\n- **Governance messaging**: Clear contribution guidelines, roadmap, support channels?\n- **Math/algorithm exposition**: For technical projects, is the theory well-explained?\n\n### Maintenance Signals\n- **Recency**: Last commit within 6 months?\n- **Star count**: Indicator of community validation (>500 stars preferred)\n- **Maintainer activity**: Active issue responses, recent releases?\n- **CI/CD badges**: Evidence of automated quality checks?\n\n## Citation Format\n\nRecord each exemplar with full attribution:\n\n```markdown\n### Exemplar: [Project Name]\n- **URL**: https://github.com/[org]/[repo]\n- **Language**: [Primary language]\n- **Stars**: [count] (as of [date])\n- **Last Updated**: [date]\n- **Relevant Patterns**:\n  - [Pattern 1]: [Description and why it's relevant]\n  - [Pattern 2]: [Description and why it's relevant]\n  - [Pattern 3]: [Description and why it's relevant]\n- **Specific Elements to Adapt**:\n  - [Element]: [How it applies to this project]\n```\n\n## Storage Recommendations\n\n### Temporary Research Notes\nStore research findings in a temporary file during the session:\n\n```bash\n# Create research notes file\ncat > /tmp/readme-research.md << 'EOF'\n# README Exemplar Research\n\n## [Language 1] Exemplars\n[Citations...]\n\n## [Language 2] Exemplars\n[Citations...]\nEOF\n```\n\n### Final Report Integration\nInclude exemplar citations in the final verification report so future maintainers can:\n- Understand the design decisions\n- Revisit the sources for updates\n- Validate the approach against current best practices\n\n## Example Multi-Language Research\n\nFor a project with Rust backend and TypeScript frontend:\n\n1. **Rust Exemplars** (2-3 projects)\n   - Focus on: CLI tool patterns, installation via cargo, feature flags, performance claims\n\n2. **TypeScript Exemplars** (2-3 projects)\n   - Focus on: npm installation, dev environment setup, API documentation, framework integration\n\n3. **Full-Stack Exemplars** (1-2 projects)\n   - Focus on: How to structure README for multiple runtimes, quickstart for both components, architecture diagrams\n\n## Quality Threshold\n\nMinimum criteria for an exemplar to be useful:\n- Must have >100 stars OR be from a recognized organization\n- README must be >200 lines (substantial content)\n- Must have been updated in the last year\n- Must demonstrate at least 3 structural patterns relevant to the target project\n\nFile v1.9.14:modules/language-audit.md\n\n# Language Audit Patterns\n\nDetailed patterns and commands for detecting project languages and their documentation implications.\n\n## Manifest File Detection\n\nCheck for language-specific manifest files to identify the primary language(s):\n\n```bash\n# Rust\nls -1 Cargo.toml 2>/dev/null\n\n# Node.js/TypeScript\nls -1 package.json 2>/dev/null\n\n# Go\nls -1 go.mod 2>/dev/null\n\n# Python\nls -1 pyproject.toml setup.py requirements.txt 2>/dev/null\n\n# Java/Kotlin\nls -1 pom.xml build.gradle build.gradle.kts 2>/dev/null\n\n# Ruby\nls -1 Gemfile 2>/dev/null\n\n# PHP\nls -1 composer.json 2>/dev/null\n```\n\n## File Count Analysis\n\nCount source files by extension to determine language distribution:\n\n```bash\n# Rust\ngit ls-files | rg '\\.rs$' | wc -l\n# or for preview\nrg --files -g '*.rs' | head -10\n\n# Python\ngit ls-files | rg '\\.py$' | wc -l\nrg --files -g '*.py' | head -10\n\n# Go\ngit ls-files | rg '\\.go$' | wc -l\nrg --files -g '*.go' | head -10\n\n# TypeScript/JavaScript\ngit ls-files | rg '\\.(ts|tsx|js|jsx)$' | wc -l\nrg --files -g '*.ts' -g '*.tsx' | head -10\n\n# Java\ngit ls-files | rg '\\.java$' | wc -l\nrg --files -g '*.java' | head -10\n```\n\n## Language Priority Heuristics\n\nDetermine primary language using these priority rules:\n\n1. **Manifest presence**: If a language-specific manifest exists, it's a strong signal\n2. **File count dominance**: Language with >60% of source files is primary\n3. **Directory structure**: Check for language-specific directories (src/, lib/, pkg/)\n4. **Build configuration**: Presence of Makefile, CMakeLists.txt, or build scripts\n\n## Secondary Language Handling\n\nDocument secondary languages when they:\n\n- Represent >20% of codebase\n- Serve distinct architectural roles (e.g., Rust backend + TypeScript frontend)\n- Have their own build/test infrastructure\n- Require separate installation or runtime considerations\n\n### Example Multi-Language Documentation Strategy\n\n```markdown\n## Installation\n\n### Backend (Rust)\n[Rust-specific instructions]\n\n### Frontend (TypeScript)\n[Node/npm-specific instructions]\n```\n\n## Recording Findings\n\nCapture the audit results in a structured format:\n\n```\nLanguage Audit Results:\n- Primary: [Language] ([count] files, [manifest])\n- Secondary: [Language] ([count] files, [manifest])\n- Method: [manifest detection | file count | directory structure]\n- Documentation implications: [single-language | multi-language sections needed]\n```\n\nFile v1.9.14:skill-card.md\n\n## Description: <br>\nRefreshes README structure and content using repository context and exemplar research. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[athola](https://clawhub.ai/user/athola) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and documentation maintainers use this skill to audit a repository, research high-quality README exemplars, restructure README content, apply evidence-based edits, and report verification details. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill can inspect repository documentation and modify README or governance documents. <br>\nMitigation: Use report-only mode or require explicit approval before writes when automatic documentation changes are not desired. <br>\nRisk: README updates may introduce inaccurate claims if repository evidence or exemplar comparisons are misapplied. <br>\nMitigation: Review the generated diff, verify links and claims against repository assets, and require benchmark or test evidence for performance or algorithm statements. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-sanctum-update-readme) <br>\n- [Metadata homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum) <br>\n- [Language audit patterns](artifact/modules/language-audit.md) <br>\n- [Exemplar research patterns](artifact/modules/exemplar-research.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Text, Markdown, Code, Shell commands, Guidance] <br>\n**Output Format:** [Markdown documentation edits with command summaries and verification notes] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May update README.md or a specified documentation file and summarize language findings, exemplar citations, structural decisions, and follow-up TODOs.] <br>\n\n## Skill Version(s): <br>\n1.9.14 (source: ClawHub release metadata) <br>\n\n## Ethical Considerations: <br>\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. <br>\n\nArchive v1.9.13: 5 files, 7580 bytes\n\nFiles: modules/exemplar-research.md (4022b), modules/language-audit.md (2375b), skill-card.md (2598b), SKILL.md (5813b), _meta.json (144b)\n\nFile v1.9.13:SKILL.md\n\n---\nname: update-readme\ndescription: Refreshes README structure and content using repo context and exemplar research\nversion: 1.9.8\ntriggers:\n  - readme\n  - documentation\n  - exemplars\n  - research\n  - structure\n  - README needs a structural update after significant project changes\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.sanctum:git-workspace-review\", \"night-market.imbue:proof-of-work\", \"night-market.scribe:slop-detector\", \"night-market.scribe:doc-generator\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# README Update Workflow\n\n## When To Use\nUse this skill whenever the README requires a structural refresh.\nRun `Skill(sanctum:git-workspace-review)` first to capture repo context and diffs.\n\n## When NOT To Use\n\n- Updating inline docs: use doc-updates\n- Consolidating ephemeral reports: use doc-consolidation\n\n## Required TodoWrite Items\n1. `update-readme:language-audit`\n2. `update-readme:exemplar-research`\n3. `update-readme:outline-aligned`\n4. `update-readme:edits-applied`\n5. `update-readme:slop-scanned` - AI marker detection via scribe\n6. `update-readme:verification-reporting`\n\n## Step 1 - Language Audit (`update-readme:language-audit`)\n- Confirm `pwd`, `git status -sb`, and the baseline branch for reference.\n- Detect dominant languages using repository heuristics (manifest files, file counts).\n- Note secondary languages that influence documentation (e.g., a TypeScript frontend and a Rust backend) so the README can surface both.\n- Record the method and findings.\n\nSee `modules/language-audit.md` for detailed detection patterns and commands.\n\n## Step 2 - Exemplar Research (`update-readme:exemplar-research`)\n- For each primary and secondary language, use web search to locate high-quality READMEs (star count, recency, maintainer activity).\n- Capture 2-3 exemplar repositories per language and summarize why each is relevant (section order, visuals, quickstart clarity, governance messaging, math exposition, etc.).\n- Store citations for every exemplar so the final summary references them explicitly.\n\nSee `modules/exemplar-research.md` for search query patterns and evaluation criteria.\n\n## Step 3 - Outline Alignment (`update-readme:outline-aligned`)\n- Compare current README headings (`rg -n '^#' README.md`) against patterns observed in exemplars.\n- Draft a target outline covering: value proposition, installation, quickstart, deeper usage/configuration, architecture/feature highlights, performance or math guarantees, documentation links, contribution/governance, roadmap/status, and licensing/security notes.\n- validate internal documents (docs/, specs/, wiki, commands/) are mapped to the relevant sections so the README anchors them with context-sensitive links.\n\n## Step 4 - Apply Edits (`update-readme:edits-applied`)\n- Implement the new structure directly in `README.md`\n  (or the specified file).\n- Follow `Skill(leyline:markdown-formatting)` conventions:\n  wrap prose at 80 chars (prefer sentence/clause boundaries),\n  blank lines around headings, ATX headings only, blank line\n  before lists, reference-style links for long URLs.\n- Maintain concise, evidence-based prose; avoid marketing fluff.\n- Add comparison tables, feature lists, or diagrams only if\n  they originate from current repository assets (no speculative\n  content).\n- When referencing algorithms or performance claims, point to\n  benchmarks or tests within the repository or documented math\n  reviews.\n\n## Step 4.5 - AI Slop Detection (`update-readme:slop-scanned`)\n\nRun `Skill(scribe:slop-detector)` on the updated README to detect AI-generated content markers.\n\n### Scribe Integration\n\nThe scribe plugin provides AI slop detection:\n\n```\nSkill(scribe:slop-detector) --target README.md\n```\n\nThis detects:\n- **Tier 1 words**: delve, tapestry, comprehensive, leveraging, etc.\n- **Phrase patterns**: \"In today's fast-paced world\", \"cannot be overstated\"\n- **Structural markers**: Excessive em dashes, bullet overuse, sentence uniformity\n- **Marketing language**: \"enterprise-ready\", \"cutting-edge\", \"seamless\"\n\n### Remediation\n\nIf slop score exceeds 2.0 (moderate), apply `Skill(scribe:doc-generator)` principles:\n\n1. Ground every claim with specifics\n2. Remove formulaic openers/closers\n3. Use numbers, commands, filenames over adjectives\n4. Balance bullets with narrative prose\n5. Show authorial perspective (trade-offs, reasoning)\n\nFor significant cleanup needs, use:\n\n```\nAgent(scribe:doc-editor) --target README.md\n```\n\n## Step 5 - Verification & Reporting (`update-readme:verification-reporting`)\n- Re-read the updated README for clarity, accessibility (section lengths, bullet balance), and accurate links.\n- Run `git diff README.md` (or the edited file) and capture snippets for the final report.\n- Summarize detected languages, exemplar sources (with citations), key structural decisions, and follow-up TODOs (e.g., add badges, upload diagrams).\n\n## Exit Criteria\n- All `TodoWrite` items are complete.\n- The README reflects a modern, language-aware structure, referencing both internal docs and external inspiration with citations.\n- Research notes and command references are captured so future reviewers can reproduce the process.\n## Troubleshooting\n\n### Common Issues\n\n**Documentation out of sync**\nRun `make docs-update` to regenerate from code\n\n**Build failures**\nCheck that all required dependencies are installed\n\n**Links broken**\nVerify relative paths in documentation files\n\nFile v1.9.13:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-sanctum-update-readme\",\n  \"version\": \"1.9.13\",\n  \"publishedAt\": 1782577425526\n}\n\nFile v1.9.13:modules/exemplar-research.md\n\n# Exemplar Research Patterns\n\nDetailed patterns for finding, evaluating, and documenting high-quality README exemplars.\n\n## Web Search Query Patterns\n\n### Language-Specific Queries\n\n```\n\"GitHub [language] README best practices\"\n\"[language] framework README examples\"\n\"[language] project README badges\"\n\"[language] library documentation structure\"\n\"awesome [language] README\"\n```\n\n### Framework/Domain-Specific Queries\n\n```\n\"[framework] README structure\"\n\"[domain] project README examples\" (e.g., \"CLI tool README examples\")\n\"[language] [project-type] documentation\" (e.g., \"Rust async library documentation\")\n```\n\n### Quality Indicators\n\n```\n\"high star count [language] README\"\n\"well-maintained [language] project README\"\n\"[language] project documentation best practices 2024\"\n```\n\n## Exemplar Evaluation Criteria\n\nAssess each candidate README using these dimensions:\n\n### Structure & Organization\n- **Section order**: Does it follow a logical progression (value → quickstart → details)?\n- **Progressive disclosure**: Are complex topics deferred until after basics?\n- **Table of contents**: Is it present and well-structured?\n- **Visual hierarchy**: Clear heading levels, spacing, readability?\n\n### Content Quality\n- **Value proposition**: Clear statement of what the project does and why it matters?\n- **Quickstart clarity**: Can a new user get started in <5 minutes?\n- **Code examples**: Are they runnable, realistic, well-commented?\n- **Installation steps**: Clear, tested, platform-aware?\n\n### Technical Communication\n- **Accuracy**: Does it match the actual codebase capabilities?\n- **Completeness**: Coverage of installation, usage, configuration, troubleshooting?\n- **Governance messaging**: Clear contribution guidelines, roadmap, support channels?\n- **Math/algorithm exposition**: For technical projects, is the theory well-explained?\n\n### Maintenance Signals\n- **Recency**: Last commit within 6 months?\n- **Star count**: Indicator of community validation (>500 stars preferred)\n- **Maintainer activity**: Active issue responses, recent releases?\n- **CI/CD badges**: Evidence of automated quality checks?\n\n## Citation Format\n\nRecord each exemplar with full attribution:\n\n```markdown\n### Exemplar: [Project Name]\n- **URL**: https://github.com/[org]/[repo]\n- **Language**: [Primary language]\n- **Stars**: [count] (as of [date])\n- **Last Updated**: [date]\n- **Relevant Patterns**:\n  - [Pattern 1]: [Description and why it's relevant]\n  - [Pattern 2]: [Description and why it's relevant]\n  - [Pattern 3]: [Description and why it's relevant]\n- **Specific Elements to Adapt**:\n  - [Element]: [How it applies to this project]\n```\n\n## Storage Recommendations\n\n### Temporary Research Notes\nStore research findings in a temporary file during the session:\n\n```bash\n# Create research notes file\ncat > /tmp/readme-research.md << 'EOF'\n# README Exemplar Research\n\n## [Language 1] Exemplars\n[Citations...]\n\n## [Language 2] Exemplars\n[Citations...]\nEOF\n```\n\n### Final Report Integration\nInclude exemplar citations in the final verification report so future maintainers can:\n- Understand the design decisions\n- Revisit the sources for updates\n- Validate the approach against current best practices\n\n## Example Multi-Language Research\n\nFor a project with Rust backend and TypeScript frontend:\n\n1. **Rust Exemplars** (2-3 projects)\n   - Focus on: CLI tool patterns, installation via cargo, feature flags, performance claims\n\n2. **TypeScript Exemplars** (2-3 projects)\n   - Focus on: npm installation, dev environment setup, API documentation, framework integration\n\n3. **Full-Stack Exemplars** (1-2 projects)\n   - Focus on: How to structure README for multiple runtimes, quickstart for both components, architecture diagrams\n\n## Quality Threshold\n\nMinimum criteria for an exemplar to be useful:\n- Must have >100 stars OR be from a recognized organization\n- README must be >200 lines (substantial content)\n- Must have been updated in the last year\n- Must demonstrate at least 3 structural patterns relevant to the target project\n\nFile v1.9.13:modules/language-audit.md\n\n# Language Audit Patterns\n\nDetailed patterns and commands for detecting project languages and their documentation implications.\n\n## Manifest File Detection\n\nCheck for language-specific manifest files to identify the primary language(s):\n\n```bash\n# Rust\nls -1 Cargo.toml 2>/dev/null\n\n# Node.js/TypeScript\nls -1 package.json 2>/dev/null\n\n# Go\nls -1 go.mod 2>/dev/null\n\n# Python\nls -1 pyproject.toml setup.py requirements.txt 2>/dev/null\n\n# Java/Kotlin\nls -1 pom.xml build.gradle build.gradle.kts 2>/dev/null\n\n# Ruby\nls -1 Gemfile 2>/dev/null\n\n# PHP\nls -1 composer.json 2>/dev/null\n```\n\n## File Count Analysis\n\nCount source files by extension to determine language distribution:\n\n```bash\n# Rust\ngit ls-files | rg '\\.rs$' | wc -l\n# or for preview\nrg --files -g '*.rs' | head -10\n\n# Python\ngit ls-files | rg '\\.py$' | wc -l\nrg --files -g '*.py' | head -10\n\n# Go\ngit ls-files | rg '\\.go$' | wc -l\nrg --files -g '*.go' | head -10\n\n# TypeScript/JavaScript\ngit ls-files | rg '\\.(ts|tsx|js|jsx)$' | wc -l\nrg --files -g '*.ts' -g '*.tsx' | head -10\n\n# Java\ngit ls-files | rg '\\.java$' | wc -l\nrg --files -g '*.java' | head -10\n```\n\n## Language Priority Heuristics\n\nDetermine primary language using these priority rules:\n\n1. **Manifest presence**: If a language-specific manifest exists, it's a strong signal\n2. **File count dominance**: Language with >60% of source files is primary\n3. **Directory structure**: Check for language-specific directories (src/, lib/, pkg/)\n4. **Build configuration**: Presence of Makefile, CMakeLists.txt, or build scripts\n\n## Secondary Language Handling\n\nDocument secondary languages when they:\n\n- Represent >20% of codebase\n- Serve distinct architectural roles (e.g., Rust backend + TypeScript frontend)\n- Have their own build/test infrastructure\n- Require separate installation or runtime considerations\n\n### Example Multi-Language Documentation Strategy\n\n```markdown\n## Installation\n\n### Backend (Rust)\n[Rust-specific instructions]\n\n### Frontend (TypeScript)\n[Node/npm-specific instructions]\n```\n\n## Recording Findings\n\nCapture the audit results in a structured format:\n\n```\nLanguage Audit Results:\n- Primary: [Language] ([count] files, [manifest])\n- Secondary: [Language] ([count] files, [manifest])\n- Method: [manifest detection | file count | directory structure]\n- Documentation implications: [single-language | multi-language sections needed]\n```\n\nFile v1.9.13:skill-card.md\n\n## Description: <br>\nRefreshes README structure and content using repo context and exemplar research. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[athola](https://clawhub.ai/user/athola) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and maintainers use this skill to refresh README.md or another documentation file after significant project changes. It guides repository language detection, exemplar README research, outline alignment, direct documentation edits, and final verification. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill can edit README.md or another documentation file based on repository context and external examples. <br>\nMitigation: Review the documentation diff, cited exemplar sources, and final verification report before merging changes. <br>\nRisk: The skill has broad documentation-related triggers and relies on related Night Market capabilities when available. <br>\nMitigation: Invoke it only for explicit README refresh tasks and review the related Night Market dependencies separately in environments that support them. <br>\nRisk: External README research can introduce stale, irrelevant, or unsupported patterns into project documentation. <br>\nMitigation: Require citations for exemplar-derived decisions and keep claims grounded in current repository files, tests, benchmarks, or documented reviews. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-sanctum-update-readme) <br>\n- [Night Market Sanctum plugin](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum) <br>\n- [Language Audit Patterns](artifact/modules/language-audit.md) <br>\n- [Exemplar Research Patterns](artifact/modules/exemplar-research.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Text, Markdown, Files, Shell commands, Guidance] <br>\n**Output Format:** [Markdown prose with command snippets and an edited README or documentation file] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May include citations for external README exemplars and a final verification summary.] <br>\n\n## Skill Version(s): <br>\n1.9.13 (source: server release metadata; artifact frontmatter reports 1.9.8) <br>\n\n## Ethical Considerations: <br>\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. <br>\n\nArchive v1.9.12: 5 files, 7515 bytes\n\nFiles: modules/exemplar-research.md (4022b), modules/language-audit.md (2375b), skill-card.md (2379b), SKILL.md (5813b), _meta.json (144b)\n\nFile v1.9.12:SKILL.md\n\n---\nname: update-readme\ndescription: Refreshes README structure and content using repo context and exemplar research\nversion: 1.9.8\ntriggers:\n  - readme\n  - documentation\n  - exemplars\n  - research\n  - structure\n  - README needs a structural update after significant project changes\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.sanctum:git-workspace-review\", \"night-market.imbue:proof-of-work\", \"night-market.scribe:slop-detector\", \"night-market.scribe:doc-generator\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# README Update Workflow\n\n## When To Use\nUse this skill whenever the README requires a structural refresh.\nRun `Skill(sanctum:git-workspace-review)` first to capture repo context and diffs.\n\n## When NOT To Use\n\n- Updating inline docs: use doc-updates\n- Consolidating ephemeral reports: use doc-consolidation\n\n## Required TodoWrite Items\n1. `update-readme:language-audit`\n2. `update-readme:exemplar-research`\n3. `update-readme:outline-aligned`\n4. `update-readme:edits-applied`\n5. `update-readme:slop-scanned` - AI marker detection via scribe\n6. `update-readme:verification-reporting`\n\n## Step 1 - Language Audit (`update-readme:language-audit`)\n- Confirm `pwd`, `git status -sb`, and the baseline branch for reference.\n- Detect dominant languages using repository heuristics (manifest files, file counts).\n- Note secondary languages that influence documentation (e.g., a TypeScript frontend and a Rust backend) so the README can surface both.\n- Record the method and findings.\n\nSee `modules/language-audit.md` for detailed detection patterns and commands.\n\n## Step 2 - Exemplar Research (`update-readme:exemplar-research`)\n- For each primary and secondary language, use web search to locate high-quality READMEs (star count, recency, maintainer activity).\n- Capture 2-3 exemplar repositories per language and summarize why each is relevant (section order, visuals, quickstart clarity, governance messaging, math exposition, etc.).\n- Store citations for every exemplar so the final summary references them explicitly.\n\nSee `modules/exemplar-research.md` for search query patterns and evaluation criteria.\n\n## Step 3 - Outline Alignment (`update-readme:outline-aligned`)\n- Compare current README headings (`rg -n '^#' README.md`) against patterns observed in exemplars.\n- Draft a target outline covering: value proposition, installation, quickstart, deeper usage/configuration, architecture/feature highlights, performance or math guarantees, documentation links, contribution/governance, roadmap/status, and licensing/security notes.\n- validate internal documents (docs/, specs/, wiki, commands/) are mapped to the relevant sections so the README anchors them with context-sensitive links.\n\n## Step 4 - Apply Edits (`update-readme:edits-applied`)\n- Implement the new structure directly in `README.md`\n  (or the specified file).\n- Follow `Skill(leyline:markdown-formatting)` conventions:\n  wrap prose at 80 chars (prefer sentence/clause boundaries),\n  blank lines around headings, ATX headings only, blank line\n  before lists, reference-style links for long URLs.\n- Maintain concise, evidence-based prose; avoid marketing fluff.\n- Add comparison tables, feature lists, or diagrams only if\n  they originate from current repository assets (no speculative\n  content).\n- When referencing algorithms or performance claims, point to\n  benchmarks or tests within the repository or documented math\n  reviews.\n\n## Step 4.5 - AI Slop Detection (`update-readme:slop-scanned`)\n\nRun `Skill(scribe:slop-detector)` on the updated README to detect AI-generated content markers.\n\n### Scribe Integration\n\nThe scribe plugin provides AI slop detection:\n\n```\nSkill(scribe:slop-detector) --target README.md\n```\n\nThis detects:\n- **Tier 1 words**: delve, tapestry, comprehensive, leveraging, etc.\n- **Phrase patterns**: \"In today's fast-paced world\", \"cannot be overstated\"\n- **Structural markers**: Excessive em dashes, bullet overuse, sentence uniformity\n- **Marketing language**: \"enterprise-ready\", \"cutting-edge\", \"seamless\"\n\n### Remediation\n\nIf slop score exceeds 2.0 (moderate), apply `Skill(scribe:doc-generator)` principles:\n\n1. Ground every claim with specifics\n2. Remove formulaic openers/closers\n3. Use numbers, commands, filenames over adjectives\n4. Balance bullets with narrative prose\n5. Show authorial perspective (trade-offs, reasoning)\n\nFor significant cleanup needs, use:\n\n```\nAgent(scribe:doc-editor) --target README.md\n```\n\n## Step 5 - Verification & Reporting (`update-readme:verification-reporting`)\n- Re-read the updated README for clarity, accessibility (section lengths, bullet balance), and accurate links.\n- Run `git diff README.md` (or the edited file) and capture snippets for the final report.\n- Summarize detected languages, exemplar sources (with citations), key structural decisions, and follow-up TODOs (e.g., add badges, upload diagrams).\n\n## Exit Criteria\n- All `TodoWrite` items are complete.\n- The README reflects a modern, language-aware structure, referencing both internal docs and external inspiration with citations.\n- Research notes and command references are captured so future reviewers can reproduce the process.\n## Troubleshooting\n\n### Common Issues\n\n**Documentation out of sync**\nRun `make docs-update` to regenerate from code\n\n**Build failures**\nCheck that all required dependencies are installed\n\n**Links broken**\nVerify relative paths in documentation files\n\nFile v1.9.12:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-sanctum-update-readme\",\n  \"version\": \"1.9.12\",\n  \"publishedAt\": 1781839159566\n}\n\nFile v1.9.12:modules/exemplar-research.md\n\n# Exemplar Research Patterns\n\nDetailed patterns for finding, evaluating, and documenting high-quality README exemplars.\n\n## Web Search Query Patterns\n\n### Language-Specific Queries\n\n```\n\"GitHub [language] README best practices\"\n\"[language] framework README examples\"\n\"[language] project README badges\"\n\"[language] library documentation structure\"\n\"awesome [language] README\"\n```\n\n### Framework/Domain-Specific Queries\n\n```\n\"[framework] README structure\"\n\"[domain] project README examples\" (e.g., \"CLI tool README examples\")\n\"[language] [project-type] documentation\" (e.g., \"Rust async library documentation\")\n```\n\n### Quality Indicators\n\n```\n\"high star count [language] README\"\n\"well-maintained [language] project README\"\n\"[language] project documentation best practices 2024\"\n```\n\n## Exemplar Evaluation Criteria\n\nAssess each candidate README using these dimensions:\n\n### Structure & Organization\n- **Section order**: Does it follow a logical progression (value → quickstart → details)?\n- **Progressive disclosure**: Are complex topics deferred until after basics?\n- **Table of contents**: Is it present and well-structured?\n- **Visual hierarchy**: Clear heading levels, spacing, readability?\n\n### Content Quality\n- **Value proposition**: Clear statement of what the project does and why it matters?\n- **Quickstart clarity**: Can a new user get started in <5 minutes?\n- **Code examples**: Are they runnable, realistic, well-commented?\n- **Installation steps**: Clear, tested, platform-aware?\n\n### Technical Communication\n- **Accuracy**: Does it match the actual codebase capabilities?\n- **Completeness**: Coverage of installation, usage, configuration, troubleshooting?\n- **Governance messaging**: Clear contribution guidelines, roadmap, support channels?\n- **Math/algorithm exposition**: For technical projects, is the theory well-explained?\n\n### Maintenance Signals\n- **Recency**: Last commit within 6 months?\n- **Star count**: Indicator of community validation (>500 stars preferred)\n- **Maintainer activity**: Active issue responses, recent releases?\n- **CI/CD badges**: Evidence of automated quality checks?\n\n## Citation Format\n\nRecord each exemplar with full attribution:\n\n```markdown\n### Exemplar: [Project Name]\n- **URL**: https://github.com/[org]/[repo]\n- **Language**: [Primary language]\n- **Stars**: [count] (as of [date])\n- **Last Updated**: [date]\n- **Relevant Patterns**:\n  - [Pattern 1]: [Description and why it's relevant]\n  - [Pattern 2]: [Description and why it's relevant]\n  - [Pattern 3]: [Description and why it's relevant]\n- **Specific Elements to Adapt**:\n  - [Element]: [How it applies to this project]\n```\n\n## Storage Recommendations\n\n### Temporary Research Notes\nStore research findings in a temporary file during the session:\n\n```bash\n# Create research notes file\ncat > /tmp/readme-research.md << 'EOF'\n# README Exemplar Research\n\n## [Language 1] Exemplars\n[Citations...]\n\n## [Language 2] Exemplars\n[Citations...]\nEOF\n```\n\n### Final Report Integration\nInclude exemplar citations in the final verification report so future maintainers can:\n- Understand the design decisions\n- Revisit the sources for updates\n- Validate the approach against current best practices\n\n## Example Multi-Language Research\n\nFor a project with Rust backend and TypeScript frontend:\n\n1. **Rust Exemplars** (2-3 projects)\n   - Focus on: CLI tool patterns, installation via cargo, feature flags, performance claims\n\n2. **TypeScript Exemplars** (2-3 projects)\n   - Focus on: npm installation, dev environment setup, API documentation, framework integration\n\n3. **Full-Stack Exemplars** (1-2 projects)\n   - Focus on: How to structure README for multiple runtimes, quickstart for both components, architecture diagrams\n\n## Quality Threshold\n\nMinimum criteria for an exemplar to be useful:\n- Must have >100 stars OR be from a recognized organization\n- README must be >200 lines (substantial content)\n- Must have been updated in the last year\n- Must demonstrate at least 3 structural patterns relevant to the target project\n\nFile v1.9.12:modules/language-audit.md\n\n# Language Audit Patterns\n\nDetailed patterns and commands for detecting project languages and their documentation implications.\n\n## Manifest File Detection\n\nCheck for language-specific manifest files to identify the primary language(s):\n\n```bash\n# Rust\nls -1 Cargo.toml 2>/dev/null\n\n# Node.js/TypeScript\nls -1 package.json 2>/dev/null\n\n# Go\nls -1 go.mod 2>/dev/null\n\n# Python\nls -1 pyproject.toml setup.py requirements.txt 2>/dev/null\n\n# Java/Kotlin\nls -1 pom.xml build.gradle build.gradle.kts 2>/dev/null\n\n# Ruby\nls -1 Gemfile 2>/dev/null\n\n# PHP\nls -1 composer.json 2>/dev/null\n```\n\n## File Count Analysis\n\nCount source files by extension to determine language distribution:\n\n```bash\n# Rust\ngit ls-files | rg '\\.rs$' | wc -l\n# or for preview\nrg --files -g '*.rs' | head -10\n\n# Python\ngit ls-files | rg '\\.py$' | wc -l\nrg --files -g '*.py' | head -10\n\n# Go\ngit ls-files | rg '\\.go$' | wc -l\nrg --files -g '*.go' | head -10\n\n# TypeScript/JavaScript\ngit ls-files | rg '\\.(ts|tsx|js|jsx)$' | wc -l\nrg --files -g '*.ts' -g '*.tsx' | head -10\n\n# Java\ngit ls-files | rg '\\.java$' | wc -l\nrg --files -g '*.java' | head -10\n```\n\n## Language Priority Heuristics\n\nDetermine primary language using these priority rules:\n\n1. **Manifest presence**: If a language-specific manifest exists, it's a strong signal\n2. **File count dominance**: Language with >60% of source files is primary\n3. **Directory structure**: Check for language-specific directories (src/, lib/, pkg/)\n4. **Build configuration**: Presence of Makefile, CMakeLists.txt, or build scripts\n\n## Secondary Language Handling\n\nDocument secondary languages when they:\n\n- Represent >20% of codebase\n- Serve distinct architectural roles (e.g., Rust backend + TypeScript frontend)\n- Have their own build/test infrastructure\n- Require separate installation or runtime considerations\n\n### Example Multi-Language Documentation Strategy\n\n```markdown\n## Installation\n\n### Backend (Rust)\n[Rust-specific instructions]\n\n### Frontend (TypeScript)\n[Node/npm-specific instructions]\n```\n\n## Recording Findings\n\nCapture the audit results in a structured format:\n\n```\nLanguage Audit Results:\n- Primary: [Language] ([count] files, [manifest])\n- Secondary: [Language] ([count] files, [manifest])\n- Method: [manifest detection | file count | directory structure]\n- Documentation implications: [single-language | multi-language sections needed]\n```\n\nFile v1.9.12:skill-card.md\n\n## Description: <br>\nRefreshes README structure and content using repo context and exemplar research. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[athola](https://clawhub.ai/user/athola) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and maintainers use this skill to refresh README structure after meaningful project changes. It audits repository languages, researches comparable README examples, aligns the outline, applies documentation edits, scans for formulaic AI prose, and reports verification details. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Documentation or agent guidance edits could affect future repository workflows and tooling behavior. <br>\nMitigation: Use report-only mode for sensitive repositories and review proposed changes to README, AGENTS, CONTRIBUTING, .agents, and .cursor files before applying them. <br>\nRisk: External README exemplar research may introduce outdated or poorly matched documentation patterns. <br>\nMitigation: Retain citations for selected exemplars, check recency and maintainer activity, and adapt only patterns that match the current repository evidence. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/athola/nm-sanctum-update-readme) <br>\n- [Publisher profile](https://clawhub.ai/user/athola) <br>\n- [OpenClaw homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum) <br>\n- [Language audit patterns](modules/language-audit.md) <br>\n- [Exemplar research patterns](modules/exemplar-research.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, shell commands, guidance] <br>\n**Output Format:** [Markdown reports, README edits, command snippets, and verification summaries] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May edit README.md or another specified documentation file; report-only review is recommended for sensitive repositories.] <br>\n\n## Skill Version(s): <br>\n1.9.12 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\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. <br>\n\nArchive v1.0.3: 5 files, 7412 bytes\n\nFiles: modules/exemplar-research.md (4022b), modules/language-audit.md (2375b), skill-card.md (2164b), SKILL.md (5813b), _meta.json (143b)\n\nFile v1.0.3:SKILL.md\n\n---\nname: update-readme\ndescription: Refreshes README structure and content using repo context and exemplar research\nversion: 1.9.8\ntriggers:\n  - readme\n  - documentation\n  - exemplars\n  - research\n  - structure\n  - README needs a structural update after significant project changes\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.sanctum:git-workspace-review\", \"night-market.imbue:proof-of-work\", \"night-market.scribe:slop-detector\", \"night-market.scribe:doc-generator\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# README Update Workflow\n\n## When To Use\nUse this skill whenever the README requires a structural refresh.\nRun `Skill(sanctum:git-workspace-review)` first to capture repo context and diffs.\n\n## When NOT To Use\n\n- Updating inline docs: use doc-updates\n- Consolidating ephemeral reports: use doc-consolidation\n\n## Required TodoWrite Items\n1. `update-readme:language-audit`\n2. `update-readme:exemplar-research`\n3. `update-readme:outline-aligned`\n4. `update-readme:edits-applied`\n5. `update-readme:slop-scanned` - AI marker detection via scribe\n6. `update-readme:verification-reporting`\n\n## Step 1 - Language Audit (`update-readme:language-audit`)\n- Confirm `pwd`, `git status -sb`, and the baseline branch for reference.\n- Detect dominant languages using repository heuristics (manifest files, file counts).\n- Note secondary languages that influence documentation (e.g., a TypeScript frontend and a Rust backend) so the README can surface both.\n- Record the method and findings.\n\nSee `modules/language-audit.md` for detailed detection patterns and commands.\n\n## Step 2 - Exemplar Research (`update-readme:exemplar-research`)\n- For each primary and secondary language, use web search to locate high-quality READMEs (star count, recency, maintainer activity).\n- Capture 2-3 exemplar repositories per language and summarize why each is relevant (section order, visuals, quickstart clarity, governance messaging, math exposition, etc.).\n- Store citations for every exemplar so the final summary references them explicitly.\n\nSee `modules/exemplar-research.md` for search query patterns and evaluation criteria.\n\n## Step 3 - Outline Alignment (`update-readme:outline-aligned`)\n- Compare current README headings (`rg -n '^#' README.md`) against patterns observed in exemplars.\n- Draft a target outline covering: value proposition, installation, quickstart, deeper usage/configuration, architecture/feature highlights, performance or math guarantees, documentation links, contribution/governance, roadmap/status, and licensing/security notes.\n- validate internal documents (docs/, specs/, wiki, commands/) are mapped to the relevant sections so the README anchors them with context-sensitive links.\n\n## Step 4 - Apply Edits (`update-readme:edits-applied`)\n- Implement the new structure directly in `README.md`\n  (or the specified file).\n- Follow `Skill(leyline:markdown-formatting)` conventions:\n  wrap prose at 80 chars (prefer sentence/clause boundaries),\n  blank lines around headings, ATX headings only, blank line\n  before lists, reference-style links for long URLs.\n- Maintain concise, evidence-based prose; avoid marketing fluff.\n- Add comparison tables, feature lists, or diagrams only if\n  they originate from current repository assets (no speculative\n  content).\n- When referencing algorithms or performance claims, point to\n  benchmarks or tests within the repository or documented math\n  reviews.\n\n## Step 4.5 - AI Slop Detection (`update-readme:slop-scanned`)\n\nRun `Skill(scribe:slop-detector)` on the updated README to detect AI-generated content markers.\n\n### Scribe Integration\n\nThe scribe plugin provides AI slop detection:\n\n```\nSkill(scribe:slop-detector) --target README.md\n```\n\nThis detects:\n- **Tier 1 words**: delve, tapestry, comprehensive, leveraging, etc.\n- **Phrase patterns**: \"In today's fast-paced world\", \"cannot be overstated\"\n- **Structural markers**: Excessive em dashes, bullet overuse, sentence uniformity\n- **Marketing language**: \"enterprise-ready\", \"cutting-edge\", \"seamless\"\n\n### Remediation\n\nIf slop score exceeds 2.0 (moderate), apply `Skill(scribe:doc-generator)` principles:\n\n1. Ground every claim with specifics\n2. Remove formulaic openers/closers\n3. Use numbers, commands, filenames over adjectives\n4. Balance bullets with narrative prose\n5. Show authorial perspective (trade-offs, reasoning)\n\nFor significant cleanup needs, use:\n\n```\nAgent(scribe:doc-editor) --target README.md\n```\n\n## Step 5 - Verification & Reporting (`update-readme:verification-reporting`)\n- Re-read the updated README for clarity, accessibility (section lengths, bullet balance), and accurate links.\n- Run `git diff README.md` (or the edited file) and capture snippets for the final report.\n- Summarize detected languages, exemplar sources (with citations), key structural decisions, and follow-up TODOs (e.g., add badges, upload diagrams).\n\n## Exit Criteria\n- All `TodoWrite` items are complete.\n- The README reflects a modern, language-aware structure, referencing both internal docs and external inspiration with citations.\n- Research notes and command references are captured so future reviewers can reproduce the process.\n## Troubleshooting\n\n### Common Issues\n\n**Documentation out of sync**\nRun `make docs-update` to regenerate from code\n\n**Build failures**\nCheck that all required dependencies are installed\n\n**Links broken**\nVerify relative paths in documentation files\n\nFile v1.0.3:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-sanctum-update-readme\",\n  \"version\": \"1.0.3\",\n  \"publishedAt\": 1781796115164\n}\n\nFile v1.0.3:modules/exemplar-research.md\n\n# Exemplar Research Patterns\n\nDetailed patterns for finding, evaluating, and documenting high-quality README exemplars.\n\n## Web Search Query Patterns\n\n### Language-Specific Queries\n\n```\n\"GitHub [language] README best practices\"\n\"[language] framework README examples\"\n\"[language] project README badges\"\n\"[language] library documentation structure\"\n\"awesome [language] README\"\n```\n\n### Framework/Domain-Specific Queries\n\n```\n\"[framework] README structure\"\n\"[domain] project README examples\" (e.g., \"CLI tool README examples\")\n\"[language] [project-type] documentation\" (e.g., \"Rust async library documentation\")\n```\n\n### Quality Indicators\n\n```\n\"high star count [language] README\"\n\"well-maintained [language] project README\"\n\"[language] project documentation best practices 2024\"\n```\n\n## Exemplar Evaluation Criteria\n\nAssess each candidate README using these dimensions:\n\n### Structure & Organization\n- **Section order**: Does it follow a logical progression (value → quickstart → details)?\n- **Progressive disclosure**: Are complex topics deferred until after basics?\n- **Table of contents**: Is it present and well-structured?\n- **Visual hierarchy**: Clear heading levels, spacing, readability?\n\n### Content Quality\n- **Value proposition**: Clear statement of what the project does and why it matters?\n- **Quickstart clarity**: Can a new user get started in <5 minutes?\n- **Code examples**: Are they runnable, realistic, well-commented?\n- **Installation steps**: Clear, tested, platform-aware?\n\n### Technical Communication\n- **Accuracy**: Does it match the actual codebase capabilities?\n- **Completeness**: Coverage of installation, usage, configuration, troubleshooting?\n- **Governance messaging**: Clear contribution guidelines, roadmap, support channels?\n- **Math/algorithm exposition**: For technical projects, is the theory well-explained?\n\n### Maintenance Signals\n- **Recency**: Last commit within 6 months?\n- **Star count**: Indicator of community validation (>500 stars preferred)\n- **Maintainer activity**: Active issue responses, recent releases?\n- **CI/CD badges**: Evidence of automated quality checks?\n\n## Citation Format\n\nRecord each exemplar with full attribution:\n\n```markdown\n### Exemplar: [Project Name]\n- **URL**: https://github.com/[org]/[repo]\n- **Language**: [Primary language]\n- **Stars**: [count] (as of [date])\n- **Last Updated**: [date]\n- **Relevant Patterns**:\n  - [Pattern 1]: [Description and why it's relevant]\n  - [Pattern 2]: [Description and why it's relevant]\n  - [Pattern 3]: [Description and why it's relevant]\n- **Specific Elements to Adapt**:\n  - [Element]: [How it applies to this project]\n```\n\n## Storage Recommendations\n\n### Temporary Research Notes\nStore research findings in a temporary file during the session:\n\n```bash\n# Create research notes file\ncat > /tmp/readme-research.md << 'EOF'\n# README Exemplar Research\n\n## [Language 1] Exemplars\n[Citations...]\n\n## [Language 2] Exemplars\n[Citations...]\nEOF\n```\n\n### Final Report Integration\nInclude exemplar citations in the final verification report so future maintainers can:\n- Understand the design decisions\n- Revisit the sources for updates\n- Validate the approach against current best practices\n\n## Example Multi-Language Research\n\nFor a project with Rust backend and TypeScript frontend:\n\n1. **Rust Exemplars** (2-3 projects)\n   - Focus on: CLI tool patterns, installation via cargo, feature flags, performance claims\n\n2. **TypeScript Exemplars** (2-3 projects)\n   - Focus on: npm installation, dev environment setup, API documentation, framework integration\n\n3. **Full-Stack Exemplars** (1-2 projects)\n   - Focus on: How to structure README for multiple runtimes, quickstart for both components, architecture diagrams\n\n## Quality Threshold\n\nMinimum criteria for an exemplar to be useful:\n- Must have >100 stars OR be from a recognized organization\n- README must be >200 lines (substantial content)\n- Must have been updated in the last year\n- Must demonstrate at least 3 structural patterns relevant to the target project\n\nFile v1.0.3:modules/language-audit.md\n\n# Language Audit Patterns\n\nDetailed patterns and commands for detecting project languages and their documentation implications.\n\n## Manifest File Detection\n\nCheck for language-specific manifest files to identify the primary language(s):\n\n```bash\n# Rust\nls -1 Cargo.toml 2>/dev/null\n\n# Node.js/TypeScript\nls -1 package.json 2>/dev/null\n\n# Go\nls -1 go.mod 2>/dev/null\n\n# Python\nls -1 pyproject.toml setup.py requirements.txt 2>/dev/null\n\n# Java/Kotlin\nls -1 pom.xml build.gradle build.gradle.kts 2>/dev/null\n\n# Ruby\nls -1 Gemfile 2>/dev/null\n\n# PHP\nls -1 composer.json 2>/dev/null\n```\n\n## File Count Analysis\n\nCount source files by extension to determine language distribution:\n\n```bash\n# Rust\ngit ls-files | rg '\\.rs$' | wc -l\n# or for preview\nrg --files -g '*.rs' | head -10\n\n# Python\ngit ls-files | rg '\\.py$' | wc -l\nrg --files -g '*.py' | head -10\n\n# Go\ngit ls-files | rg '\\.go$' | wc -l\nrg --files -g '*.go' | head -10\n\n# TypeScript/JavaScript\ngit ls-files | rg '\\.(ts|tsx|js|jsx)$' | wc -l\nrg --files -g '*.ts' -g '*.tsx' | head -10\n\n# Java\ngit ls-files | rg '\\.java$' | wc -l\nrg --files -g '*.java' | head -10\n```\n\n## Language Priority Heuristics\n\nDetermine primary language using these priority rules:\n\n1. **Manifest presence**: If a language-specific manifest exists, it's a strong signal\n2. **File count dominance**: Language with >60% of source files is primary\n3. **Directory structure**: Check for language-specific directories (src/, lib/, pkg/)\n4. **Build configuration**: Presence of Makefile, CMakeLists.txt, or build scripts\n\n## Secondary Language Handling\n\nDocument secondary languages when they:\n\n- Represent >20% of codebase\n- Serve distinct architectural roles (e.g., Rust backend + TypeScript frontend)\n- Have their own build/test infrastructure\n- Require separate installation or runtime considerations\n\n### Example Multi-Language Documentation Strategy\n\n```markdown\n## Installation\n\n### Backend (Rust)\n[Rust-specific instructions]\n\n### Frontend (TypeScript)\n[Node/npm-specific instructions]\n```\n\n## Recording Findings\n\nCapture the audit results in a structured format:\n\n```\nLanguage Audit Results:\n- Primary: [Language] ([count] files, [manifest])\n- Secondary: [Language] ([count] files, [manifest])\n- Method: [manifest detection | file count | directory structure]\n- Documentation implications: [single-language | multi-language sections needed]\n```\n\nFile v1.0.3:skill-card.md\n\n## Description: <br>\nRefreshes README structure and content using repo context and exemplar research. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[athola](https://clawhub.ai/user/athola) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and maintainers use this skill to audit repository context, research README exemplars, update README structure and content, and report verification notes. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill can update README files and may introduce inaccurate or misleading documentation if repository context is incomplete. <br>\nMitigation: Review the proposed outline, generated diff, and final README before relying on or publishing the changes. <br>\nRisk: External exemplar research can influence README structure and citations in ways that may not fit the target project. <br>\nMitigation: Verify exemplar links, keep claims grounded in current repository files, and remove unsupported comparisons or marketing language. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/athola/nm-sanctum-update-readme) <br>\n- [Project homepage from metadata](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum) <br>\n- [Language audit patterns](modules/language-audit.md) <br>\n- [Exemplar research patterns](modules/exemplar-research.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Markdown, Files, Shell commands, Guidance] <br>\n**Output Format:** [Markdown guidance with inline shell commands and direct README edits] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May include README diffs, exemplar citations, and verification notes.] <br>\n\n## Skill Version(s): <br>\n1.0.3 (source: server release metadata; artifact frontmatter reports 1.9.8) <br>\n\n## Ethical Considerations: <br>\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. <br>\n\nArchive v1.0.2: 5 files, 7448 bytes\n\nFiles: modules/exemplar-research.md (4020b), modules/language-audit.md (2375b), skill-card.md (2262b), SKILL.md (5748b), _meta.json (143b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: update-readme\ndescription: |\n  Refresh README structure and content using repo context from git-workspace-review\nversion: 1.9.5\ntriggers:\n  - readme\n  - documentation\n  - exemplars\n  - research\n  - structure\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.sanctum:git-workspace-review\", \"night-market.imbue:proof-of-work\", \"night-market.scribe:slop-detector\", \"night-market.scribe:doc-generator\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# README Update Workflow\n\n## When To Use\nUse this skill whenever the README requires a structural refresh.\nRun `Skill(sanctum:git-workspace-review)` first to capture repo context and diffs.\n\n## When NOT To Use\n\n- Updating inline docs: use doc-updates\n- Consolidating ephemeral reports: use doc-consolidation\n\n## Required TodoWrite Items\n1. `update-readme:language-audit`\n2. `update-readme:exemplar-research`\n3. `update-readme:outline-aligned`\n4. `update-readme:edits-applied`\n5. `update-readme:slop-scanned` - AI marker detection via scribe\n6. `update-readme:verification-reporting`\n\n## Step 1 - Language Audit (`update-readme:language-audit`)\n- Confirm `pwd`, `git status -sb`, and the baseline branch for reference.\n- Detect dominant languages using repository heuristics (manifest files, file counts).\n- Note secondary languages that influence documentation (e.g., a TypeScript frontend and a Rust backend) so the README can surface both.\n- Record the method and findings.\n\nSee `modules/language-audit.md` for detailed detection patterns and commands.\n\n## Step 2 - Exemplar Research (`update-readme:exemplar-research`)\n- For each primary and secondary language, use web search to locate high-quality READMEs (star count, recency, maintainer activity).\n- Capture 2-3 exemplar repositories per language and summarize why each is relevant (section order, visuals, quickstart clarity, governance messaging, math exposition, etc.).\n- Store citations for every exemplar so the final summary references them explicitly.\n\nSee `modules/exemplar-research.md` for search query patterns and evaluation criteria.\n\n## Step 3 - Outline Alignment (`update-readme:outline-aligned`)\n- Compare current README headings (`rg -n '^#' README.md`) against patterns observed in exemplars.\n- Draft a target outline covering: value proposition, installation, quickstart, deeper usage/configuration, architecture/feature highlights, performance or math guarantees, documentation links, contribution/governance, roadmap/status, and licensing/security notes.\n- validate internal documents (docs/, specs/, wiki, commands/) are mapped to the relevant sections so the README anchors them with context-sensitive links.\n\n## Step 4 - Apply Edits (`update-readme:edits-applied`)\n- Implement the new structure directly in `README.md`\n  (or the specified file).\n- Follow `Skill(leyline:markdown-formatting)` conventions:\n  wrap prose at 80 chars (prefer sentence/clause boundaries),\n  blank lines around headings, ATX headings only, blank line\n  before lists, reference-style links for long URLs.\n- Maintain concise, evidence-based prose; avoid marketing fluff.\n- Add comparison tables, feature lists, or diagrams only if\n  they originate from current repository assets (no speculative\n  content).\n- When referencing algorithms or performance claims, point to\n  benchmarks or tests within the repository or documented math\n  reviews.\n\n## Step 4.5 - AI Slop Detection (`update-readme:slop-scanned`)\n\nRun `Skill(scribe:slop-detector)` on the updated README to detect AI-generated content markers.\n\n### Scribe Integration\n\nThe scribe plugin provides AI slop detection:\n\n```\nSkill(scribe:slop-detector) --target README.md\n```\n\nThis detects:\n- **Tier 1 words**: delve, tapestry, comprehensive, leveraging, etc.\n- **Phrase patterns**: \"In today's fast-paced world\", \"cannot be overstated\"\n- **Structural markers**: Excessive em dashes, bullet overuse, sentence uniformity\n- **Marketing language**: \"enterprise-ready\", \"cutting-edge\", \"seamless\"\n\n### Remediation\n\nIf slop score exceeds 2.0 (moderate), apply `Skill(scribe:doc-generator)` principles:\n\n1. Ground every claim with specifics\n2. Remove formulaic openers/closers\n3. Use numbers, commands, filenames over adjectives\n4. Balance bullets with narrative prose\n5. Show authorial perspective (trade-offs, reasoning)\n\nFor significant cleanup needs, use:\n\n```\nAgent(scribe:doc-editor) --target README.md\n```\n\n## Step 5 - Verification & Reporting (`update-readme:verification-reporting`)\n- Re-read the updated README for clarity, accessibility (section lengths, bullet balance), and accurate links.\n- Run `git diff README.md` (or the edited file) and capture snippets for the final report.\n- Summarize detected languages, exemplar sources (with citations), key structural decisions, and follow-up TODOs (e.g., add badges, upload diagrams).\n\n## Exit Criteria\n- All `TodoWrite` items are complete.\n- The README reflects a modern, language-aware structure, referencing both internal docs and external inspiration with citations.\n- Research notes and command references are captured so future reviewers can reproduce the process.\n## Troubleshooting\n\n### Common Issues\n\n**Documentation out of sync**\nRun `make docs-update` to regenerate from code\n\n**Build failures**\nCheck that all required dependencies are installed\n\n**Links broken**\nVerify relative paths in documentation files\n\nFile v1.0.2:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-sanctum-update-readme\",\n  \"version\": \"1.0.2\",\n  \"publishedAt\": 1778293212005\n}\n\nFile v1.0.2:modules/exemplar-research.md\n\n# Exemplar Research Patterns\n\nDetailed patterns for finding, evaluating, and documenting high-quality README exemplars.\n\n## Web Search Query Patterns\n\n### Language-Specific Queries\n\n```\n\"GitHub [language] README best practices\"\n\"[language] framework README examples\"\n\"[language] project README badges\"\n\"[language] library documentation structure\"\n\"awesome [language] README\"\n```\n\n### Framework/Domain-Specific Queries\n\n```\n\"[framework] README structure\"\n\"[domain] project README examples\" (e.g., \"CLI tool README examples\")\n\"[language] [project-type] documentation\" (e.g., \"Rust async library documentation\")\n```\n\n### Quality Indicators\n\n```\n\"high star count [language] README\"\n\"well-maintained [language] project README\"\n\"[language] project documentation best practices 2024\"\n```\n\n## Exemplar Evaluation Criteria\n\nAssess each candidate README using these dimensions:\n\n### Structure & Organization\n- **Section order**: Does it follow a logical progression (value → quickstart → details)?\n- **Progressive disclosure**: Are complex topics deferred until after basics?\n- **Table of contents**: Is it present and well-structured?\n- **Visual hierarchy**: Clear heading levels, spacing, readability?\n\n### Content Quality\n- **Value proposition**: Clear statement of what the project does and why it matters?\n- **Quickstart clarity**: Can a new user get started in <5 minutes?\n- **Code examples**: Are they runnable, realistic, well-commented?\n- **Installation steps**: Clear, tested, platform-aware?\n\n### Technical Communication\n- **Accuracy**: Does it match the actual codebase capabilities?\n- **Completeness**: Coverage of installation, usage, configuration, troubleshooting?\n- **Governance messaging**: Clear contribution guidelines, roadmap, support channels?\n- **Math/algorithm exposition**: For technical projects, is the theory well-explained?\n\n### Maintenance Signals\n- **Recency**: Last commit within 6 months?\n- **Star count**: Indicator of community validation (>500 stars preferred)\n- **Maintainer activity**: Active issue responses, recent releases?\n- **CI/CD badges**: Evidence of automated quality checks?\n\n## Citation Format\n\nRecord each exemplar with full attribution:\n\n```markdown\n### Exemplar: [Project Name]\n- **URL**: https://github.com/[org]/[repo]\n- **Language**: [Primary language]\n- **Stars**: [count] (as of [date])\n- **Last Updated**: [date]\n- **Relevant Patterns**:\n  - [Pattern 1]: [Description and why it's relevant]\n  - [Pattern 2]: [Description and why it's relevant]\n  - [Pattern 3]: [Description and why it's relevant]\n- **Specific Elements to Adapt**:\n  - [Element]: [How it applies to this project]\n```\n\n## Storage Recommendations\n\n### Temporary Research Notes\nStore research findings in a temporary file during the session:\n\n```bash\n# Create research notes file\ncat > /tmp/readme-research.md << 'EOF'\n# README Exemplar Research\n\n## [Language 1] Exemplars\n[Citations...]\n\n## [Language 2] Exemplars\n[Citations...]\nEOF\n```\n\n### Final Report Integration\nInclude exemplar citations in the final verification report so future maintainers can:\n- Understand the design decisions\n- Revisit the sources for updates\n- Validate the approach against current best practices\n\n## Example Multi-Language Research\n\nFor a project with Rust backend + TypeScript frontend:\n\n1. **Rust Exemplars** (2-3 projects)\n   - Focus on: CLI tool patterns, installation via cargo, feature flags, performance claims\n\n2. **TypeScript Exemplars** (2-3 projects)\n   - Focus on: npm installation, dev environment setup, API documentation, framework integration\n\n3. **Full-Stack Exemplars** (1-2 projects)\n   - Focus on: How to structure README for multiple runtimes, quickstart for both components, architecture diagrams\n\n## Quality Threshold\n\nMinimum criteria for an exemplar to be useful:\n- Must have >100 stars OR be from a recognized organization\n- README must be >200 lines (substantial content)\n- Must have been updated in the last year\n- Must demonstrate at least 3 structural patterns relevant to the target project\n\nFile v1.0.2:modules/language-audit.md\n\n# Language Audit Patterns\n\nDetailed patterns and commands for detecting project languages and their documentation implications.\n\n## Manifest File Detection\n\nCheck for language-specific manifest files to identify the primary language(s):\n\n```bash\n# Rust\nls -1 Cargo.toml 2>/dev/null\n\n# Node.js/TypeScript\nls -1 package.json 2>/dev/null\n\n# Go\nls -1 go.mod 2>/dev/null\n\n# Python\nls -1 pyproject.toml setup.py requirements.txt 2>/dev/null\n\n# Java/Kotlin\nls -1 pom.xml build.gradle build.gradle.kts 2>/dev/null\n\n# Ruby\nls -1 Gemfile 2>/dev/null\n\n# PHP\nls -1 composer.json 2>/dev/null\n```\n\n## File Count Analysis\n\nCount source files by extension to determine language distribution:\n\n```bash\n# Rust\ngit ls-files | rg '\\.rs$' | wc -l\n# or for preview\nrg --files -g '*.rs' | head -10\n\n# Python\ngit ls-files | rg '\\.py$' | wc -l\nrg --files -g '*.py' | head -10\n\n# Go\ngit ls-files | rg '\\.go$' | wc -l\nrg --files -g '*.go' | head -10\n\n# TypeScript/JavaScript\ngit ls-files | rg '\\.(ts|tsx|js|jsx)$' | wc -l\nrg --files -g '*.ts' -g '*.tsx' | head -10\n\n# Java\ngit ls-files | rg '\\.java$' | wc -l\nrg --files -g '*.java' | head -10\n```\n\n## Language Priority Heuristics\n\nDetermine primary language using these priority rules:\n\n1. **Manifest presence**: If a language-specific manifest exists, it's a strong signal\n2. **File count dominance**: Language with >60% of source files is primary\n3. **Directory structure**: Check for language-specific directories (src/, lib/, pkg/)\n4. **Build configuration**: Presence of Makefile, CMakeLists.txt, or build scripts\n\n## Secondary Language Handling\n\nDocument secondary languages when they:\n\n- Represent >20% of codebase\n- Serve distinct architectural roles (e.g., Rust backend + TypeScript frontend)\n- Have their own build/test infrastructure\n- Require separate installation or runtime considerations\n\n### Example Multi-Language Documentation Strategy\n\n```markdown\n## Installation\n\n### Backend (Rust)\n[Rust-specific instructions]\n\n### Frontend (TypeScript)\n[Node/npm-specific instructions]\n```\n\n## Recording Findings\n\nCapture the audit results in a structured format:\n\n```\nLanguage Audit Results:\n- Primary: [Language] ([count] files, [manifest])\n- Secondary: [Language] ([count] files, [manifest])\n- Method: [manifest detection | file count | directory structure]\n- Documentation implications: [single-language | multi-language sections needed]\n```\n\nFile v1.0.2:skill-card.md\n\n## Description: <br>\nRefresh README structure and content using repo context from git-workspace-review. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[athola](https://clawhub.ai/user/athola) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and documentation maintainers use this skill to audit a repository, research README examples, restructure README content, and report the resulting documentation changes. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: README edits may introduce inaccurate, outdated, or misleading project guidance. <br>\nMitigation: Review the README diff, verify links and claims against repository evidence, and approve changes before committing. <br>\nRisk: Optional project commands may run untrusted repository automation. <br>\nMitigation: Inspect commands such as make docs-update before execution, especially in unfamiliar repositories. <br>\nRisk: Referenced helper skills or agents may add behavior outside this skill's artifact. <br>\nMitigation: Review and approve helper skills or agents separately before relying on them. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill listing](https://clawhub.ai/athola/nm-sanctum-update-readme) <br>\n- [Clawdis homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum) <br>\n- [Exemplar research patterns](modules/exemplar-research.md) <br>\n- [Language audit patterns](modules/language-audit.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, shell commands, guidance] <br>\n**Output Format:** [Markdown documentation edits with concise command summaries and citation notes] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Produces README-focused analysis, edits, and verification reporting for human review.] <br>\n\n## Skill Version(s): <br>\n1.0.2 (source: ClawHub release metadata; source skill frontmatter: 1.9.5) <br>\n\n## Ethical Considerations: <br>\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. <br>\n\nArchive v1.0.1: 4 files, 6249 bytes\n\nFiles: modules/exemplar-research.md (4020b), modules/language-audit.md (2375b), SKILL.md (5748b), _meta.json (143b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: update-readme\ndescription: |\n  Refresh README structure and content using repo context from git-workspace-review\nversion: 1.9.4\ntriggers:\n  - readme\n  - documentation\n  - exemplars\n  - research\n  - structure\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.sanctum:git-workspace-review\", \"night-market.imbue:proof-of-work\", \"night-market.scribe:slop-detector\", \"night-market.scribe:doc-generator\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# README Update Workflow\n\n## When To Use\nUse this skill whenever the README requires a structural refresh.\nRun `Skill(sanctum:git-workspace-review)` first to capture repo context and diffs.\n\n## When NOT To Use\n\n- Updating inline docs: use doc-updates\n- Consolidating ephemeral reports: use doc-consolidation\n\n## Required TodoWrite Items\n1. `update-readme:language-audit`\n2. `update-readme:exemplar-research`\n3. `update-readme:outline-aligned`\n4. `update-readme:edits-applied`\n5. `update-readme:slop-scanned` - AI marker detection via scribe\n6. `update-readme:verification-reporting`\n\n## Step 1 - Language Audit (`update-readme:language-audit`)\n- Confirm `pwd`, `git status -sb`, and the baseline branch for reference.\n- Detect dominant languages using repository heuristics (manifest files, file counts).\n- Note secondary languages that influence documentation (e.g., a TypeScript frontend and a Rust backend) so the README can surface both.\n- Record the method and findings.\n\nSee `modules/language-audit.md` for detailed detection patterns and commands.\n\n## Step 2 - Exemplar Research (`update-readme:exemplar-research`)\n- For each primary and secondary language, use web search to locate high-quality READMEs (star count, recency, maintainer activity).\n- Capture 2-3 exemplar repositories per language and summarize why each is relevant (section order, visuals, quickstart clarity, governance messaging, math exposition, etc.).\n- Store citations for every exemplar so the final summary references them explicitly.\n\nSee `modules/exemplar-research.md` for search query patterns and evaluation criteria.\n\n## Step 3 - Outline Alignment (`update-readme:outline-aligned`)\n- Compare current README headings (`rg -n '^#' README.md`) against patterns observed in exemplars.\n- Draft a target outline covering: value proposition, installation, quickstart, deeper usage/configuration, architecture/feature highlights, performance or math guarantees, documentation links, contribution/governance, roadmap/status, and licensing/security notes.\n- validate internal documents (docs/, specs/, wiki, commands/) are mapped to the relevant sections so the README anchors them with context-sensitive links.\n\n## Step 4 - Apply Edits (`update-readme:edits-applied`)\n- Implement the new structure directly in `README.md`\n  (or the specified file).\n- Follow `Skill(leyline:markdown-formatting)` conventions:\n  wrap prose at 80 chars (prefer sentence/clause boundaries),\n  blank lines around headings, ATX headings only, blank line\n  before lists, reference-style links for long URLs.\n- Maintain concise, evidence-based prose; avoid marketing fluff.\n- Add comparison tables, feature lists, or diagrams only if\n  they originate from current repository assets (no speculative\n  content).\n- When referencing algorithms or performance claims, point to\n  benchmarks or tests within the repository or documented math\n  reviews.\n\n## Step 4.5 - AI Slop Detection (`update-readme:slop-scanned`)\n\nRun `Skill(scribe:slop-detector)` on the updated README to detect AI-generated content markers.\n\n### Scribe Integration\n\nThe scribe plugin provides AI slop detection:\n\n```\nSkill(scribe:slop-detector) --target README.md\n```\n\nThis detects:\n- **Tier 1 words**: delve, tapestry, comprehensive, leveraging, etc.\n- **Phrase patterns**: \"In today's fast-paced world\", \"cannot be overstated\"\n- **Structural markers**: Excessive em dashes, bullet overuse, sentence uniformity\n- **Marketing language**: \"enterprise-ready\", \"cutting-edge\", \"seamless\"\n\n### Remediation\n\nIf slop score exceeds 2.0 (moderate), apply `Skill(scribe:doc-generator)` principles:\n\n1. Ground every claim with specifics\n2. Remove formulaic openers/closers\n3. Use numbers, commands, filenames over adjectives\n4. Balance bullets with narrative prose\n5. Show authorial perspective (trade-offs, reasoning)\n\nFor significant cleanup needs, use:\n\n```\nAgent(scribe:doc-editor) --target README.md\n```\n\n## Step 5 - Verification & Reporting (`update-readme:verification-reporting`)\n- Re-read the updated README for clarity, accessibility (section lengths, bullet balance), and accurate links.\n- Run `git diff README.md` (or the edited file) and capture snippets for the final report.\n- Summarize detected languages, exemplar sources (with citations), key structural decisions, and follow-up TODOs (e.g., add badges, upload diagrams).\n\n## Exit Criteria\n- All `TodoWrite` items are complete.\n- The README reflects a modern, language-aware structure, referencing both internal docs and external inspiration with citations.\n- Research notes and command references are captured so future reviewers can reproduce the process.\n## Troubleshooting\n\n### Common Issues\n\n**Documentation out of sync**\nRun `make docs-update` to regenerate from code\n\n**Build failures**\nCheck that all required dependencies are installed\n\n**Links broken**\nVerify relative paths in documentation files\n\nFile v1.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-sanctum-update-readme\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1778077297994\n}\n\nFile v1.0.1:modules/exemplar-research.md\n\n# Exemplar Research Patterns\n\nDetailed patterns for finding, evaluating, and documenting high-quality README exemplars.\n\n## Web Search Query Patterns\n\n### Language-Specific Queries\n\n```\n\"GitHub [language] README best practices\"\n\"[language] framework README examples\"\n\"[language] project README badges\"\n\"[language] library documentation structure\"\n\"awesome [language] README\"\n```\n\n### Framework/Domain-Specific Queries\n\n```\n\"[framework] README structure\"\n\"[domain] project README examples\" (e.g., \"CLI tool README examples\")\n\"[language] [project-type] documentation\" (e.g., \"Rust async library documentation\")\n```\n\n### Quality Indicators\n\n```\n\"high star count [language] README\"\n\"well-maintained [language] project README\"\n\"[language] project documentation best practices 2024\"\n```\n\n## Exemplar Evaluation Criteria\n\nAssess each candidate README using these dimensions:\n\n### Structure & Organization\n- **Section order**: Does it follow a logical progression (value → quickstart → details)?\n- **Progressive disclosure**: Are complex topics deferred until after basics?\n- **Table of contents**: Is it present and well-structured?\n- **Visual hierarchy**: Clear heading levels, spacing, readability?\n\n### Content Quality\n- **Value proposition**: Clear statement of what the project does and why it matters?\n- **Quickstart clarity**: Can a new user get started in <5 minutes?\n- **Code examples**: Are they runnable, realistic, well-commented?\n- **Installation steps**: Clear, tested, platform-aware?\n\n### Technical Communication\n- **Accuracy**: Does it match the actual codebase capabilities?\n- **Completeness**: Coverage of installation, usage, configuration, troubleshooting?\n- **Governance messaging**: Clear contribution guidelines, roadmap, support channels?\n- **Math/algorithm exposition**: For technical projects, is the theory well-explained?\n\n### Maintenance Signals\n- **Recency**: Last commit within 6 months?\n- **Star count**: Indicator of community validation (>500 stars preferred)\n- **Maintainer activity**: Active issue responses, recent releases?\n- **CI/CD badges**: Evidence of automated quality checks?\n\n## Citation Format\n\nRecord each exemplar with full attribution:\n\n```markdown\n### Exemplar: [Project Name]\n- **URL**: https://github.com/[org]/[repo]\n- **Language**: [Primary language]\n- **Stars**: [count] (as of [date])\n- **Last Updated**: [date]\n- **Relevant Patterns**:\n  - [Pattern 1]: [Description and why it's relevant]\n  - [Pattern 2]: [Description and why it's relevant]\n  - [Pattern 3]: [Description and why it's relevant]\n- **Specific Elements to Adapt**:\n  - [Element]: [How it applies to this project]\n```\n\n## Storage Recommendations\n\n### Temporary Research Notes\nStore research findings in a temporary file during the session:\n\n```bash\n# Create research notes file\ncat > /tmp/readme-research.md << 'EOF'\n# README Exemplar Research\n\n## [Language 1] Exemplars\n[Citations...]\n\n## [Language 2] Exemplars\n[Citations...]\nEOF\n```\n\n### Final Report Integration\nInclude exemplar citations in the final verification report so future maintainers can:\n- Understand the design decisions\n- Revisit the sources for updates\n- Validate the approach against current best practices\n\n## Example Multi-Language Research\n\nFor a project with Rust backend + TypeScript frontend:\n\n1. **Rust Exemplars** (2-3 projects)\n   - Focus on: CLI tool patterns, installation via cargo, feature flags, performance claims\n\n2. **TypeScript Exemplars** (2-3 projects)\n   - Focus on: npm installation, dev environment setup, API documentation, framework integration\n\n3. **Full-Stack Exemplars** (1-2 projects)\n   - Focus on: How to structure README for multiple runtimes, quickstart for both components, architecture diagrams\n\n## Quality Threshold\n\nMinimum criteria for an exemplar to be useful:\n- Must have >100 stars OR be from a recognized organization\n- README must be >200 lines (substantial content)\n- Must have been updated in the last year\n- Must demonstrate at least 3 structural patterns relevant to the target project\n\nFile v1.0.1:modules/language-audit.md\n\n# Language Audit Patterns\n\nDetailed patterns and commands for detecting project languages and their documentation implications.\n\n## Manifest File Detection\n\nCheck for language-specific manifest files to identify the primary language(s):\n\n```bash\n# Rust\nls -1 Cargo.toml 2>/dev/null\n\n# Node.js/TypeScript\nls -1 package.json 2>/dev/null\n\n# Go\nls -1 go.mod 2>/dev/null\n\n# Python\nls -1 pyproject.toml setup.py requirements.txt 2>/dev/null\n\n# Java/Kotlin\nls -1 pom.xml build.gradle build.gradle.kts 2>/dev/null\n\n# Ruby\nls -1 Gemfile 2>/dev/null\n\n# PHP\nls -1 composer.json 2>/dev/null\n```\n\n## File Count Analysis\n\nCount source files by extension to determine language distribution:\n\n```bash\n# Rust\ngit ls-files | rg '\\.rs$' | wc -l\n# or for preview\nrg --files -g '*.rs' | head -10\n\n# Python\ngit ls-files | rg '\\.py$' | wc -l\nrg --files -g '*.py' | head -10\n\n# Go\ngit ls-files | rg '\\.go$' | wc -l\nrg --files -g '*.go' | head -10\n\n# TypeScript/JavaScript\ngit ls-files | rg '\\.(ts|tsx|js|jsx)$' | wc -l\nrg --files -g '*.ts' -g '*.tsx' | head -10\n\n# Java\ngit ls-files | rg '\\.java$' | wc -l\nrg --files -g '*.java' | head -10\n```\n\n## Language Priority Heuristics\n\nDetermine primary language using these priority rules:\n\n1. **Manifest presence**: If a language-specific manifest exists, it's a strong signal\n2. **File count dominance**: Language with >60% of source files is primary\n3. **Directory structure**: Check for language-specific directories (src/, lib/, pkg/)\n4. **Build configuration**: Presence of Makefile, CMakeLists.txt, or build scripts\n\n## Secondary Language Handling\n\nDocument secondary languages when they:\n\n- Represent >20% of codebase\n- Serve distinct architectural roles (e.g., Rust backend + TypeScript frontend)\n- Have their own build/test infrastructure\n- Require separate installation or runtime considerations\n\n### Example Multi-Language Documentation Strategy\n\n```markdown\n## Installation\n\n### Backend (Rust)\n[Rust-specific instructions]\n\n### Frontend (TypeScript)\n[Node/npm-specific instructions]\n```\n\n## Recording Findings\n\nCapture the audit results in a structured format:\n\n```\nLanguage Audit Results:\n- Primary: [Language] ([count] files, [manifest])\n- Secondary: [Language] ([count] files, [manifest])\n- Method: [manifest detection | file count | directory structure]\n- Documentation implications: [single-language | multi-language sections needed]\n```\n\nArchive v1.0.0: 4 files, 6250 bytes\n\nFiles: modules/exemplar-research.md (4020b), modules/language-audit.md (2375b), SKILL.md (5748b), _meta.json (143b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: update-readme\ndescription: |\n  Refresh README structure and content using repo context from git-workspace-review\nversion: 1.8.2\ntriggers:\n  - readme\n  - documentation\n  - exemplars\n  - research\n  - structure\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.sanctum:git-workspace-review\", \"night-market.imbue:proof-of-work\", \"night-market.scribe:slop-detector\", \"night-market.scribe:doc-generator\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# README Update Workflow\n\n## When To Use\nUse this skill whenever the README requires a structural refresh.\nRun `Skill(sanctum:git-workspace-review)` first to capture repo context and diffs.\n\n## When NOT To Use\n\n- Updating inline docs: use doc-updates\n- Consolidating ephemeral reports: use doc-consolidation\n\n## Required TodoWrite Items\n1. `update-readme:language-audit`\n2. `update-readme:exemplar-research`\n3. `update-readme:outline-aligned`\n4. `update-readme:edits-applied`\n5. `update-readme:slop-scanned` - AI marker detection via scribe\n6. `update-readme:verification-reporting`\n\n## Step 1 - Language Audit (`update-readme:language-audit`)\n- Confirm `pwd`, `git status -sb`, and the baseline branch for reference.\n- Detect dominant languages using repository heuristics (manifest files, file counts).\n- Note secondary languages that influence documentation (e.g., a TypeScript frontend and a Rust backend) so the README can surface both.\n- Record the method and findings.\n\nSee `modules/language-audit.md` for detailed detection patterns and commands.\n\n## Step 2 - Exemplar Research (`update-readme:exemplar-research`)\n- For each primary and secondary language, use web search to locate high-quality READMEs (star count, recency, maintainer activity).\n- Capture 2-3 exemplar repositories per language and summarize why each is relevant (section order, visuals, quickstart clarity, governance messaging, math exposition, etc.).\n- Store citations for every exemplar so the final summary references them explicitly.\n\nSee `modules/exemplar-research.md` for search query patterns and evaluation criteria.\n\n## Step 3 - Outline Alignment (`update-readme:outline-aligned`)\n- Compare current README headings (`rg -n '^#' README.md`) against patterns observed in exemplars.\n- Draft a target outline covering: value proposition, installation, quickstart, deeper usage/configuration, architecture/feature highlights, performance or math guarantees, documentation links, contribution/governance, roadmap/status, and licensing/security notes.\n- validate internal documents (docs/, specs/, wiki, commands/) are mapped to the relevant sections so the README anchors them with context-sensitive links.\n\n## Step 4 - Apply Edits (`update-readme:edits-applied`)\n- Implement the new structure directly in `README.md`\n  (or the specified file).\n- Follow `Skill(leyline:markdown-formatting)` conventions:\n  wrap prose at 80 chars (prefer sentence/clause boundaries),\n  blank lines around headings, ATX headings only, blank line\n  before lists, reference-style links for long URLs.\n- Maintain concise, evidence-based prose; avoid marketing fluff.\n- Add comparison tables, feature lists, or diagrams only if\n  they originate from current repository assets (no speculative\n  content).\n- When referencing algorithms or performance claims, point to\n  benchmarks or tests within the repository or documented math\n  reviews.\n\n## Step 4.5 - AI Slop Detection (`update-readme:slop-scanned`)\n\nRun `Skill(scribe:slop-detector)` on the updated README to detect AI-generated content markers.\n\n### Scribe Integration\n\nThe scribe plugin provides AI slop detection:\n\n```\nSkill(scribe:slop-detector) --target README.md\n```\n\nThis detects:\n- **Tier 1 words**: delve, tapestry, comprehensive, leveraging, etc.\n- **Phrase patterns**: \"In today's fast-paced world\", \"cannot be overstated\"\n- **Structural markers**: Excessive em dashes, bullet overuse, sentence uniformity\n- **Marketing language**: \"enterprise-ready\", \"cutting-edge\", \"seamless\"\n\n### Remediation\n\nIf slop score exceeds 2.0 (moderate), apply `Skill(scribe:doc-generator)` principles:\n\n1. Ground every claim with specifics\n2. Remove formulaic openers/closers\n3. Use numbers, commands, filenames over adjectives\n4. Balance bullets with narrative prose\n5. Show authorial perspective (trade-offs, reasoning)\n\nFor significant cleanup needs, use:\n\n```\nAgent(scribe:doc-editor) --target README.md\n```\n\n## Step 5 - Verification & Reporting (`update-readme:verification-reporting`)\n- Re-read the updated README for clarity, accessibility (section lengths, bullet balance), and accurate links.\n- Run `git diff README.md` (or the edited file) and capture snippets for the final report.\n- Summarize detected languages, exemplar sources (with citations), key structural decisions, and follow-up TODOs (e.g., add badges, upload diagrams).\n\n## Exit Criteria\n- All `TodoWrite` items are complete.\n- The README reflects a modern, language-aware structure, referencing both internal docs and external inspiration with citations.\n- Research notes and command references are captured so future reviewers can reproduce the process.\n## Troubleshooting\n\n### Common Issues\n\n**Documentation out of sync**\nRun `make docs-update` to regenerate from code\n\n**Build failures**\nCheck that all required dependencies are installed\n\n**Links broken**\nVerify relative paths in documentation files\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-sanctum-update-readme\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1776686506848\n}\n\nFile v1.0.0:modules/exemplar-research.md\n\n# Exemplar Research Patterns\n\nDetailed patterns for finding, evaluating, and documenting high-quality README exemplars.\n\n## Web Search Query Patterns\n\n### Language-Specific Queries\n\n```\n\"GitHub [language] README best practices\"\n\"[language] framework README examples\"\n\"[language] project README badges\"\n\"[language] library documentation structure\"\n\"awesome [language] README\"\n```\n\n### Framework/Domain-Specific Queries\n\n```\n\"[framework] README structure\"\n\"[domain] project README examples\" (e.g., \"CLI tool README examples\")\n\"[language] [project-type] documentation\" (e.g., \"Rust async library documentation\")\n```\n\n### Quality Indicators\n\n```\n\"high star count [language] README\"\n\"well-maintained [language] project README\"\n\"[language] project documentation best practices 2024\"\n```\n\n## Exemplar Evaluation Criteria\n\nAssess each candidate README using these dimensions:\n\n### Structure & Organization\n- **Section order**: Does it follow a logical progression (value → quickstart → details)?\n- **Progressive disclosure**: Are complex topics deferred until after basics?\n- **Table of contents**: Is it present and well-structured?\n- **Visual hierarchy**: Clear heading levels, spacing, readability?\n\n### Content Quality\n- **Value proposition**: Clear statement of what the project does and why it matters?\n- **Quickstart clarity**: Can a new user get started in <5 minutes?\n- **Code examples**: Are they runnable, realistic, well-commented?\n- **Installation steps**: Clear, tested, platform-aware?\n\n### Technical Communication\n- **Accuracy**: Does it match the actual codebase capabilities?\n- **Completeness**: Coverage of installation, usage, configuration, troubleshooting?\n- **Governance messaging**: Clear contribution guidelines, roadmap, support channels?\n- **Math/algorithm exposition**: For technical projects, is the theory well-explained?\n\n### Maintenance Signals\n- **Recency**: Last commit within 6 months?\n- **Star count**: Indicator of community validation (>500 stars preferred)\n- **Maintainer activity**: Active issue responses, recent releases?\n- **CI/CD badges**: Evidence of automated quality checks?\n\n## Citation Format\n\nRecord each exemplar with full attribution:\n\n```markdown\n### Exemplar: [Project Name]\n- **URL**: https://github.com/[org]/[repo]\n- **Language**: [Primary language]\n- **Stars**: [count] (as of [date])\n- **Last Updated**: [date]\n- **Relevant Patterns**:\n  - [Pattern 1]: [Description and why it's relevant]\n  - [Pattern 2]: [Description and why it's relevant]\n  - [Pattern 3]: [Description and why it's relevant]\n- **Specific Elements to Adapt**:\n  - [Element]: [How it applies to this project]\n```\n\n## Storage Recommendations\n\n### Temporary Research Notes\nStore research findings in a temporary file during the session:\n\n```bash\n# Create research notes file\ncat > /tmp/readme-research.md << 'EOF'\n# README Exemplar Research\n\n## [Language 1] Exemplars\n[Citations...]\n\n## [Language 2] Exemplars\n[Citations...]\nEOF\n```\n\n### Final Report Integration\nInclude exemplar citations in the final verification report so future maintainers can:\n- Understand the design decisions\n- Revisit the sources for updates\n- Validate the approach against current best practices\n\n## Example Multi-Language Research\n\nFor a project with Rust backend + TypeScript frontend:\n\n1. **Rust Exemplars** (2-3 projects)\n   - Focus on: CLI tool patterns, installation via cargo, feature flags, performance claims\n\n2. **TypeScript Exemplars** (2-3 projects)\n   - Focus on: npm installation, dev environment setup, API documentation, framework integration\n\n3. **Full-Stack Exemplars** (1-2 projects)\n   - Focus on: How to structure README for multiple runtimes, quickstart for both components, architecture diagrams\n\n## Quality Threshold\n\nMinimum criteria for an exemplar to be useful:\n- Must have >100 stars OR be from a recognized organization\n- README must be >200 lines (substantial content)\n- Must have been updated in the last year\n- Must demonstrate at least 3 structural patterns relevant to the target project\n\nFile v1.0.0:modules/language-audit.md\n\n# Language Audit Patterns\n\nDetailed patterns and commands for detecting project languages and their documentation implications.\n\n## Manifest File Detection\n\nCheck for language-specific manifest files to identify the primary language(s):\n\n```bash\n# Rust\nls -1 Cargo.toml 2>/dev/null\n\n# Node.js/TypeScript\nls -1 package.json 2>/dev/null\n\n# Go\nls -1 go.mod 2>/dev/null\n\n# Python\nls -1 pyproject.toml setup.py requirements.txt 2>/dev/null\n\n# Java/Kotlin\nls -1 pom.xml build.gradle build.gradle.kts 2>/dev/null\n\n# Ruby\nls -1 Gemfile 2>/dev/null\n\n# PHP\nls -1 composer.json 2>/dev/null\n```\n\n## File Count Analysis\n\nCount source files by extension to determine language distribution:\n\n```bash\n# Rust\ngit ls-files | rg '\\.rs$' | wc -l\n# or for preview\nrg --files -g '*.rs' | head -10\n\n# Python\ngit ls-files | rg '\\.py$' | wc -l\nrg --files -g '*.py' | head -10\n\n# Go\ngit ls-files | rg '\\.go$' | wc -l\nrg --files -g '*.go' | head -10\n\n# TypeScript/JavaScript\ngit ls-files | rg '\\.(ts|tsx|js|jsx)$' | wc -l\nrg --files -g '*.ts' -g '*.tsx' | head -10\n\n# Java\ngit ls-files | rg '\\.java$' | wc -l\nrg --files -g '*.java' | head -10\n```\n\n## Language Priority Heuristics\n\nDetermine primary language using these priority rules:\n\n1. **Manifest presence**: If a language-specific manifest exists, it'","readmeExcerpt":"Skill: update-readme Owner: athola Summary: Refreshes README structure and content using repo context and exemplar research Tags: latest:1.9.19 Version history: v1.9.19 | 2026-08-26T13:21:22.309Z | user Release v1.9.19 v1.9.17 | 2026-07-30T05:41:22.501Z | user Release v1.9.17 v1.9.16 | 2026-07-14T19:58:10.077Z | user Release v1.9.16 v1.9.14 | 2026-06-30T18:05:59.607Z | user Release v1.9.14 v1.9.13 | 2026-06-27T16:23:","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"Skill(scribe:slop-detector) --target README.md"},{"language":"text","snippet":"Agent(scribe:doc-editor) --target README.md"},{"language":"text","snippet":"\"GitHub [language] README best practices\"\n\"[language] framework README examples\"\n\"[language] project README badges\"\n\"[language] library documentation structure\"\n\"awesome [language] README\""},{"language":"text","snippet":"\"[framework] README structure\"\n\"[domain] project README examples\" (e.g., \"CLI tool README examples\")\n\"[language] [project-type] documentation\" (e.g., \"Rust async library documentation\")"},{"language":"text","snippet":"\"high star count [language] README\"\n\"well-maintained [language] project README\"\n\"[language] project documentation best practices 2024\""},{"language":"markdown","snippet":"### Exemplar: [Project Name]\n- **URL**: https://github.com/[org]/[repo]\n- **Language**: [Primary language]\n- **Stars**: [count] (as of [date])\n- **Last Updated**: [date]\n- **Relevant Patterns**:\n  - [Pattern 1]: [Description and why it's relevant]\n  - [Pattern 2]: [Description and why it's relevant]\n  - [Pattern 3]: [Description and why it's relevant]\n- **Specific Elements to Adapt**:\n  - [Element]: [How it applies to this project]"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: update-readme\ndescription: Refreshes README structure and content using repo context and exemplar research\nversion: 1.9.8\ntriggers:\n  - readme\n  - documentation\n  - exemplars\n  - research\n  - structure\n  - README needs a structural update after significant project changes\nmetadata: {\"openclaw\": {\"homepage\": \"https://github.com/athola/claude-night-market/tree/master/plugins/sanctum\", \"emoji\": \"\\ud83e\\udd9e\", \"requires\": {\"config\": [\"night-market.sanctum:shared\", \"night-market.sanctum:git-workspace-review\", \"night-market.imbue:proof-of-work\", \"night-market.scribe:slop-detector\", \"night-market.scribe:doc-generator\"]}}}\nsource: claude-night-market\nsource_plugin: sanctum\n---\n\n> **Night Market Skill** — ported from [claude-night-market/sanctum](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum). For the full experience with agents, hooks, and commands, install the Claude Code plugin.\n\n\n# README Update Workflow\n\n## When To Use\nUse this skill whenever the README requires a structural refresh.\nRun `Skill(sanctum:git-workspace-review)` first to capture repo context and diffs.\n\n## When NOT To Use\n\n- Updating inline docs: use doc-updates\n- Consolidating ephemeral reports: use doc-consolidation\n\n## Required TodoWrite Items\n1. `update-readme:language-audit`\n2. `update-readme:exemplar-research`\n3. `update-readme:outline-aligned`\n4. `update-readme:edits-applied`\n5. `update-readme:slop-scanned` - AI marker detection via scribe\n6. `update-readme:verification-reporting`\n\n## Step 1 - Language Audit (`update-readme:language-audit`)\n- Confirm `pwd`, `git status -sb`, and the baseline branch for reference.\n- Detect dominant languages using repository heuristics (manifest files, file counts).\n- Note secondary languages that influence documentation (e.g., a TypeScript frontend and a Rust backend) so the README can surface both.\n- Record the method and findings.\n\nSee `modules/language-audit.md` for detailed detection patterns and commands.\n\n## Step 2 - Exemplar Research (`update-readme:exemplar-research`)\n- For each primary and secondary language, use web search to locate high-quality READMEs (star count, recency, maintainer activity).\n- Capture 2-3 exemplar repositories per language and summarize why each is relevant (section order, visuals, quickstart clarity, governance messaging, math exposition, etc.).\n- Store citations for every exemplar so the final summary references them explicitly.\n\nSee `modules/exemplar-research.md` for search query patterns and evaluation criteria.\n\n## Step 3 - Outline Alignment (`update-readme:outline-aligned`)\n- Compare current README headings (`rg -n '^#' README.md`) against patterns observed in exemplars.\n- Draft a target outline covering: value proposition, installation, quickstart, deeper usage/configuration, architecture/feature highlights, performance or math guarantees, documentation links, contribution/governance, roadmap/status, and licensing/security notes.\n- validate internal documents (docs/, spe"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn7d107jg9jv602h9ytsegydq184a42s\",\n  \"slug\": \"nm-sanctum-update-readme\",\n  \"version\": \"1.9.19\",\n  \"publishedAt\": 1787750482309\n}"},{"path":"modules/exemplar-research.md","content":"# Exemplar Research Patterns\n\nDetailed patterns for finding, evaluating, and documenting high-quality README exemplars.\n\n## Web Search Query Patterns\n\n### Language-Specific Queries\n\n```\n\"GitHub [language] README best practices\"\n\"[language] framework README examples\"\n\"[language] project README badges\"\n\"[language] library documentation structure\"\n\"awesome [language] README\"\n```\n\n### Framework/Domain-Specific Queries\n\n```\n\"[framework] README structure\"\n\"[domain] project README examples\" (e.g., \"CLI tool README examples\")\n\"[language] [project-type] documentation\" (e.g., \"Rust async library documentation\")\n```\n\n### Quality Indicators\n\n```\n\"high star count [language] README\"\n\"well-maintained [language] project README\"\n\"[language] project documentation best practices 2024\"\n```\n\n## Exemplar Evaluation Criteria\n\nAssess each candidate README using these dimensions:\n\n### Structure & Organization\n- **Section order**: Does it follow a logical progression (value → quickstart → details)?\n- **Progressive disclosure**: Are complex topics deferred until after basics?\n- **Table of contents**: Is it present and well-structured?\n- **Visual hierarchy**: Clear heading levels, spacing, readability?\n\n### Content Quality\n- **Value proposition**: Clear statement of what the project does and why it matters?\n- **Quickstart clarity**: Can a new user get started in <5 minutes?\n- **Code examples**: Are they runnable, realistic, well-commented?\n- **Installation steps**: Clear, tested, platform-aware?\n\n### Technical Communication\n- **Accuracy**: Does it match the actual codebase capabilities?\n- **Completeness**: Coverage of installation, usage, configuration, troubleshooting?\n- **Governance messaging**: Clear contribution guidelines, roadmap, support channels?\n- **Math/algorithm exposition**: For technical projects, is the theory well-explained?\n\n### Maintenance Signals\n- **Recency**: Last commit within 6 months?\n- **Star count**: Indicator of community validation (>500 stars preferred)\n- **Maintainer activity**: Active issue responses, recent releases?\n- **CI/CD badges**: Evidence of automated quality checks?\n\n## Citation Format\n\nRecord each exemplar with full attribution:\n\n```markdown\n### Exemplar: [Project Name]\n- **URL**: https://github.com/[org]/[repo]\n- **Language**: [Primary language]\n- **Stars**: [count] (as of [date])\n- **Last Updated**: [date]\n- **Relevant Patterns**:\n  - [Pattern 1]: [Description and why it's relevant]\n  - [Pattern 2]: [Description and why it's relevant]\n  - [Pattern 3]: [Description and why it's relevant]\n- **Specific Elements to Adapt**:\n  - [Element]: [How it applies to this project]\n```\n\n## Storage Recommendations\n\n### Temporary Research Notes\nStore research findings in a temporary file during the session:\n\n```bash\n# Create research notes file\ncat > /tmp/readme-research.md << 'EOF'\n# README Exemplar Research\n\n## [Language 1] Exemplars\n[Citations...]\n\n## [Language 2] Exemplars\n[Citations...]\nEOF\n```\n\n### Final Report Integration\nInclude exemplar cit"},{"path":"modules/language-audit.md","content":"# Language Audit Patterns\n\nDetailed patterns and commands for detecting project languages and their documentation implications.\n\n## Manifest File Detection\n\nCheck for language-specific manifest files to identify the primary language(s):\n\n```bash\n# Rust\nls -1 Cargo.toml 2>/dev/null\n\n# Node.js/TypeScript\nls -1 package.json 2>/dev/null\n\n# Go\nls -1 go.mod 2>/dev/null\n\n# Python\nls -1 pyproject.toml setup.py requirements.txt 2>/dev/null\n\n# Java/Kotlin\nls -1 pom.xml build.gradle build.gradle.kts 2>/dev/null\n\n# Ruby\nls -1 Gemfile 2>/dev/null\n\n# PHP\nls -1 composer.json 2>/dev/null\n```\n\n## File Count Analysis\n\nCount source files by extension to determine language distribution:\n\n```bash\n# Rust\ngit ls-files | rg '\\.rs$' | wc -l\n# or for preview\nrg --files -g '*.rs' | head -10\n\n# Python\ngit ls-files | rg '\\.py$' | wc -l\nrg --files -g '*.py' | head -10\n\n# Go\ngit ls-files | rg '\\.go$' | wc -l\nrg --files -g '*.go' | head -10\n\n# TypeScript/JavaScript\ngit ls-files | rg '\\.(ts|tsx|js|jsx)$' | wc -l\nrg --files -g '*.ts' -g '*.tsx' | head -10\n\n# Java\ngit ls-files | rg '\\.java$' | wc -l\nrg --files -g '*.java' | head -10\n```\n\n## Language Priority Heuristics\n\nDetermine primary language using these priority rules:\n\n1. **Manifest presence**: If a language-specific manifest exists, it's a strong signal\n2. **File count dominance**: Language with >60% of source files is primary\n3. **Directory structure**: Check for language-specific directories (src/, lib/, pkg/)\n4. **Build configuration**: Presence of Makefile, CMakeLists.txt, or build scripts\n\n## Secondary Language Handling\n\nDocument secondary languages when they:\n\n- Represent >20% of codebase\n- Serve distinct architectural roles (e.g., Rust backend + TypeScript frontend)\n- Have their own build/test infrastructure\n- Require separate installation or runtime considerations\n\n### Example Multi-Language Documentation Strategy\n\n```markdown\n## Installation\n\n### Backend (Rust)\n[Rust-specific instructions]\n\n### Frontend (TypeScript)\n[Node/npm-specific instructions]\n```\n\n## Recording Findings\n\nCapture the audit results in a structured format:\n\n```\nLanguage Audit Results:\n- Primary: [Language] ([count] files, [manifest])\n- Secondary: [Language] ([count] files, [manifest])\n- Method: [manifest detection | file count | directory structure]\n- Documentation implications: [single-language | multi-language sections needed]\n```"},{"path":"skill-card.md","content":"## Description:\n\nRefreshes README structure and content using repo context and exemplar research.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[athola](https://clawhub.ai/user/athola)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and documentation maintainers use this skill to audit a repository, research relevant README examples, and restructure README content with clearer installation, usage, governance, and verification sections.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: README edits could introduce inaccurate or misleading project guidance.\n\nMitigation: Review the documentation diff, verify links and claims against repository files, and scan the final README before release.\n\nRisk: The workflow uses web-based exemplar research and references external plugin dependencies.\n\nMitigation: Review cited exemplar sources and external plugin dependencies separately before relying on their recommendations.\n\nRisk: Some trigger words are broader than the README update workflow itself.\n\nMitigation: Invoke the skill explicitly for README refresh tasks rather than relying only on broad trigger matching.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/athola/skills/nm-sanctum-update-readme)\n- [Metadata homepage](https://github.com/athola/claude-night-market/tree/master/plugins/sanctum)\n\n## Skill Output:\n\n**Output Type(s):** [markdown, shell commands, guidance]\n\n**Output Format:** [Markdown documentation edits with command snippets and verification notes]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include citations for researched README exemplars and summaries of repository language findings.]\n\n## Skill Version(s):\n\n1.9.19 (source: server release metadata)\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":"Refreshes README structure and content using repo context and exemplar research Skill: update-readme Owner: athola Summary: Refreshes README structure and content using repo context and exemplar research Tags: latest:1.9.19 Version history: v1.9.19 | 2026-08-26T13:21:22.309Z | user Release v1.9.19 v1.9.17 | 2026-07-30T05:41:22.501Z | user Release v1.9.17 v1.9.16 | 2026-07-14T19:58:10.077Z | user Release v1.9.16 v1.9.14 | 2026-06-30T18:05:59.607Z | user Release v1.9.14 v1.9.13 | 2026-06-27T16:23:","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1387,"uniquenessScore":54,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-10T07:24:19.464Z","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-10T07:24:19.464Z","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-10T10:49:58.913Z","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"}]}}}