ankn
a5f8fb49ab
Bahn: aisupport, Analyse-O2C-C2S, awesome-bahn-mcp-servers, beam-mcp,
Confluence_Bot, db-planet-mcp-server, O2C-Harness, project-audit,
Projekt-KIQ-HP, teamlandkarte-mcp
Dhive: Jury-Voting
Privat: CV, NoteGraph (NOTE: NoteGraph needs complete redo after consolidation)
Shared: AI-Orchestrator, OrgMyLife, power_skills_and_more
Shared/references: symphony (read-only)
Bahn repos remain available as independent remotes - this monorepo
pulls them in via subtree, the originals are untouched.
34 lines
1.2 KiB
Markdown
34 lines
1.2 KiB
Markdown
---
|
|
name: task-discovery
|
|
description: >
|
|
Browse and inspect published tasks from the Teamlandkarte database.
|
|
Use this skill when the user wants to list open tasks, view task details,
|
|
validate task requirements, or infer the primary role for a task.
|
|
---
|
|
|
|
# Task Discovery
|
|
|
|
## Available Operations
|
|
|
|
### List open tasks
|
|
Call `list_open_tasks(limit=20)` to show a table of published tasks with task_id, title, created date, and time range.
|
|
|
|
### View task details
|
|
Call `get_task_details(task_id)` to inspect a specific task's fields (title, description, skills, time range).
|
|
|
|
### Validate task requirements
|
|
Call `validate_task_requirements(task_id)` to compare DB-stored skills vs embedding-inferred skills.
|
|
- Only use when the user explicitly asks for validation
|
|
- This is NOT part of the default matching workflow
|
|
|
|
### Infer primary role
|
|
Call `infer_primary_role(task_id=...)` or `infer_primary_role(task_text=...)` to suggest the closest matching role.
|
|
- Use when the role is unclear before starting a capacity search
|
|
|
|
## Typical Flow
|
|
|
|
1. User asks to see tasks → `list_open_tasks()`
|
|
2. User picks a task → `get_task_details(task_id)`
|
|
3. Optionally validate → `validate_task_requirements(task_id)`
|
|
4. Proceed to capacity matching (use the capacity-matching skill)
|