Audit or tidy a Hyalo knowledgebase for broken links, orphan documents, stale content, and inconsistent metadata.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Resolve the installed hyalo executable and run hyalo config --format json.
Use the configured vault and existing schemas. If the executable or configuration is
missing, report what is needed before doing maintenance.
An audit or health question is read-only. A request to tidy or repair authorizes relevant changes, not deletion of notes based only on age or orphan status.
Only when the user explicitly selects Jev assistance, read references/jev.md and follow its scoped preparation and suggestion workflow before loading full documents. An API key or repository setting never enables Jev. Ordinary tidy needs no JavaScript runtime or network access; Jev failure leaves the usual local workflow available.
Orient with hyalo summary --format text, hyalo lint --format text, and
hyalo find --broken-links --format text. Inspect individual files with hyalo read.
Check schemas with hyalo types list before proposing metadata normalization.
An orphan can be a legitimate entry point; stale status requires evidence from its content.
Prioritize concrete findings. When authorized to repair, preview applicable fixes
(hyalo lint --fix --dry-run; consult hyalo links --help for link repairs).
Use Hyalo for frontmatter and tasks, normal editing tools for prose, and preserve meaning.
Do not apply uncertain fuzzy link replacements without inspecting the candidates.
Run lint on changed files and recheck the original findings. Report what changed, what remains unresolved, and any skipped or failed checks. Keep audit-only runs free of writes, including creating or dropping snapshot indexes.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Run a dogfooding session for hyalo — build from source, exercise the CLI against real knowledgebases (own KB, MDN, GitHub Docs, VS Code docs), find bugs, verify recent fixes, assess UX, measure performance, and write a structured report. Use this skill whenever the user says /dogfood, "dogfood", "run a dogfood session", "test hyalo against real data", or wants to exercise hyalo on real knowledgebases to find issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Search and edit structured markdown knowledgebases with the Hyalo CLI: frontmatter, tags, tasks, links, and document structure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use the hyalo CLI instead of read/edit/grep/write when working with markdown (.md) files that have YAML frontmatter. This skill MUST be consulted whenever pi is working with markdown documentation directories, knowledgebases, wikis, notes, Obsidian-compatible collections, Zettelkasten systems, iteration plans, or any collection of .md files with frontmatter. Trigger this skill when: searching or filtering markdown files by content, tags, or properties; reading or modifying YAML frontmatter; managing tags or metadata across documents; toggling task checkboxes in markdown; getting an overview of a documentation directory; querying document properties or status fields; bulk-updating metadata across many markdown files; or when you find yourself repeatedly using read/edit/grep/write on .md files. Even if the user does not mention "hyalo" by name, use this skill whenever the task involves structured markdown documents with frontmatter. For pi sessions, ALWAYS use `--format text` for compact, LLM-friendly output.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Maintain Keep a Changelog files with Hyalo's changelog profile and add/release commands.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Maintain Markdown Architecture Decision Records with Hyalo's MADR profile and table-of-contents commands.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Maintain Open Knowledge Format vaults with Hyalo's OKF index, log, and conformance commands.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.