Loading...
Loading...
Found 97 Skills
Use this skill when users need to perform cross-wiki operations on knowledge content across multiple local LLM wikis (yzr-llm-wiki-management system) — from a global workspace perspective: cross-wiki scanning and indexing (INDEX/STATS), cross-wiki Q&A (routing/synthesis/comparison), cross-wiki cross-referencing and duplicate entity governance, workspace-level health checks (LINT), cross-wiki memory (MEMORY/), and workspace format upgrade. Triggers: "Summarize content about X across all my wikis" / "Compare what wiki A and B say about Y" / "Which wiki should I check for this question" / "Scan my workspace" / "Count the number of pages across all wikis" / "Workspace health check" / "Entity X in wiki A also exists in wiki B, add a link" / "Upgrade workspace". Use this skill whenever you need to read, summarize, compare or govern content across multiple wikis — even if the workspace or skill name is not explicitly mentioned. Not applicable: Operations within a single wiki (use yzr-llm-wiki-management); Single llmw command operations such as workspace/wiki metadata configuration, adding/removing wikis, session start/stop (run llmw directly, see llmw --help, no need to load this skill); Cloud collaborative wikis (Notion / Confluence / Outline, etc.).
Manage workspace users, API tokens, folders, roles, and submit reports to workspace management using the Cargo CLI. Use when the user wants to invite or manage workspace members, create or rotate API tokens, organize resources into folders, inspect workspace roles and permissions, or submit a report to workspace management when the CLI fails or is misused.
Use this skill when users work within a local, single-user, compound-growth Markdown personal wiki (Karpathy's 'LLM owns wiki' model) — covering: ingesting raw/ materials (papers/ clippings/ external repo symlinks), querying and cross-page synthesis/ contradiction reconciliation, archiving conclusions back to the wiki, linting orphan/ outdated summaries, and format upgrades. Three core rules: raw/ controlled by users + wiki/ owned by LLM + AGENTS.md as the single source of truth. Triggers: "Ingest this paper into the wiki" / "Does the wiki have/ summarize content about X?" / "There's a contradiction between A and B in the wiki" / "Save the previous conclusion to the wiki" / "Check the wiki for orphan pages/ outdated summaries" / "Upgrade the wiki/ check wiki version" / "Include repo X in the wiki". Always use this skill whenever users need to digest materials/ retrieve wiki deposits/ archive new conclusions — even if they don't mention the skill name. Not applicable to: cloud/ team wikis (Notion/ Confluence/ Outline, etc.); wiki metadata configuration, wiki creation/deletion, session start/stop (use a single llmw command directly). **Trigger only when the cwd is the wiki root (containing `wiki_metadata.toml` + AGENTS.md skeleton)**; cross-wiki/ workspace operations go to `yzr-llm-workspace-management`; not applicable to other directories.
Grill me about specs for the workflows I want to build, within this workspace.
Work inside one artist's folder — read and update their context, brand, songs, and releases. Use for "organize [artist]'s files", "update [artist]'s brand/context", "what's in [artist]'s workspace", or any task about a named artist's files. To list your whole roster use recoup-roster-list-artists; for research/metrics on an artist use recoup-research-artist-overview.
Comprehensive cmux CLI usage guide. Use when the user asks about cmux CLI, cmux --help, socket commands, command discovery, workspaces, panes, surfaces, browser CLI, hooks, feed, settings, or automation through the cmux command.
Interpret pasted cmux workspace, pane, surface, or window refs and IDs. Use for cmux-ref, cmux-id, workspace_ref, workspace_id, pane_ref, pane_id, surface_ref, surface_id, window_ref, or window_id context blocks.
Databricks integration. Manage Workspaces. Use when the user wants to interact with Databricks data.
Segment integration. Manage Workspaces. Use when the user wants to interact with Segment data.
Invoke the `slack-cli` binary to read and act on a Slack workspace from the command line — list channels, read/search conversation history and threads, fetch unread messages, search users, manage user groups, post messages, add reactions, mark channels read, and manage saved items. Use whenever a task needs Slack data or actions, such as "what are the unread messages in
Alibaba Cloud PAI Workspace Management Skill. Create, query, and list workspaces on the Platform for AI (PAI). Triggers: "create PAI workspace", "query PAI workspace", "list workspaces", "PAI workspace", "create workspace", "get workspace", "list workspaces", "AIWorkSpace CreateWorkspace", "AIWorkSpace GetWorkspace", "AIWorkSpace ListWorkspaces"
Keep the Orca desktop app's workspace list honest about the git worktrees your workflow actually creates — link each one to its issue, keep its status current, and clean out the ones whose work already merged. Use when the user says "orcakit", "clean up my orca workspaces", "my Orca sidebar is full of finished work", "which workspaces are stale", "link my worktrees to their issues", "remove the workspaces for merged issues", or "where should Orca put new worktrees".