[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D36FNBAADC939FTQ9YRNQN":3,"skill-same:01M7D36FNBAADC939FTQ9YRNQN":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7D36FNBAADC939FTQ9YRNQN","log-worklogs",null,"Log Tempo timesheet entries to Jira worklogs from a freeform bullet list. Use when the user asks to log Tempo hours, post worklogs, add time to Jira, log time for yesterday\u002Ftoday\u002F\u003Cdate>, update their daily timesheet, or pastes a list of `> TICKET-KEY :: Nh` blocks. Also trigger on phrases like \"log my tempo hours\", \"post my hours\", \"add worklog for \u003CTICKET>\", \"log time for \u003Cdate>\".","rabihkodeih\u002Fagentic-workflow","rabihkodeih","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1883033?v=4","01M7D357MHZJG4N8PQV8R5TZ82","Rabih Kodeih","01M7D357NM3WD86XTZ93FV7DNK",0,"MIT","https:\u002F\u002Fgithub.com\u002Frabihkodeih\u002Fagentic-workflow\u002Fblob\u002Fmain\u002Fskills\u002Flog-worklogs\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: log-worklogs\ndescription: 'Log Tempo timesheet entries to Jira worklogs from a freeform bullet list. Use when the user asks to log Tempo hours, post worklogs, add time to Jira, log time for yesterday\u002Ftoday\u002F\u003Cdate>, update their daily timesheet, or pastes a list of `> TICKET-KEY :: Nh` blocks. Also trigger on phrases like \"log my tempo hours\", \"post my hours\", \"add worklog for \u003CTICKET>\", \"log time for \u003Cdate>\".'\nallowed-tools: mcp__plugin_atlassian_atlassian__addWorklogToJiraIssue, mcp__plugin_atlassian_atlassian__getJiraIssue, Bash\n---\n\n# Log worklogs\n\nParse a freeform list of ticket entries with hours and bullets, then post each one as a Jira worklog via the Atlassian MCP plugin. Tempo reads Jira worklogs directly, so they appear in the Tempo timesheet automatically , **never use a browser or the Tempo UI** (the Connect iframe makes it painfully slow).\n\n## Input format\n\nThe user pastes blocks like:\n\n```\n> TICKET-KEY :: \u003Cduration>\n    (optional header line, e.g. \"Catch-up \u002F Planning\")\n    - bullet 1\n    - bullet 2\n        - nested sub-bullet\n        - another sub-bullet\n\n> ANOTHER-KEY :: \u003Cduration>\n    - bullet\n```\n\n- Duration accepts Jira time format: `Nh`, `Nm`, `N.Nh`, `Nh Nm`, `0.5h`, etc.\n- Description = every indented line after the `> ... ::` line, up to the next `>` or blank line.\n- Copy description text **verbatim**. Do not reword, summarize, or strip leading `(...)` headers. Bullets stay bullets.\n- **Preserve bullet nesting.** Bullets indented deeper than their siblings are sub-bullets , keep their relative indentation so they render as nested sublists, not flattened to a single level.\n\n## Date resolution\n\nThe user may say \"yesterday\", \"today\", \"Monday\", \"May 13\", or give an explicit date.\n\n- Resolve relative dates against the timezone in **User context** below.\n- Default to **today** if unspecified.\n- If ambiguous (e.g., \"Monday\" with no week context), ask which week before posting.\n\n## Steps\n\n1. **Parse all entries first.** If any block fails to parse, stop and ask the user to clarify before posting *anything* , no partial logging.\n2. **Sanity-check totals.** Sum the durations. If the total exceeds **8h**, surface the breakdown and ask the user to confirm. Could be intentional (overtime) or a typo (e.g., `5h` instead of `0.5h`).\n3. **Validate unknown ticket keys.** For any ticket key that is not in the shorthand list below, call `getJiraIssue` to confirm it exists. If it 404s, stop and ask.\n4. **Duplicate guard (best-effort).** If the user explicitly mentions a past date *and* the bullets look identical to recent ones for the same ticket, flag it before posting. Otherwise proceed , duplicate detection across the full Jira worklog history isn't worth the API cost for the common case.\n5. **Post worklogs in parallel.** In a single message, dispatch all `addWorklogToJiraIssue` calls at once. For each entry:\n   - `cloudId`: the Atlassian site from **User context**\n   - `issueIdOrKey`: the ticket key\n   - `timeSpent`: the parsed duration string (e.g., `1h`, `2h30m`, `0.5h`)\n   - `started`: ISO 8601 with the target date and staggered hours (09:00, 10:00, 11:00, ... UTC) so multiple entries on the same day don't overlap each other on the Tempo timeline\n   - `commentBody`: the description **verbatim** , keep the `(...)` header line if present, keep the bullet markers (`- `) intact, and **preserve the indentation of nested bullets**. Normalize each nesting level to 4 spaces of indentation relative to its parent (strip any trailing whitespace on lines, but never collapse leading indentation that signals nesting).\n   - `contentFormat`: `\"markdown\"` , Jira auto-converts `- ` prefixes into a proper bulletList in ADF, and indented `- ` lines into nested `bulletList`s within their parent `listItem`\n6. **Print a summary table.** After all calls complete:\n\n   ```\n   | Ticket | Hours | Worklog ID |\n   |---|---|---|\n   | ... | ... | ... |\n   | **Total** | **Nh** | |\n   ```\n\n   Then tell the user to refresh the Tempo timesheet to see the entries.\n\n7. **Failure handling.** If any worklog call fails, report which entries succeeded and which failed with the error message. **Do not retry blindly** , ask how to proceed.\n\n## User context (defaults, fill in per person)\n\n- Atlassian site: `\u003Cyourorg>.atlassian.net`\n- Timezone: `\u003CIANA zone the timesheet is kept in, e.g. America\u002FToronto>`\n- Common shorthand keys (skip validation for these):\n  - `TIME-1` → General meetings (not project specific)\n  - `TIME-2` → General non-project work\n  - `PROJ-*` → main product project\n\n## Do NOT\n\n- Use a browser or the Tempo UI. Tempo reads Jira worklogs, so the API is the right path and is ~50× faster.\n- Reword, summarize, or \"clean up\" bullet text. Copy verbatim, including grammar quirks.\n- Flatten nested bullets to a single level. Preserve the indentation hierarchy so sub-bullets stay nested under their parent.\n- Post anything if the parse is incomplete or the daily total looks wrong , ask first.\n- Retry on partial failure , surface what happened, let the user decide.\n- Assume timezone , if the user is in a different TZ for a trip, ask before resolving \"yesterday\u002Ftoday\".\n\n## Example invocation\n\nUser:\n> Please log my tempo hours for yesterday:\n> ```\n> > TIME-2 :: 1h\n>     (Catch-up \u002F Planning)\n>     - reviewed slack\n>     - groomed TODOs\n> > PROJ-1234 :: 3h\n>     - investigated s3 output option\n>     - finalized design doc\n> ```\n\nExpected behavior:\n1. Resolve \"yesterday\" → ISO date in the configured timezone.\n2. Parse 2 entries totaling 4h (under 8h, no confirmation needed).\n3. Skip ticket validation (`TIME-2` and `PROJ-*` are known shorthand).\n4. Dispatch 2 `addWorklogToJiraIssue` calls in parallel with staggered `started` times.\n5. Print summary table; remind user to refresh Tempo.\n","# Log worklogs\n\nParse a freeform list of ticket entries with hours and bullets, then post each one as a Jira worklog via the Atlassian MCP plugin. Tempo reads Jira worklogs directly, so they appear in the Tempo timesheet automatically , **never use a browser or the Tempo UI** (the Connect iframe makes it painfully slow).\n\n## Input format\n\nThe user pastes blocks like:\n\n```\n> TICKET-KEY :: \u003Cduration>\n    (optional header line, e.g. \"Catch-up \u002F Planning\")\n    - bullet 1\n    - bullet 2\n        - nested sub-bullet\n        - another sub-bullet\n\n> ANOTHER-KEY :: \u003Cduration>\n    - bullet\n```\n\n- Duration accepts Jira time format: `Nh`, `Nm`, `N.Nh`, `Nh Nm`, `0.5h`, etc.\n- Description = every indented line after the `> ... ::` line, up to the next `>` or blank line.\n- Copy description text **verbatim**. Do not reword, summarize, or strip leading `(...)` headers. Bullets stay bullets.\n- **Preserve bullet nesting.** Bullets indented deeper than their siblings are sub-bullets , keep their relative indentation so they render as nested sublists, not flattened to a single level.\n\n## Date resolution\n\nThe user may say \"yesterday\", \"today\", \"Monday\", \"May 13\", or give an explicit date.\n\n- Resolve relative dates against the timezone in **User context** below.\n- Default to **today** if unspecified.\n- If ambiguous (e.g., \"Monday\" with no week context), ask which week before posting.\n\n## Steps\n\n1. **Parse all entries first.** If any block fails to parse, stop and ask the user to clarify before posting *anything* , no partial logging.\n2. **Sanity-check totals.** Sum the durations. If the total exceeds **8h**, surface the breakdown and ask the user to confirm. Could be intentional (overtime) or a typo (e.g., `5h` instead of `0.5h`).\n3. **Validate unknown ticket keys.** For any ticket key that is not in the shorthand list below, call `getJiraIssue` to confirm it exists. If it 404s, stop and ask.\n4. **Duplicate guard (best-effort).** If the user explicitly mentions a past date *and* the bullets look identical to recent ones for the same ticket, flag it before posting. Otherwise proceed , duplicate detection across the full Jira worklog history isn't worth the API cost for the common case.\n5. **Post worklogs in parallel.** In a single message, dispatch all `addWorklogToJiraIssue` calls at once. For each entry:\n   - `cloudId`: the Atlassian site from **User context**\n   - `issueIdOrKey`: the ticket key\n   - `timeSpent`: the parsed duration string (e.g., `1h`, `2h30m`, `0.5h`)\n   - `started`: ISO 8601 with the target date and staggered hours (09:00, 10:00, 11:00, ... UTC) so multiple entries on the same day don't overlap each other on the Tempo timeline\n   - `commentBody`: the description **verbatim** , keep the `(...)` header line if present, keep the bullet markers (`- `) intact, and **preserve the indentation of nested bullets**. Normalize each nesting level to 4 spaces of indentation relative to its parent (strip any trailing whitespace on lines, but never collapse leading indentation that signals nesting).\n   - `contentFormat`: `\"markdown\"` , Jira auto-converts `- ` prefixes into a proper bulletList in ADF, and indented `- ` lines into nested `bulletList`s within their parent `listItem`\n6. **Print a summary table.** After all calls complete:\n\n   ```\n   | Ticket | Hours | Worklog ID |\n   |---|---|---|\n   | ... | ... | ... |\n   | **Total** | **Nh** | |\n   ```\n\n   Then tell the user to refresh the Tempo timesheet to see the entries.\n\n7. **Failure handling.** If any worklog call fails, report which entries succeeded and which failed with the error message. **Do not retry blindly** , ask how to proceed.\n\n## User context (defaults, fill in per person)\n\n- Atlassian site: `\u003Cyourorg>.atlassian.net`\n- Timezone: `\u003CIANA zone the timesheet is kept in, e.g. America\u002FToronto>`\n- Common shorthand keys (skip validation for these):\n  - `TIME-1` → General meetings (not project specific)\n  - `TIME-2` → General non-project work\n  - `PROJ-*` → main product project\n\n## Do NOT\n\n- Use a browser or the Tempo UI. Tempo reads Jira worklogs, so the API is the right path and is ~50× faster.\n- Reword, summarize, or \"clean up\" bullet text. Copy verbatim, including grammar quirks.\n- Flatten nested bullets to a single level. Preserve the indentation hierarchy so sub-bullets stay nested under their parent.\n- Post anything if the parse is incomplete or the daily total looks wrong , ask first.\n- Retry on partial failure , surface what happened, let the user decide.\n- Assume timezone , if the user is in a different TZ for a trip, ask before resolving \"yesterday\u002Ftoday\".\n\n## Example invocation\n\nUser:\n> Please log my tempo hours for yesterday:\n> ```\n> > TIME-2 :: 1h\n>     (Catch-up \u002F Planning)\n>     - reviewed slack\n>     - groomed TODOs\n> > PROJ-1234 :: 3h\n>     - investigated s3 output option\n>     - finalized design doc\n> ```\n\nExpected behavior:\n1. Resolve \"yesterday\" → ISO date in the configured timezone.\n2. Parse 2 entries totaling 4h (under 8h, no confirmation needed).\n3. Skip ticket validation (`TIME-2` and `PROJ-*` are known shorthand).\n4. Dispatch 2 `addWorklogToJiraIssue` calls in parallel with staggered `started` times.\n5. Print summary table; remind user to refresh Tempo.\n",{"name":5,"description":7,"allowed-tools":24},"mcp__plugin_atlassian_atlassian__addWorklogToJiraIssue, mcp__plugin_atlassian_atlassian__getJiraIssue, Bash","main","7b05d4ac96431d4dca2179b70d4f124979d4c3a8","skills\u002Flog-worklogs","https:\u002F\u002Fgithub.com\u002Frabihkodeih\u002Fagentic-workflow","https:\u002F\u002Fgithub.com\u002Frabihkodeih","2026-09-20 04:17:12",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add rabihkodeih\u002Fagentic-workflow --skill log-worklogs",{"tool":37,"command":38},"bunx","bunx skills add rabihkodeih\u002Fagentic-workflow --skill log-worklogs",{"tool":40,"command":41},"pnpm","pnpm dlx skills add rabihkodeih\u002Fagentic-workflow --skill log-worklogs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frabihkodeih\u002Fagentic-workflow\u002Fblob\u002Fmain\u002Fskills\u002Flog-worklogs\u002FSKILL.md",true,[],[46,53,60,67,74,80],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7D37HNRY0RGK352YT1SYQVH","yes-no","Answer the user's question with a yes or no, optionally followed by a short explanation when the model sees fit. Use when the user types \"\u002Fyes-no\", asks a yes\u002Fno question and wants a decisive answer, or says \"just yes or no\".","https:\u002F\u002Fgithub.com\u002Frabihkodeih\u002Fagentic-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fyes-no\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7D37CDX8K153CYY4FVCGAT5","sonar-workflow","Fix SonarQube code quality issues for a pull request. Auto-fixes trivial issues (formatting, unused imports) and requests approval for complex issues (security, bugs). Integrates with commit-workflow and pr-workflow skills.","https:\u002F\u002Fgithub.com\u002Frabihkodeih\u002Fagentic-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fsonar-workflow\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7D377REEE0MBH7SJ37JWR41","short-answer","Answer the user's question as concisely as possible, a direct, to-the-point response with no preamble, filler, or unnecessary elaboration. Use when the user types \"\u002Fshort-answer\", asks for a brief\u002Fshort\u002Fconcise\u002FTL;DR answer, or says \"just the answer\".","https:\u002F\u002Fgithub.com\u002Frabihkodeih\u002Fagentic-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fshort-answer\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7D371KTYERB0DFG67XE9PTC","redash","Query a Redash instance over its REST API , list data sources and saved queries, read a saved query's SQL, run it, or run ad-hoc read-only SQL and get the rows back. Use when the user asks about Redash, a Redash query\u002Fdashboard\u002Flink, \"run that query\", \"what does query 1234 return\", or wants numbers out of an analytics data source rather than the application DB.","https:\u002F\u002Fgithub.com\u002Frabihkodeih\u002Fagentic-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fredash\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7D36Y5BF600Z6B470W1AFNZ","prod-db-postgres","https:\u002F\u002Fgithub.com\u002Frabihkodeih\u002Fagentic-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fprod-db-postgres\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7D36VE5AEREF874PDV2SJSG","prod-db-mysql-bastion","https:\u002F\u002Fgithub.com\u002Frabihkodeih\u002Fagentic-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fprod-db-mysql-bastion\u002FSKILL.md",[],[]]