[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74GRMN0AAWHTEFSW4E17PQ2":3,"skill-same:01M74GRMN0AAWHTEFSW4E17PQ2":47},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M74GRMN0AAWHTEFSW4E17PQ2","clean-stack-traces",null,"Use when the user provides a stack trace, structured exception frames, Keycloak exception JSON, Java frame objects, or similar noisy error output and asks to clean it up, simplify it, make it readable, or format it for copy-paste.","jesperronn\u002Fdotfiles","jesperronn","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6267?v=4","01M74GR60DHXTCHW2MMYYQHFGR","Jesper Rønn-Jensen","01M74GR615DJ290CSGD5CF2Z7Z",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjesperronn\u002Fdotfiles\u002Fblob\u002Fmain\u002Flink-dir\u002F.agents\u002Fskills\u002Fclean-stack-traces\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: clean-stack-traces\ngroup: writing-format\nsummary: \"Condenses noisy exception-frame data into a readable, copy-pasteable stack trace.\"\ndescription: Use when the user provides a stack trace, structured exception frames, Keycloak exception JSON, Java frame objects, or similar noisy error output and asks to clean it up, simplify it, make it readable, or format it for copy-paste.\n---\n\n# Clean Stack Traces\n\nConvert noisy Java exception data into a compact stack trace that preserves the useful execution path without inventing details.\n\n## Output contract\n\nWhen the user asks for copy-pasteable output, return exactly one fenced `text` block and no surrounding explanation.\n\nUse this order:\n\n1. Exception type, if supplied or unambiguously inferable.\n2. Exception message.\n3. The first 2–5 frames, prioritizing application\u002Fproject frames.\n4. A blank line and `... N frames omitted ...` when frames were removed.\n5. The last 1–3 frames, retaining the thread\u002Fruntime boundary.\n\nUse standard Java notation:\n\n```text\nat fully.qualified.Class.method(File.java:line)\n```\n\nFor frames without a line number, omit the location rather than guessing it. Preserve nested-class `$` names. Use `Unknown source` only when the input explicitly says so.\n\n## Selecting frames\n\n- Treat the input order as stack order unless the input identifies a cause chain.\n- Keep the first application frames intact; these usually locate the defect.\n- Keep the final runtime frames intact; these show the request\u002Fthread boundary.\n- Remove repetitive framework plumbing from the middle.\n- Count omitted frames accurately. If the count is uncertain, use `... frames omitted ...` without a number.\n- Do not add a cause, exception type, or diagnosis that is not present in the input.\n\nIf the input contains structured fields such as `class`, `method`, and `line`, transform each field mechanically. Do not include the JSON objects in the cleaned result.\n\n## Exception type handling\n\nOnly label an exception as `NoSuchMethodError` when the input explicitly supplies that type or the surrounding data clearly identifies it. A message such as:\n\n```text\njava.lang.Boolean org.keycloak.models.IdentityProviderModel.isHideOnLogin()\n```\n\nis a method-signature message, not by itself proof of the exception type. If no type is supplied, begin with the message instead of inventing `NoSuchMethodError`.\n\n## Example\n\nInput: structured frames with application frames followed by framework\u002Fruntime frames, plus a method-signature message.\n\nOutput shape:\n\n```text\n\u003Cexception type, if provided>:\n  \u003Cmessage>\n\nat \u003Cfirst application frame>\nat \u003Cnext application frame>\nat \u003Cremaining selected first frames>\n\n... \u003Cnumber> frames omitted ...\n\nat \u003Cselected final runtime frame>\nat \u003Clast runtime frame>\n```\n\n## Common mistakes\n\n- Do not explain the likely root cause when the request is only for cleaned output.\n- Do not preserve every repetitive framework frame.\n- Do not use `... 15 more` unless exactly 15 frames were omitted.\n- Do not turn a method-signature message into a definitive exception type.\n- Do not put prose before or after the code fence when copy-paste output was requested.\n\n","# Clean Stack Traces\n\nConvert noisy Java exception data into a compact stack trace that preserves the useful execution path without inventing details.\n\n## Output contract\n\nWhen the user asks for copy-pasteable output, return exactly one fenced `text` block and no surrounding explanation.\n\nUse this order:\n\n1. Exception type, if supplied or unambiguously inferable.\n2. Exception message.\n3. The first 2–5 frames, prioritizing application\u002Fproject frames.\n4. A blank line and `... N frames omitted ...` when frames were removed.\n5. The last 1–3 frames, retaining the thread\u002Fruntime boundary.\n\nUse standard Java notation:\n\n```text\nat fully.qualified.Class.method(File.java:line)\n```\n\nFor frames without a line number, omit the location rather than guessing it. Preserve nested-class `$` names. Use `Unknown source` only when the input explicitly says so.\n\n## Selecting frames\n\n- Treat the input order as stack order unless the input identifies a cause chain.\n- Keep the first application frames intact; these usually locate the defect.\n- Keep the final runtime frames intact; these show the request\u002Fthread boundary.\n- Remove repetitive framework plumbing from the middle.\n- Count omitted frames accurately. If the count is uncertain, use `... frames omitted ...` without a number.\n- Do not add a cause, exception type, or diagnosis that is not present in the input.\n\nIf the input contains structured fields such as `class`, `method`, and `line`, transform each field mechanically. Do not include the JSON objects in the cleaned result.\n\n## Exception type handling\n\nOnly label an exception as `NoSuchMethodError` when the input explicitly supplies that type or the surrounding data clearly identifies it. A message such as:\n\n```text\njava.lang.Boolean org.keycloak.models.IdentityProviderModel.isHideOnLogin()\n```\n\nis a method-signature message, not by itself proof of the exception type. If no type is supplied, begin with the message instead of inventing `NoSuchMethodError`.\n\n## Example\n\nInput: structured frames with application frames followed by framework\u002Fruntime frames, plus a method-signature message.\n\nOutput shape:\n\n```text\n\u003Cexception type, if provided>:\n  \u003Cmessage>\n\nat \u003Cfirst application frame>\nat \u003Cnext application frame>\nat \u003Cremaining selected first frames>\n\n... \u003Cnumber> frames omitted ...\n\nat \u003Cselected final runtime frame>\nat \u003Clast runtime frame>\n```\n\n## Common mistakes\n\n- Do not explain the likely root cause when the request is only for cleaned output.\n- Do not preserve every repetitive framework frame.\n- Do not use `... 15 more` unless exactly 15 frames were omitted.\n- Do not turn a method-signature message into a definitive exception type.\n- Do not put prose before or after the code fence when copy-paste output was requested.\n\n",{"name":5,"group":24,"summary":25,"description":7},"writing-format","Condenses noisy exception-frame data into a readable, copy-pasteable stack trace.","main","c1d43fc3463eca86b9221288c8b29805891ae792","link-dir\u002F.agents\u002Fskills\u002Fclean-stack-traces","https:\u002F\u002Fgithub.com\u002Fjesperronn\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Fjesperronn","http:\u002F\u002Fjustaddwater.dk\u002F","2026-11-14 15:24:38",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add jesperronn\u002Fdotfiles --skill clean-stack-traces",{"tool":39,"command":40},"bunx","bunx skills add jesperronn\u002Fdotfiles --skill clean-stack-traces",{"tool":42,"command":43},"pnpm","pnpm dlx skills add jesperronn\u002Fdotfiles --skill clean-stack-traces","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjesperronn\u002Fdotfiles\u002Fblob\u002Fmain\u002Flink-dir\u002F.agents\u002Fskills\u002Fclean-stack-traces\u002FSKILL.md",true,[],[48,56,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M76CVMYE4MRKSWGZMZJQP3WY","maintainer-workflow-commands","Use when adding or auditing project commands for setup, development, tests, lint, dependencies, troubleshooting, or releases, and when making those commands discoverable through bin\u002Fworkflows.","https:\u002F\u002Fgithub.com\u002Fjesperronn\u002Fdotfiles\u002Fblob\u002Fmain\u002Flink-dir\u002F.agents\u002Fskills\u002Fmaintainer-workflow-commands\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M74GVPPNXZTYFS5C0KJ59GE8","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fjesperronn\u002Fdotfiles\u002Fblob\u002Fmain\u002Flink-dir\u002F.agents\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M74GVKHYF7RFF60C8JHP68FH","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fjesperronn\u002Fdotfiles\u002Fblob\u002Fmain\u002Flink-dir\u002F.agents\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M74GVF4BCHZ1HQ4Y61P72T07","wrap-up","Scan the current conversation and produce a structured session close-out: deferred items, open questions, decisions made, and the single clearest next action. Ends with a ready-to-paste \"next session opener\" prompt. Use this skill whenever the user says \"\u002Fwrap-up\", \"\u002Fdeferred\", \"wrap up this session\", \"what did we defer\", \"what's left\", \"end of session summary\", or asks what to pick up next time.","https:\u002F\u002Fgithub.com\u002Fjesperronn\u002Fdotfiles\u002Fblob\u002Fmain\u002Flink-dir\u002F.agents\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M74GVBMXJYHWN3KJPWZAR2A5","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fjesperronn\u002Fdotfiles\u002Fblob\u002Fmain\u002Flink-dir\u002F.agents\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M74GV9C16Z8YB6R6TK2AVCCJ","using-superpowers","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002Fjesperronn\u002Fdotfiles\u002Fblob\u002Fmain\u002Flink-dir\u002F.agents\u002Fskills\u002Fusing-superpowers\u002FSKILL.md",[],[]]