Siyuan MCP Import Migration
yangtaihong59/siyuan-plugins-mcp-sisyphus
MCP staged playbook for Markdown and external database migration with explicit targets, mappings, bounded writes, and layered readback.
Checklists for adding a new MCP tool, a new Flyway database migration, or a new Gradle dependency to the Task Orchestrator server, including the tool-documentation single-source policy…
Install Add Component
$ npx skills add jpicklyk/task-orchestrator --skill add-component -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jpicklyk/task-orchestrator add-component --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jpicklyk/task-orchestrator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/add-component .claude/skills/add-component && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "add-component" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/add-component into .claude/skills/add-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-component", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/add-componentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jpicklyk/task-orchestrator --skill add-component -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jpicklyk/task-orchestrator add-component --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jpicklyk/task-orchestrator.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/add-component .agents/skills/add-component && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "add-component" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/add-component into .agents/skills/add-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-component", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jpicklyk/task-orchestrator --skill add-component -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jpicklyk/task-orchestrator add-component --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jpicklyk/task-orchestrator.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/add-component .cursor/skills/add-component && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "add-component" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/add-component into .cursor/skills/add-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-component", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jpicklyk/task-orchestrator.git --path .claude/skills/add-component--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jpicklyk/task-orchestrator --skill add-component -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jpicklyk/task-orchestrator add-component --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jpicklyk/task-orchestrator.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/add-component .gemini/skills/add-component && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "add-component" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/add-component into .gemini/skills/add-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-component", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jpicklyk/task-orchestrator add-componentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jpicklyk/task-orchestrator --skill add-component -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jpicklyk/task-orchestrator.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/add-component .github/skills/add-component && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "add-component" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/add-component into .github/skills/add-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-component", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jpicklyk/task-orchestrator --skill add-component -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jpicklyk/task-orchestrator add-component --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jpicklyk/task-orchestrator.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/add-component .opencode/skills/add-component && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "add-component" agent skill from https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/add-component into .opencode/skills/add-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-component", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
add-component- GitHub stars
- 207
- Token cost
- ~1k tokens
- SKILL.md length
- 442 words
- Files
- 1
- Skills in repo
- 28
- Repo updated
- First seen
- Licence
- MIT
At a glance
Checklists for adding a new MCP tool, a new Flyway database migration, or a new Gradle dependency to the Task Orchestrator server, including the tool-documentation single-source policy…
- Works in 5 steps: Extend BaseToolDefinition in… → Register in buildMcpTools()… → Update all three documentation surfaces… → …
- Changing an MCP tool
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Creating a migration
What it does
Add Component is an agent skill from jpicklyk/task-orchestrator. Checklists for adding a new MCP tool, a new Flyway database migration, or a new Gradle dependency to the Task Orchestrator server, including the tool-documentation single-source policy (parameterSchema field descriptions vs the prose description string vs api-reference.md). Use when adding or changing an MCP tool or its parameters, creating a migration, or adding a dependency to the version catalog.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Databases, covering Database migrations and MCP servers. It works with Gradle. The repository describes itself as: Server-enforced workflow discipline for AI agents. An MCP server providing persistent work items, dependency graphs, quality gates, and actor attribution. Schemas define what… The licence is MIT.
When your agent uses it
- Changing an MCP tool
- Creating a migration
- Adding a dependency to the version catalog
Example prompts
- “Use the add-component skill to checklist for adding a new MCP tool, a new Flyway database migration, or a new Gradle dependency to the Task…”
- “/add-component”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Extend BaseToolDefinition in current/src/main/kotlin/.../application/tools/
- Register in buildMcpTools() (CurrentMcpServer.kt) — ToolDocumentationConsistencyTest and
- Update all three documentation surfaces (see below)
- Add a ToolTokenBudgetTest per-tool ceiling row for the new tool (see that test's "BUDGET
- Add tests in current/src/test/kotlin/io/github/jpicklyk/mcptask/current/application/tools/
What it can do on your machine
Read from SKILL.md and the folder at commit b688ea0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Add Component loads about 1k tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 442 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jpicklyk/task-orchestrator at commit b688ea0, republished under its MIT licence (© jpicklyk). 442 words, ~1,019 tokens.
Download SKILL.mdSave it as
.claude/skills/add-component/SKILL.md (or your agent's skills folder).- name
- add-component
- description
- Checklists for adding a new MCP tool, a new Flyway database migration, or a new Gradle dependency to the Task Orchestrator server, including the tool-documentation single-source policy (parameterSchema field descriptions vs the prose description string vs api-reference.md). Use when adding or changing an MCP tool or its parameters, creating a migration, or adding a dependency to the version catalog.
Adding New Components
Moved from the root CLAUDE.md so it loads only when needed. The single-source documentation policy summary stays in CLAUDE.md; this file is the full procedure.
New MCP Tool
- Extend
BaseToolDefinitionincurrent/src/main/kotlin/.../application/tools/ - Register in
buildMcpTools()(CurrentMcpServer.kt) —ToolDocumentationConsistencyTestandToolTokenBudgetTestderive their tool list from this function, so registering here is sufficient for both guard tests to pick up the new tool automatically - Update all three documentation surfaces (see below)
- Add a
ToolTokenBudgetTestper-tool ceiling row for the new tool (see that test's "BUDGET PHILOSOPHY" doc comment for how to measure and set it) — its sync check fails loudly if a row is missing - Add tests in
current/src/test/kotlin/io/github/jpicklyk/mcptask/current/application/tools/
Tool Documentation Surfaces — Single-Source Policy (post token-efficiency program)
Every tool has three documentation surfaces:
| Surface | Location | Audience |
|---|---|---|
description string | In the tool source file | LLMs — seen via tools/list |
parameterSchema | In the tool source file | MCP clients — drives validation |
| API reference | current/docs/api-reference.md | Humans |
Single source of truth per parameter: each parameter is documented ONCE, in its own
parameterSchema field description — not duplicated in the tool's prose description string.
The prose description is reserved for what a flat JSON Schema cannot express: operation/mode
enum selection, mode-selection rules, trigger effects (e.g. the trigger table in advance_item),
gate semantics, and mutual-exclusion/XOR constraints across fields. This keeps the tools/list
payload lean — the MCP Token-Efficiency Program cut the full tool payload substantially by removing
exactly this kind of prose/schema duplication; ToolTokenBudgetTest guards the result going
forward with per-tool ceilings rather than a single aggregate number.
CI guard: ToolDocumentationConsistencyTest asserts (1) every parameterSchema property has
a non-blank field-level description, and (2) every operation/mode enum value is still named
in the prose description (so callers can discover available operations without reading the full
schema). It no longer requires every param name to appear in the prose description — that older
policy is what produced the bloat this program removed.
The api-reference.md surface is not machine-checked — update it manually alongside code changes.
Show full SKILL.md (115 more words)Show less
When changing a tool's parameters:
- Add/rename a param → update its
parameterSchemafield description andapi-reference.md; touch the prosedescriptiononly if the change affects mode-selection/trigger/gate semantics - Remove a param → same, plus remove any prose mention if one existed
- Change required/optional status → update the field's own schema description and
api-reference.md - Do NOT reintroduce per-field prose in
descriptionthat merely restates what's already inparameterSchema— that's the duplication this program removed
New Database Migration
Create current/src/main/resources/db/migration/V{N}__{Description}.sql. SQLite has no ALTER COLUMN — schema changes require table recreation. New tables in DirectDatabaseSchemaManager must be inserted in foreign-key order.
New Gradle Dependency
Add to gradle/libs.versions.toml ([versions] + [libraries]), then reference as libs.{name} in build.gradle.kts. Check Maven Central for the latest version.
© jpicklyk, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/add-component of jpicklyk/task-orchestrator.
Open the folder on GitHubat commit b688ea0
Compare with similar skills
Add Component next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Add Component this skilljpicklyk/task-orchestrator | 207 | — | ~1k | Automated safety check: Pass | MIT | |
| Siyuan MCP Import Migrationyangtaihong59/siyuan-plugins-mcp-sisyphus | 114 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Plan ReviewKenjiOhtsuka/harmonica | 131 | — | ~1k | Automated safety check: Pass | MIT | |
| Harmonica DevKenjiOhtsuka/harmonica | 131 | — | ~742 | Automated safety check: Pass | MIT | |
| Java MCP Server Generatorgithub/awesome-copilot | 40k | 1 repos | ~5.5k | Automated safety check: Pass | MIT | |
| Cloud API OperationsTencentCloudBase/CloudBase-AI-Toolkit | 1.1k | 1 repos | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
Plan Review
KenjiOhtsuka/harmonica
A skill your agent uses when reviewing the Harmonica restart plan against reality — after a phase PR or milestone merges, before proposing the next phase, or when asked "are the specs up to date" /…
Harmonica Dev
KenjiOhtsuka/harmonica
A skill your agent uses when working on the Harmonica Kotlin DB migration tool — planning, phase work, PRs, or anything touching this repo.
- Official
Java MCP Server Generator
github/awesome-copilot
Generate a complete Model Context Protocol server project in Java using the official MCP Java SDK with reactive streams and optional Spring Boot integration.
Cloud API Operations
TencentCloudBase/CloudBase-AI-Toolkit
Operate Tencent Cloud control-plane resources (monitoring/alarms, CLB, CAM roles, COS, MySQL, SCF) via cloud APIs when no dedicated MCP tool covers the task.
Cloudbase CLI
TencentCloudBase/CloudBase-AI-Toolkit
CloudBase CLI (tcb, 云开发CLI, Tencent CloudBase命令行) resource management skill.
More from jpicklyk/task-orchestrator
All 28 skills in this repoTask Orchestrator Server Setup
jpicklyk/task-orchestrator
Walks through how to launch and reach the MCP Task Orchestrator server container: transport, REST API, port publishing, config mounts and config-sync.
Run Wave
jpicklyk/task-orchestrator
Resolves ready MCP work items into a run plan, shows it to you, then executes it through the Workflow tool or direct subagent dispatch, with post-run verification.
Adopt Project Scope Migration
jpicklyk/task-orchestrator
Migrates an existing unscoped Task Orchestrator database to the project-scoping convention in place, creating one project anchor root and re-parenting work trees under it after a mandatory dry run.
Bulk Task Completion
jpicklyk/task-orchestrator
Completes or cancels a whole feature subtree, a named list of items, or a batch of stale work items at once, previewing the impact and warning before force-completing anything active.
Task Orchestrator Item Creator
jpicklyk/task-orchestrator
Creates an MCP work item from conversation context, anchoring it under the right container, inferring type and priority and pre-filling the required notes.
Work Item Dependency Manager
jpicklyk/task-orchestrator
Views, creates, deletes and diagnoses BLOCKS, IS_BLOCKED_BY and RELATES_TO links between MCP work items, including why an item cannot start.
Related
Works with
Categories
Questions about Add Component
What does Add Component do?
Checklists for adding a new MCP tool, a new Flyway database migration, or a new Gradle dependency to the Task Orchestrator server, including the tool-documentation single-source policy…. Add Component is an agent skill from jpicklyk/task-orchestrator.md).
When should I use Add Component?
Add Component fits situations like: changing an MCP tool; creating a migration; adding a dependency to the version catalog.
How do I install Add Component in Claude Code?
Run `npx skills add jpicklyk/task-orchestrator --skill add-component -a claude-code`. Or copy the skill folder (.claude/skills/add-component in jpicklyk/task-orchestrator) into .claude/skills/add-component in your project. Claude Code loads it when a task matches its description.
How do I install Add Component in Codex?
Run `npx skills add jpicklyk/task-orchestrator --skill add-component -a codex`. Or copy the skill folder (.claude/skills/add-component in jpicklyk/task-orchestrator) into .agents/skills/add-component in your project. Codex loads it when a task matches its description.
Can I use Add Component in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jpicklyk/task-orchestrator --skill add-component -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-component, .gemini/skills/add-component, .github/skills/add-component and .opencode/skills/add-component in your project.
What does Add Component need to run?
SKILL.md names no scripts, command-line tools or credentials: Add Component is instructions for the agent only.
Does Add Component access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Add Component safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Add Component use?
Add Component is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Add Component use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Add Component?
Skills that share tags, products or a category with Add Component: Siyuan MCP Import Migration (yangtaihong59/siyuan-plugins-mcp-sisyphus, 114 stars), Plan Review (KenjiOhtsuka/harmonica, 131 stars), Harmonica Dev (KenjiOhtsuka/harmonica, 131 stars) and Java MCP Server Generator (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Add Component?
jpicklyk (a GitHub user) maintains it in jpicklyk/task-orchestrator, which has 207 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 6, 2026.
Source: jpicklyk/task-orchestrator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.