Dynamic Skills & Agentic Demo Rediness

Open
#129 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
backend, tooling

Research direction

Start by reading server.js and tracing its initialization and tool setup. Identify where the /skills directory is scanned, how core and auxiliary tools are separated, and how rulesets determine exposed tools. Done means skills load automatically, invalid or missing skills do not prevent startup, and basic validation or logging is present.

Written by the indexing model from the issue text.

Description

As a developer, I want a dynamic skills registry so that I can add new tools without modifying core code.

Acceptance Criteria:

  • Skills are auto-loaded from a /skills directory at startup
  • Core tools ard xiliary tools are decoupled
  • Only relevant toolsare exposed per ruleset
  • System starts cleanly with missing or invalid skills

Sprint Tasks:

  • Refactor server.js to implement skill loader
  • Scan /skills directory on initialization
  • Seperate manifold-core tools from auxiliary tools
  • Implement tool filtering by installed rulesets
  • Add basic validation/logging for skill loading.
Dominant language
JavaScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Picolab/MCPforEXP

All issues in Picolab/MCPforEXP

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.