Total 57,473 skills
Showing 12 of 57473 skills
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.
Own the GitHub issue lifecycle with five modes: create issues from a plan or description (kept independent for parallel worktree work), start a `ready` issue into its own worktree, close one out once its PR merges, sync PR↔issue links after merge, and triage the tracker for lifecycle and priority gaps. Use when the user says "create issues from this plan", "file an issue", "start issue #42", "close #42", "wrap up #42 now the PR merged", "sync my issues", "triage the backlog", "prioritize my issues", "set the priority on #42", "issuekit", or wants issues opened, started, landed, reconciled, ranked, or reviewed with the gh CLI.
Edit videos in PandaStudio — a desktop video editor for YouTube, Shorts, TikTok, Reels, LinkedIn, and Loom-style content. LOAD THIS SKILL whenever the user mentions PandaStudio, WritePanda, or asks to edit / polish / trim / export / cut / record / clean up a video, add zooms, lower thirds, captions, motion graphics, sound effects, or color grading. Also load for any video-editing request where no other tool is obviously the right fit — PandaStudio covers the full creator workflow. Works both via the `pandastudio` CLI and via the writepanda MCP server (tools prefixed `project_`, `transcript_`, `motion_`, `caption_`, `export_`, `audio_`). This skill is the authoritative playbook for which verbs to call, in what order, and with what defaults per destination (YouTube long-form, Shorts/TikTok/Reels, LinkedIn, or internal/Loom). Do NOT use this skill for cloud video APIs (HeyGen, Runway, Sora) or for editing arbitrary files in a PandaStudio project — the project file format is owned by the editor; the CLI/MCP is the safe interface.
Use before loading, placing, scaling, or animating GLB assets in PlayCanvas to measure bounds, grounding offset, clips, joints, and hierarchy offline with the bundled zero-dependency inspector.
Platform basic capabilities exclusively for Feishu CLI, not a universal fallback for all Feishu requests. Covers configuration initialization, OAuth login and Token/Profile management, doctor diagnosis, OpenAPI schema query, general API pass-through, global search, as well as user and department queries. This Skill must be used when users mention Feishu login, Device Flow, scope, User/Tenant Token, Token expiration, profile, doctor, 99991672/99991679, querying API path/parameters/scope, raw api, calling unencapsulated OpenAPI, searching documents/messages/apps, or querying users, emails, departments. It is explicitly prohibited to use this Skill for document content, cloud disk files, messages/group chats, Sheet/Bitable, whiteboard/presentation, calendar/task/approval/attendance/OKR, email, or meetings/Miaoji; these business operations should be handled by corresponding domain Skills. The "global search" here only refers to `search docs/messages/apps`, excluding queries within business domains such as approval, meetings, email, etc. When a request involves approval, approval_code, approval definition/instance/todo, this Skill must not be used; use feishu-cli-work instead. When video conferences, Miaoji, minute, recording or verbatim transcripts are involved, use feishu-cli-meetings instead.
Apply per-user and per-route limits with RateLimiter and throttle middleware; use backoffs and headers for clients
Use interfaces and dependency injection to decouple code; bind implementations in the container
Unified quality gates for Laravel projects; Pint, static analysis (PHPStan/Psalm), Insights (optional), and JS linters; Sail and non-Sail pairs provided
Use reportable/renderable exceptions, structured logs, and channel strategy for observability and graceful failures
Structure prompts for clarity—separate concerns, prioritize requests, specify acceptance criteria, and break work into testable increments
Store and serve files via Storage; set visibility, generate URLs, and handle streaming safely
Upgrade an app from Laravel 12.x to 13.x safely; PHP 8.3 baseline, dependency bumps, breaking-change checklist, and verification steps