Skip to main content
Manusで任意のスキルを実行
ワンクリックで
GitHub リポジトリ

claude-skills

claude-skills には Magnus-Gille から収集した 13 個の skills があり、リポジトリ単位の職業カバレッジとサイト内 skill 詳細ページを表示します。

収集済み skills
13
Stars
4
更新
2026-07-15
Forks
0
職業カバレッジ
7 件の職業カテゴリ · 100% 分類済み
リポジトリエクスプローラー

このリポジトリの skills

close
ソフトウェア開発者

Session closing checklist for Git state, documentation, handoff files, and Munin memory. Use when the user invokes /close or asks to wrap up a session, including work that touched multiple repositories.

2026-07-15
ticket-fleet
その他コンピュータ職

Resolve a batch of GitHub tickets via parallel headless Claude Code sessions — one isolated git worktree per ticket, gated permissions, triple review (Codex + local-model first-pass + orchestrator comment), interrupt-resume, and merge orchestration. Use when the user wants many well-scoped tickets solved autonomously across one or more repos.

2026-07-13
debate-claude
プロジェクト管理専門家

Run an adversarial debate with Claude to stress-test a draft, plan, research claim, or design decision. Use when Codex needs structured cross-model critique before finalizing a consequential decision, architecture, protocol, research claim, security assessment, or product priority.

2026-07-12
debate
ソフトウェア開発者

Run an adversarial debate with a cross-model reviewer (Codex or Antigravity/agy) to stress-test a draft, plan, research claim, or design decision. Use this whenever you need structured critique before finalizing decisions.

2026-07-10
review-pr-codex
ソフトウェア品質保証アナリスト・テスター

Run a cross-model PR review using Codex CLI. Invokes Codex headless to review the current branch diff, then reads findings and fixes issues or reports to user.

2026-07-10
friction-triage
ソフトウェア開発者

Sweep the Munin signals/friction corpus (report_friction self-reports), group recurring failures, and file consolidated GitHub issues routed to their owning repos + the Grimnir Roadmap board. Use when the user wants to triage accumulated friction, turn friction signals into tickets, or asks "what friction have we collected / let's file tickets for it".

2026-06-30
email-triage
一般事務員

Reliable conversation-level email triage over a date range. Identifies genuinely open threads, emails that actually need a reply, and real correspondence hiding in junk — by reconstructing each conversation across inbox + sent + drafts + junk before judging, so mobile-quoted or already-sent replies are never mis-flagged. Use for "what's still open / what do I owe a reply / anything missed" over weeks or months.

2026-06-09
user-test-memory
ソフトウェア品質保証アナリスト・テスター

Spawn independent AI agents across one or more ecosystems (Claude, Codex, Antigravity) to user-test the Munin memory system. Each explores with minimal pre-knowledge and returns structured feedback on what works, what's broken, and what's missing.

2026-06-01
magnus-security-review
情報セキュリティアナリスト

Comprehensive AI-powered security review of a codebase or repository. Builds a threat model, scans for vulnerabilities across OWASP Top 10 + LLM Top 10, validates findings, and proposes patches. Mirrors the workflow of Claude Code Security and Codex Security but using manual best practices.

2026-05-18
delegate
ソフトウェア開発者

Delegate a bounded one-shot task to Hugin's orchestrator-v1 broker — cheaper / smaller runtimes via the `hugin-mcp` MCP. Use for summarize / extract / classify / draft / rewrite / short reason work where you'd rather not spend Claude tokens. Submits, polls to completion, surfaces the result, and prompts the user to rate it.

2026-05-06
commit
ソフトウェア開発者

Standardized git commit workflow with author verification, diff review, and conventional commit messages.

2026-04-27
eli5
カスタマーサービス担当者

Re-explain the previous response in plain, easy-to-understand language. No jargon, no acronyms without unpacking, short sentences. Use when the user types /eli5 — they want the same content as the last assistant turn, but accessible to a non-expert.

2026-04-27
issues
プロジェクト管理専門家

Check GitHub issues and tickets for the current repo. List open issues, view details, filter by label, or search. Use when the user asks about issues, tickets, bugs, or backlog.

2026-04-04