Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add hieptran87/atlassian-mcp-server --skill capture-tasks-from-meeting-notesgit clone --depth 1 https://github.com/hieptran87/atlassian-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/hieptran87/atlassian-mcp-server/capture-tasks-from-meeting-notes)<a href="https://agentmods.dev/skills/hieptran87/atlassian-mcp-server/capture-tasks-from-meeting-notes"><img src="https://agentmods.dev/badge/skills/hieptran87/atlassian-mcp-server/capture-tasks-from-meeting-notes/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hieptran87/atlassian-mcp-server/capture-tasks-from-meeting-notes"><img src="https://agentmods.dev/badge/skills/hieptran87/atlassian-mcp-server/capture-tasks-from-meeting-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00098 | $0.03752 |
| Opus 5 | $0.00049 | $0.01876 |
| Sonnet 5 | $0.00020 | $0.00750 |
| Haiku 4.5 | $0.00010 | $0.00375 |
Grade A, and why
capture-tasks-from-meeting-notes scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
91% identical to capture-tasks-from-meeting-notes — 106 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 672 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capture Tasks from Meeting Notes
Keywords
meeting notes, action items, create tasks, create tickets, extract tasks, parse notes, analyze notes, assigned work, assignees, from meeting, post-meeting, capture tasks, generate tasks, turn into tasks, convert to tasks, action item, to-do, task list, follow-up, assigned to, create Jira tasks, create Jira tickets, meeting action items, extract action items, find action items, analyze meeting
Overview
Automatically extract action items from meeting notes and create Jira tasks with proper assignees. This skill parses unstructured meeting notes (from Confluence or pasted text), identifies action items with assignees, looks up Jira account IDs, and creates tasks—eliminating the tedious post-meeting ticket creation process.
Use this skill when: Users have meeting notes with action items that need to become Jira tasks.
Workflow
Follow this 7-step process to turn meeting notes into actionable Jira tasks:
Step 1: Get Meeting Notes
Obtain the meeting notes from the user.
Option A: Confluence Page URL
If user provides a Confluence URL:
confluence_get_page(
page_id="[extracted from URL]"
)
URL patterns:
https://[site].atlassian.net/wiki/spaces/[SPACE]/pages/[PAGE_ID]/[title]- Extract PAGE_ID from the numeric portion
Option B: Pasted Text
If user pastes meeting notes directly:
- Use the text as-is
- No fetching needed
If Unclear
Ask: "Do you have a Confluence link to the meeting notes, or would you like to paste them directly?"
Step 2: Parse Action Items
Scan the notes for action items with assignees.
Common Patterns
Pattern 1: @mention format (highest priority)
@Sarah to create user stories for chat feature
@Mike will update architecture doc
Pattern 2: Name + action verb
Sarah to create user stories
Mike will update architecture doc
Lisa should review the mockups
Pattern 3: Action: Name - Task
Action: Sarah - create user stories
Action Item: Mike - update architecture
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 672 lines · 98 tokens per session scan A 790146da8cec
capture-tasks-from-meeting-notes is a skill published in the GitHub repository hieptran87/atlassian-mcp-server (0 stars, last pushed 1mo ago), licensed MIT. It adds 98 tokens to every session and 3,752 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to capture-tasks-from-meeting-notes, differing in 106 lines, and is treated as a copy.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.