agentleFS
DONGHO5270DONGHO5270/mcp-management-system/.claude/skills/mcp-management-workflow/skill.md

mcp-management-workflow

Skill0 starsChanged 9 months agoApache-2.0View on GitHub

Complete development workflow for MCP Management System v2.1 including Phase 0 cognitive analysis, MCP service selection and testing, template modification procedures, and deployment protocols. Use when working on MCP Management System development tasks.

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start: Read NEXT_SESSION.md → Skills auto-load → Plan 2-3 hours

    line 69
  2. Very specific:

    End: Update NEXT_SESSION.md (state, decisions, actions) → Commit WIP

    line 71

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
skill.md

MCP Management Workflow

MCP Management System v2.1 개발 워크플로우.

Development Cycle

PhasePurposeSkills/MCP
P0Analysisphase0-analysis
P1MCP Selectionmcp-selector
P2ImplementationTDD, coding-standards
P3Testingtest scripts
P4DocumentationCLAUDE.md
P5Deploymentdeployment-checklist

Common Workflows

WorkflowSteps
Quick Bug FixFix → Test → Commit (fix:)
Feature AdditionP0 → P1 → P2 → P3 → P4 → P5
Template ModP0 → Modify → Test tokens → Deploy
MCP AdditionP0 → Implement → .mcp.json → Test → Deploy

Key Commands

node test-all-15-services.cjs     # Test all MCP
node mcp-bridge.cjs [svc] [method] # Indirect call
gh pr create --title "[T]"         # Create PR

Session Management

Start: Read NEXT_SESSION.md → Skills auto-load → Plan 2-3 hours

End: Update NEXT_SESSION.md (state, decisions, actions) → Commit WIP

DON'T document: Methodologies (in skills), Workflows (in skills), Checklists (in skills)


Detailed workflow guide: See prompt.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.