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

Mexus

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

収集済み skills
24
Stars
84
更新
2026-05-18
Forks
4
職業カバレッジ
2 件の職業カテゴリ · 100% 分類済み
リポジトリエクスプローラー

このリポジトリの skills

board
その他コンピュータ職

Use when showing a Web board for a Markdown-only Agent Team Mission without a Mexus server.

2026-05-18
roundtable
その他コンピュータ職

Use when opening a RoundTable proposal in the active Markdown-backed Agent Team Mission.

2026-05-18
run
その他コンピュータ職

Use when executing the next tasks from a Markdown-backed Agent Team kanban with Claude Code or Codex background Agents.

2026-05-18
team
その他コンピュータ職

Use when starting or continuing a Markdown-only Agent Team Mission with Claude Code or Codex background Agents and no Mexus server.

2026-05-18
team-status
その他コンピュータ職

Use when summarizing a Markdown-only Agent Team Mission from local files.

2026-05-18
team-stop
その他コンピュータ職

Use when stopping the local Web board for a Markdown-only Agent Team Mission.

2026-05-18
board
その他コンピュータ職

Use when a Mexus-launched agent should show a local Web board for repository Agent Team Mission files.

2026-05-16
team
その他コンピュータ職

Use when a Mexus-launched agent should start or continue an Agent Team Mission using Markdown kanban coordination.

2026-05-16
team-status
その他コンピュータ職

Use when a Mexus-launched agent should summarize the current Agent Team Mission kanban in the terminal.

2026-05-16
team-stop
その他コンピュータ職

Use when a Mexus-launched agent should stop the local Agent Team Web board.

2026-05-16
agent-team-mission-workflow
その他コンピュータ職

Create and operate Markdown-native Mission workflows for multi-agent engineering collaboration in Mexus or similar CLI-agent workbenches. Use when the user wants to split a complex engineering goal across multiple agents, create agent-team mission files, define Squad Lead and agent roles, manage kanban task flow, run publisher review, or use a roundtable voting file for cross-agent decisions.

2026-05-09
agent-team-mission-workflow
その他コンピュータ職

Create and operate Markdown-native Mission workflows for multi-agent engineering collaboration in Mexus or similar CLI-agent workbenches. Use when the user wants to split a complex engineering goal across multiple agents, create agent-team mission files, define Squad Lead and agent roles, manage kanban task flow, run publisher review, or use a roundtable voting file for cross-agent decisions.

2026-05-09
dispatch-list
その他コンピュータ職

List panes attached to the active Mission for Squad Lead dispatch decisions.

2026-05-09
dispatch
その他コンピュータ職

Ensure a real Mission Agent Pane exists for an agent in the active Mission.

2026-05-09
mission-activate
その他コンピュータ職

Activate an existing Agent Team Mission through the Mexus CLI.

2026-05-09
mission-agent-add
その他コンピュータ職

Add an Agent roster entry to the active Mission agents.md.

2026-05-09
mission-agent-remove
その他コンピュータ職

Remove an Agent roster entry from the active Mission agents.md without closing panes.

2026-05-09
mission-archive
その他コンピュータ職

Archive a Mission and close its Mission Panes through the Mexus CLI.

2026-05-09
mission-create
その他コンピュータ職

Open a Squad Lead Pane for a new Agent Team Mission without generating Mission files.

2026-05-09
gh-issue-list
ソフトウェア開発者

List GitHub issues from the current repository with optional filters. Use when the user asks to see open/closed issues, pending tickets, issues by label/assignee, or triage work.

2026-04-19
gh-issue-reply
ソフトウェア開発者

Post a reply comment to a GitHub issue. Use when the user wants to respond to an issue, acknowledge a bug report, or share a fix reference with the reporter.

2026-04-19
gh-issue-resolve
ソフトウェア開発者

Analyze a GitHub issue and implement the fix in code. Use when the user says "fix issue

2026-04-19
gh-push
ソフトウェア開発者

Commit pending changes (optional) and push the current branch to the remote. Use when the user says "push", "push the code", "commit and push", or "send it up". Includes safety checks for main-branch pushes and force-push.

2026-04-19
gh-workflow
ソフトウェア開発者

End-to-end GitHub issue workflow — list issues, pick one, implement the fix, commit, push, and reply to the reporter. Use when the user says "handle issues", "work through the issue queue", or "process issue

2026-04-19