-
Notifications
You must be signed in to change notification settings - Fork 0
Skill
A packaged skill (yamtrack-mcp-workflow) that provides ready-to-use workflows on top of the Yamtrack MCP server. It is meant for AI assistants that connect to Yamtrack over MCP.
All skill files live in the repo under src/yamtrack_mcp/skill/:
src/yamtrack_mcp/skill/
├── SKILL.md # this skill's instructions
├── yamtrack.skill # skill manifest (name, version, files)
├── mcp_config.json # stdio launch config example
├── references/ # tool schemas (mcp_tools.md)
└── scripts/ # validation + workflow scripts
├── mcp_client.py
├── mcp_introspector.py
├── mcp_smoke_test.py
└── workflows/
├── research_and_track.py
└── batch_stats.py
The skill is not deployed with the container; it is consumed by the assistant's skill loader from the source tree.
The MCP server must be reachable (Streamable HTTP at /mcp, or stdio via run_mcp). See MCP for transports and authentication.
Searches external providers for a query and, if the item is not already tracked, starts tracking it in Planning status.
from skill.scripts.workflows.research_and_track import research_and_track
await research_and_track("Dune")Aggregates statistics across one or more date ranges for comparison.
from skill.scripts.workflows.batch_stats import get_stats_range
stats = await get_stats_range(start_date="2025-01-01", end_date="2025-12-31")The workflows call the MCP tools documented in MCP: search_media, get_details, create_entry, get_statistics, and others.
The scripts/ folder also holds HTTP validation helpers that hit the running container (they do not mutate it):
-
mcp_client.py— minimal Streamable HTTP client. -
mcp_introspector.py— dumps tool schemas tointrospection.json. -
mcp_smoke_test.py— smoke test; readsYAMTRACK_JWTfrom the environment.