agent-system

What to consider before installing: - The skill's high-level purpose (an autonomous orchestrator) matches the code and docs, but there are serious inconsistencies that will likely break integration or produce surprising behavior. Notable problems: index.js references a non-existent export, complexity is documented as a numeric 1–10 but the planner returns 'low'/'medium'/'high' strings, and schema fields (metrics, plan shape) don't line up with actual return values. These will cause runtime errors or mismatched contracts. - Policy/design concern: the skill forces 'do not ask clarifying questions' and requires auto-filling defaults and always producing output. That design increases the chance of hallucinated/incorrect results and could be unsafe if the agent is allowed to act autonomously on ambiguous or sensitive tasks. Consider whether you want the agent to proceed without asking. - Operational safety: no credentials or network calls appear in the code, which reduces exfiltration risk, but the code is runnable JS — review it, run tests in an isolated environment, and do a security audit before enabling the skill for production/autonomous use. - Recommended actions before enabling broadly: 1) Fix the code/docs/schema mismatches (export names, complexity type, metrics field names) and ensure files are complete. 2) Add/verify unit tests that exercise index.js tools (agent_dispatch/agent_plan/agent_review) and dispatch path. 3) Reconsider the 'prohibit asking' policy: permit safe clarifying questions for tasks that may have security/privilege implications. 4) Run the package in a sandboxed environment (no access to secrets or production systems) and inspect logs/outputs; disable autonomous invocation for sensitive contexts until behavior is validated. 5) If you are not the maintainer, ask the publisher for a canonical homepage or source repo and for signed releases; lack of a homepage and the truncated file reduce confidence in the package's integrity.