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

devcard

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

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

このリポジトリの skills

devcard
ソフトウェア開発者

Orchestrate DevCard MCP tools for GitHub profile analysis. Use when user wants to check a developer profile, compare developers, audit GitHub presence, generate a DevCard, or improve their profile. Entry point for all DevCard MCP interactions. Not for CLI-only operations — use devcard-generate skill for that.

2026-05-07
devcard-agent-ready
ソフトウェア開発者

Make a GitHub profile readable by AI agents and coding assistants. Use when user wants to improve their "agent readiness score", deploy devcard.json, create llms.txt, generate AGENTS.md, or make their profile machine-readable for tools like Claude Code, Cursor, Copilot, or Windsurf. Covers the full agent-readiness optimization workflow.

2026-05-07
devcard-generate
ソフトウェア開発者

Generate DevCard outputs in various formats (SVG, JSON, terminal, markdown). Use when user wants to "generate a card", "create my devcard", "make an SVG", "show my profile card", embed a card in their README, or export developer data. Covers all output formats, themes, and enrichment options.

2026-05-07
devcard-profile-audit
ソフトウェア開発者

Run a full GitHub profile audit with actionable advice. Use when user says "audit my profile", "what should I improve", "review my GitHub", "how's my profile", or wants profile advice. Combines DevCard's audit scoring, advisor rules, and fix pipelines into a guided improvement workflow.

2026-05-07
persist-plan
プロジェクト管理専門家

Persist an internal plan to context/product/plans/. Use when exiting plan mode, when the user says "save the plan", or when you notice a plan exists in .claude/plans/ that hasn't been copied to context/product/plans/ yet.

2026-04-25
retro
プロジェクト管理専門家

Run a retrospective with transcript analysis and log feedback. Use when the user explicitly invokes /retro, when a full plan implementation is complete, or after creating a PR or addressing code review feedback (if a retro hasn't happened yet this session).

2026-04-25