Borrowing it
Nothing to install: this file belongs to openshift-online/gcp-hcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/openshift-online/gcp-hcp/main/.claude/skills/meeting-notes-to-jira/SKILL.mdgit clone --depth 1 https://github.com/openshift-online/gcp-hcpWrote 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/openshift-online/gcp-hcp/meeting-notes-to-jira)<a href="https://agentmods.dev/skills/openshift-online/gcp-hcp/meeting-notes-to-jira"><img src="https://agentmods.dev/badge/skills/openshift-online/gcp-hcp/meeting-notes-to-jira/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/openshift-online/gcp-hcp/meeting-notes-to-jira"><img src="https://agentmods.dev/badge/skills/openshift-online/gcp-hcp/meeting-notes-to-jira.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.00040 | $0.02320 |
| Opus 5.5 | $0.00016 | $0.00928 |
| Sonnet 5.5 | $0.00008 | $0.00464 |
| Haiku 4.5 | $0.00004 | $0.00232 |
Grade A, and why
meeting-notes-to-jira scanned grade A with 1 finding 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 14d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**All Jira operations:** Atlassian MCP tools only. Never use curl or REST API calls. How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting Notes to Jira Updates
Process a meeting transcript (typically Gemini-generated markdown from Google Meet) into a reviewed set of Jira updates for the GCP HCP project.
Project: GCP (Google Cloud Platform HCP — Hypershift on GKE) Jira instance: redhat.atlassian.net All Jira operations: Atlassian MCP tools only. Never use curl or REST API calls.
Prerequisites
Before starting, verify:
- Atlassian MCP server is authenticated (
/mcp→ Atlassian → check status) - The user has provided a transcript file path (via
$ARGUMENTSor@file reference) - The provided file is a readable markdown or text file. Do not process binary files, executables, or files outside the user's working directory.
If the MCP server is not authenticated, instruct the user to run /mcp and reauthenticate before proceeding.
Phase 1: Ingest
Read the full transcript file provided by the user. These are typically Gemini-generated markdown files containing both a summary/notes section and a full transcript section.
Extract all Jira-actionable items:
- Fix version changes — tickets moving between milestones (private-preview, public-preview, GA, future-consideration)
- Comments to add — meeting discussion context to capture on specific tickets
- Title or description updates — when meeting decisions make existing card content inaccurate (e.g., scope changed, milestone reference is stale)
- New tickets to create — new features, initiatives, epics, or tasks identified during the meeting
- Bulk field operations — systematic field changes agreed upon for multiple tickets
- Consolidation actions — tickets identified as overlapping or duplicate
Accuracy rule: When a discussion covers multiple goals, decisions, or viewpoints, extract all of them — do not distill to the most prominent one. A meeting segment about ARM scope that touches operator tiers, IBM-owned operators, and blocking bugs should produce a comment covering all three, not a single "scope clarified" sentence.
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.
- 14d ago Changed · +11 lines 84c759198a8c
- 2mo ago First seen · 196 lines · 40 tokens per session scan A cde4d27bc442
meeting-notes-to-jira is a skill published in the GitHub repository openshift-online/gcp-hcp (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 40 tokens to every session and 2,320 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.