Use when editing MoltNet docs, especially onboarding, docs IA, examples, tone, cross-links, and avoiding duplicated canonical guidance.
53
60%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/rendered-pack-5bf21e8c/SKILL.md210007f3-bee4-44da-9fb4-12484333e1dfbafkreide5x73w2fzuyukboxpcpqfwdi4fdw5xoac264mfeyxythv6hpzuqfullDocs should read as product and operator documentation, not as process notes between an AI agent and a maintainer. Avoid phrases like "this section should stay short" or route-map language that explains the documentation artifact instead of guiding the reader.
For onboarding docs, prefer one canonical flow over a parallel page. Extend the existing page at the relevant decision point and link to the command/reference guides for details. Do not duplicate the identity-flow, team, task, daemon, or access-control explanations when those pages already exist.
operator: edouard tool: codex timestamp: 2026-06-08T15:34:40Z branch: codex/company-pilot-onboarding scope: docs,onboarding,tone refs: docs/start/getting-started.md, docs/start/install-and-initialize.md, docs/reference/agent-configuration.mdb875bde8-6529-4135-8d17-e625920d9e35bafkreibzoagbskxemlwjweodb742p2xyvialituzmaqxl724yndy72p3hufullThis onboarding-docs correction should seed a future docs-editing context pack. The useful pattern is not just wording cleanup; it is a docs architecture rule: avoid adding parallel pages when an existing canonical guide already owns the reader journey.
Candidate pack ingredients: docs tone expectations, onboarding flow placement, cross-linking without duplication, and examples of phrasing that sounds like internal process notes rather than user-facing documentation. The pack should activate when editing docs/start, docs/use, docs/reference, or when a reviewer asks for docs tone/duplication cleanup.
operator: edouard tool: codex timestamp: 2026-06-08T15:35:40Z branch: codex/company-pilot-onboarding scope: docs,context-packs,onboarding refs: docs/start/install-and-initialize.md, docs/start/getting-started.md, docs/use/context-packs.md65a6130b-2055-480b-8a2d-d5f723cd5d76bafkreidc5jm24naixep2stwnrunungudo6xy535fr2qotpcwpaown54svifullChanges:
Out of scope for this PR (follow-up): rewriting docs/use/context-pack-evals.md (still references the old Harbor design and predates the current Agent Runtime model). signer: 1671-B080-99BF-4270 operator: edouard tool: claude risk-level: low files-changed: 11 refs: AGENTS.md, apps/agent-daemon/README.md, docs/.vitepress/config.ts, docs/start/getting-started.md, docs/start/install-and-initialize.md timestamp: 2026-05-12T14:03:57Z branch: docs/use-section-reorder scope: docs, agent-daemon
a075b46c-111c-46b1-bab2-0c897cf5581ebafkreibswrlnlxmrz53rj6texajedhe56hheabwzcupfxgweauipwdss5afull55dec741-5681-4b77-b5f4-ab7bdeba67ebbafkreie3sxmlqto6bfdxwt5jeeemk5dyjmp44777tt7j7t3fkokstkfkdyfulldfe5cae0-4e85-4a29-ba1b-fefd427bb2b4bafkreifz4wtrdud723rglsj5zkempqtwdfbs4qok7chfmhuhinwwurnhbqfullStandardized the context-packs docs to the new example-command pattern. Updated tag-convention discovery to show Agent CLI, Human SDK, and MCP tabs, and updated rendered-pack activation description to show CLI, SDK, and MCP update paths. Kept the work isolated in the docs/context-pack-tabs-origin-main worktree off origin/main.
80cd8936-1cb9-41e0-b80b-784353c67340bafkreibdd3jz3kew25f62nbaozlae3oa5kxjtqp5gtjzgjprdyy2htrudifullAdded a docs-level accessibility guide for browser apps, docs pages, forms, graph/data surfaces, validation, and current lint enforcement. Linked it from the VitePress Understand sidebar and cross-linked it from the design system guide so builders can distinguish component-level rules from product/page-level checks. Validation passed with nx docs lint, typecheck, and build.\n\n\noperator: edouard\ntool: codex\ntimestamp: 2026-06-07T13:29:00Z\nbranch: docs-accessibility-guidance\nscope: docs\nrefs: docs/understand/accessibility.md, docs/understand/design-system.md, docs/.vitepress/config.ts\nrisk-level: low\nfiles-changed: 3\n
79891286-4000-4b79-95c7-2a37c9978a76bafkreid7k2m3b2w4qvr5mmxdpe6ea4fxmexdg7ldihheys2tkmiqbxngiefullRevised PR #1088 after review: split the oversized start/getting-started.md into install, diary harvesting, context pack, eval, rendered-pack, commit-authorship, and quick-reference pages. Removed deprecated docs instead of keeping compatibility stubs: builder journal, doc maintenance, builders manifesto, agent coordination, sandbox, task lifecycle, OpenClaw integration, and old root duplicates. Removed obsolete Claude project-board lifecycle commands (claim/handoff/sync), feature-dev plugins, and related gh project permissions. Updated onboarding skill links and source comments to the new canonical docs paths. Validation: pnpm --filter @moltnet/docs build passed in the isolated PR worktree.
operator: edouard tool: codex timestamp: 2026-05-10T06:45:00Z branch: codex-docs-purpose-ia scope: docs,docs-ia,claude-settings refs: docs/start/getting-started.md,docs/start/install-and-initialize.md,docs/use/context-packs.md,.claude/settings.json,.claude/commands/claim.md signer: 1671-B080-99BF-4270 risk-level: medium files-changed: 6030939b81-bb47-4ed2-9b53-a4f9b4cd4f50bafkreibu6witk37mwcousirnssy2ldoln6s5azt37qu36otclem2r6ckcmfullUpdated the onboarding docs so they read as user-facing product documentation instead of internal process notes. Replaced meta wording in Getting Started, removed future/internal phrasing from Install and Initialize, and linked the team creation step directly to console.themolt.net.
Validation: pnpm --filter @moltnet/docs build.
Related entries: 210007f3-bee4-44da-9fb4-12484333e1df (docs tone rule), b875bde8-6529-4135-8d17-e625920d9e35 (docs pack candidate).
operator: edouard tool: codex timestamp: 2026-06-08T15:36:20Z branch: codex/company-pilot-onboarding scope: docs,onboarding,tone refs: docs/start/getting-started.md, docs/start/install-and-initialize.md risk-level: low files-changed: 25daa9ca
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.