Skills your agents can run
Plug-and-play capabilities — vetted, versioned, and runnable from any Mighty agent.
Local-first personal knowledge base for tracking ideas, projects, tasks, habits, and any object type you define. YAML-based with no cloud lock-in.
Read a Confluence page and recursively explore its child pages up to 3 levels deep. Use when users want to comprehensively read a Confluence page tree, understand hierarchical documentation, or analyze content across parent and child pages.
为指定的 Markdown 文章添加完整的 frontmatter 头信息,包括 title、slug、category、readingTime 等字段。当用户需要格式化文章、添加文章头信息时使用此 Skill。
将重要内容记录到 Obsidian Memory 文件夹,自动按日期整理并添加时间戳
Governance + tooling pattern for storing research artifacts, tagging, and discovery.
Use when implementing plan-build-improve cycles for content updates. Triggers on "knowledge workflow", "plan then build", "spec-driven implementation".
Operations, syncing, versioning, and release management for Obsidian projects. Load when running builds, syncing references, bumping versions, or preparing for release.
Build mobile-compatible Obsidian study vaults from academic materials with checkpoint workflow and QA. Battle-tested on 800KB+ projects. Works across CS, medicine, business.
Automates the creation of documentation for solved problems.
Quick capture of raw thoughts with intelligent domain classification and competitive intelligence extraction
Create TikZ diagrams in Obsidian using TikZJax plugin. Use when visualizing geometric shapes, coordinate systems, game scenes, circuit diagrams, chemical structures, or complex technical drawings that require precise positioning.
This rule provides instruction for interacting with the Obsidian API
Create an implementation plan and a GitHub Issue based on the task description provided as an argument
Curated repository of experiment hypotheses, assumptions, and historical learnings.
Creates GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.
Git history investigation. Use when: tracking code changes, finding where bugs were introduced, root cause analysis. Not for: code exploration (use code-explore), issue analysis (use issue-analyze). Output: history trace + root cause report.
Writing pull request titles and descriptions for the tldraw repository. Use when creating a new PR, updating an existing PR's title or body, or when the /pr command needs PR content guidance.
GitHub CLI (gh) comprehensive reference for repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line.
Git operations: commits, branches, PRs, and conflict resolution
Professional code review with auto CHANGELOG generation, integrated with Codex AI