Loading...
Loading...
Found 168 Skills
Inspect an existing memory corpus (wiki substrate) and align it to this repo's Obsidian-friendly note-graph conventions. Use this when the user wants to import, normalize, retrofit, or clean up existing memory, notes folder, vault, docs tree, or mixed markdown knowledge base. In monorepos, also use it to align relevant AGENTS.md and CLAUDE.md files. Excludes goals/ from normalization. Not for routine wiki maintenance; use /loam::linting-memory for that.
Keep a Blume docs site in sync with the product it documents. Audit recently merged pull requests, changelogs, config schemas, CLI help, and public APIs against the docs content, update only pages that are factually stale, verify the docs build, and open (or update) a maintenance pull request — or report a clean no-op. Use when asked to check docs for drift, refresh stale documentation, run a scheduled docs audit, or keep docs current after a release.
[user] 설정된 repository들의 open pull request를 deterministic fresh triage로 읽고, 지금 처리할 일과 기다릴 일을 자연스럽게 브리핑한 뒤 한 번 승인된 범위에서 bounded multi-PR maintenance를 수행합니다.
This skill should be used when the user asks to validate, reindex, repair registries, check links, check continuity, count words, summarize a story project, import an existing manuscript, export a manuscript, run the story CLI, or perform deterministic maintenance on a Story Skills markdown project.
Track the IP portfolio — registrations, renewals, maintenance fees, and use declarations. Use when checking what's renewing, adding or updating an asset, recording a maintenance filing, or auditing the register for gaps, lapses, and use-in-commerce questions. Receives handoffs from prosecution and clearance work.
Build and run a business owner's second brain: one vault, two wings (personal + four-layer business), operated through Claude Code with Obsidian as the viewing deck. Routes every entry to one of four modes: Setup, Capture, Distill, Create-My-Jarvis. Use when the user wants a second brain built or their business knowledge organized into a vault ("set up my second brain"), wants to move their business in one room at a time ("capture", "move in a room"), asks for the weekly maintenance ritual ("distill", "tidy my vault", "weekly review"), wants their AI given a persona ("create my jarvis"), or asks for a retrofit an older vault lacks: the safety lock, session memory ("make my sessions searchable"), the maintenance doorbell ("update my maintenance doorbell"), the boot gate ("upgrade my command base"), or the Command Deck ("rebuild my deck", "fix my deck", "add my command deck", "my dashboard is empty").
Consult installed, version-matched Rstack docs only for user-facing `rs` command behavior, `rstack.config.*` semantics, or public `rstack` APIs. Do not use for purely internal implementation, tests, performance, or repository maintenance.
Unified upstream repo operations: audit commit drift, check UDS file-level drift, detect repo overlap with local project, and perform sync maintenance. Use when: reviewing upstream updates, auditing standards drift, evaluating a new repo for integration, updating last-sync.yaml after sync. Triggers: "upstream audit", "uds check", "repo overlap", "sync maintenance", "上游同步", "上游檢查", "上游維護".
Turn a process that lives in the owner's head into a written SOP their staff can actually follow: one guided sitting ending in a markdown note with a step-by-step RACI table and a swimlane map filed beside it. Works with or without a second-brain vault. Use when the user wants a process documented as an SOP ("write an SOP", "document this process", "SOP for <anything>", "帮我写 SOP", "把流程变成 SOP"), and when they resume a draft left mid-sitting ("continue the SOP", "接着上次那个 SOP"). NOT for setting up a second brain, building a vault, capturing a business into rooms, weekly maintenance, or giving an AI a persona: those belong to the my-second-brain skill, which is installed and updated separately from this one.
Use when running an infra-only health audit across Pylot systems — LaunchAgent, cron, secrets, labels, branches, and issues.
Schedule tasks with safety; use withoutOverlapping, onOneServer, and visibility settings for reliable cron execution
Perform a structured maintainer-style PR review for the mariadb-operator repository. Gathers PR context, triages the change, and evaluates correctness, safety, pitfalls, backwards compatibility and code quality against the project conventions documented in AGENTS.md. Use whenever the user mentions a mariadb-operator PR number or URL and wants any kind of judgment on it — "review this PR", "what do you think of #1234", "is this safe to merge", "assess this diff", "take a look at this change" — even if they don't literally say "review".