[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M698V5W40C7545QX9RS11B49":3,"skill-same:01M698V5W40C7545QX9RS11B49":121},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":53,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M698V5W40C7545QX9RS11B49","knowledge-correct",null,"Correct or withdraw specific saved Knowledge claims, explicit relationships, or pages at the user's request, preserving provenance and inspecting affected knowledge. Use for “that's wrong”, “retract that”, or a Knowledge chat reference; not automatic contradiction resolution or physical erasure.","openclaw\u002Fopenclaw","openclaw","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252820863?v=4","01M698P3FSAZ6B4R928ZF19KPT","01M698PDMDRVH56MV30D253NFP",394302,"MIT","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fextensions\u002Fknowledge\u002Fskills\u002Fknowledge-correct\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"knowledge","correct","knowledge correct","physical","automatic","request","Wrong","for","claims","at","saved","affected","pages","resolution","withdraw","chat","relationships","reference","use","provenance","2026-11-10 10:12:30",false,"---\nname: knowledge-correct\ndescription: Correct or withdraw specific saved Knowledge claims, explicit relationships, or pages at the user's request, preserving provenance and inspecting affected knowledge. Use for “that's wrong”, “retract that”, or a Knowledge chat reference; not automatic contradiction resolution or physical erasure.\n---\n\n# Correct saved knowledge through agent tools\n\nRead [shared conventions](references\u002Fconventions.md) and\n[publication](references\u002Fpublication.md) before writes.\n\n## Identify the owning record\n\nUse a supplied structured record\u002Fclaim ID and revision as the primary target,\nnot just its display label. Read `knowledge_record` with metadata and evidence;\nconfirm its current revision\u002Fhash. A referenced revision that changed requires\nrereading and reconciling the request, not silently acting on a new assertion.\nWithout an exact reference, use lookup\u002Fsearch, inspect candidates, and ask only\nwhen the requested target or correction remains materially ambiguous.\n\nDistinguish an erroneous saved assertion from an unsupported answer, conflicting\nsource statements, and a fact that changed over time. Contradiction alone does\nnot authorize supersession; the one non-user case is a standing statement its own\nholder explicitly replaced, per publication. Do not manufacture a stored “guard fact” when no\nrecord exists or treat a retraction as evidence for its opposite.\n\n## Apply the right operation\n\n- **Claim or explicit relationship correction:** call `knowledge_correct` with\n  the exact ID, observed `expectedRevision` and `expectedHash`, reason, observed\n  vault UUID and ontology fingerprint, and a complete `replacement` of the same\n  `kind`. Replacement fields use the create-claim\u002Fcreate-relationship contract;\n  there is one outer request ID, not a second replacement request. Preserve\n  supported context, attribution, precise dates and evidence; remove or revise\n  what the correction actually changes. The operation publishes the replacement\n  and supersedes the old assertion together, with links in both directions.\n- **Replaced by a claim that already exists:** call `knowledge_supersede` with\n  the existing claim as `by` and the earlier claims' fences in `superseded`\n  instead of correcting, which would write a duplicate of the replacement. The\n  claims must share a linked page. Undo a mistaken supersession with the same\n  call and `undo: true`.\n- **Withdrawal without a replacement:** call `knowledge_withdraw` with the\n  exact ID, revision\u002Fhash, reason and vault UUID. It accepts pages, claims and\n  explicit relationships. An edge is identified by its own ID, not its endpoint\n  pair. It preserves original evidence\u002Fhistory and is not file deletion.\n- **Page prose correction:** use ordinary revision-fenced `knowledge_save_page`,\n  preserving unrelated authored material and sources. Page corrections are\n  revisions, not replacement entity identities.\n- **Two pages for one entity:** call `knowledge_merge` with the surviving page,\n  the duplicate, both pages' current revision\u002Fhash and a reason. Keep the page\n  with the fuller identity (real name, more connections) as the survivor; pass\n  `title` to rename it and `body` when the combined page should say more than\n  the survivor's current prose. The duplicate's ID, title, aliases, claims,\n  relationships and links then resolve to the survivor; nothing is corrected one\n  by one. Undo a mistaken merge with `knowledge_unmerge`.\n\nAn explicit user correction can supply evidence: retain their exact statement\nwith `knowledge_attach`, attribute it to the user, and reference its verified\nlocator. Use `assertion_origin: user_belief` to distinguish a user assertion from\nan independently sourced statement; do not claim documentary verification.\nAgent inference still needs retained premise evidence, not an invented quote.\n\n## Resolve a handle or mistaken identity\n\nUse `knowledge-entities` to find and read the handle profile, the established\nperson and their connected records. Retain the user's exact identification as\nevidence. Update supported aliases and identity context on the existing pages;\npreserve unrelated content and describe the connection to the established person.\nUse that person's existing ID for future enrichment. When the handle already has\nits own page, merge it into the established person's page with `knowledge_merge`\ninstead of writing a pointer page, withdrawing it, or correcting its claims one by\none. Merge only on identity evidence (the user's statement, a self-introduction, a\nshared stable account ID), never on name similarity; `knowledge_diagnostics`\n`mergeCandidates` lists pages to check, not pages to merge. Retain the identity\nevidence with `knowledge_attach` and pass it as `evidence`.\n\nInspect affected prose, claims and relationships, including source notes, within the correction\nscope. Correct mistaken attribution and unresolved identity where the new evidence\nsupports it, using the page\u002Fassertion operations above; preserve source labels,\nverbatim quotes, event dates and correction provenance. A confirmed author identity\ndoes not independently verify that author's factual claims.\n\nChanges go through these tools, not manual Markdown edits, browser forms, SQL,\nor separate “create then withdraw” calls. No additional approval ritual applies\nto an unambiguous user-authorized correction. Follow publication retry\u002Fconflict\nhandling; a receipt in accepted\u002Fconflict state is not a completed repair.\n\n## Inspect propagation and report honestly\n\nThe receipt's `impact.items` identifies known scoped direct\u002Ftransitive dependents\nat acceptance. It does not update them. Read affected records by exact ID and\ninspect their evidence. Repair only supported changes within the request's scope;\ndo not blindly replace dependency IDs or source quotes with the new claim.\nRecords depending on an inactive assertion are withheld from current discovery\nuntil repaired; exact record\u002Fhistory inspection remains available.\n\nSearch for plausible prose copies as a supplementary check. Search misses,\nunlinked prose, hidden scopes and incomplete indexes prevent a universal “all\ncopies fixed” promise. Do not alter unrelated memory or identity systems as an\nautomatic consequence of a Knowledge correction.\n\nRead back the original and replacement (or withdrawn target), verify lifecycle\nand evidence, and verify current lookup excludes the old assertion. Reply with\nthe receipt\u002Frequest ID, affected record IDs, the correction\u002Fretraction reason,\nand repaired versus unresolved dependencies. Mention retained history only when\nrelevant; never promise erasure from originals, exports or backups.\n","# Correct saved knowledge through agent tools\n\nRead [shared conventions](references\u002Fconventions.md) and\n[publication](references\u002Fpublication.md) before writes.\n\n## Identify the owning record\n\nUse a supplied structured record\u002Fclaim ID and revision as the primary target,\nnot just its display label. Read `knowledge_record` with metadata and evidence;\nconfirm its current revision\u002Fhash. A referenced revision that changed requires\nrereading and reconciling the request, not silently acting on a new assertion.\nWithout an exact reference, use lookup\u002Fsearch, inspect candidates, and ask only\nwhen the requested target or correction remains materially ambiguous.\n\nDistinguish an erroneous saved assertion from an unsupported answer, conflicting\nsource statements, and a fact that changed over time. Contradiction alone does\nnot authorize supersession; the one non-user case is a standing statement its own\nholder explicitly replaced, per publication. Do not manufacture a stored “guard fact” when no\nrecord exists or treat a retraction as evidence for its opposite.\n\n## Apply the right operation\n\n- **Claim or explicit relationship correction:** call `knowledge_correct` with\n  the exact ID, observed `expectedRevision` and `expectedHash`, reason, observed\n  vault UUID and ontology fingerprint, and a complete `replacement` of the same\n  `kind`. Replacement fields use the create-claim\u002Fcreate-relationship contract;\n  there is one outer request ID, not a second replacement request. Preserve\n  supported context, attribution, precise dates and evidence; remove or revise\n  what the correction actually changes. The operation publishes the replacement\n  and supersedes the old assertion together, with links in both directions.\n- **Replaced by a claim that already exists:** call `knowledge_supersede` with\n  the existing claim as `by` and the earlier claims' fences in `superseded`\n  instead of correcting, which would write a duplicate of the replacement. The\n  claims must share a linked page. Undo a mistaken supersession with the same\n  call and `undo: true`.\n- **Withdrawal without a replacement:** call `knowledge_withdraw` with the\n  exact ID, revision\u002Fhash, reason and vault UUID. It accepts pages, claims and\n  explicit relationships. An edge is identified by its own ID, not its endpoint\n  pair. It preserves original evidence\u002Fhistory and is not file deletion.\n- **Page prose correction:** use ordinary revision-fenced `knowledge_save_page`,\n  preserving unrelated authored material and sources. Page corrections are\n  revisions, not replacement entity identities.\n- **Two pages for one entity:** call `knowledge_merge` with the surviving page,\n  the duplicate, both pages' current revision\u002Fhash and a reason. Keep the page\n  with the fuller identity (real name, more connections) as the survivor; pass\n  `title` to rename it and `body` when the combined page should say more than\n  the survivor's current prose. The duplicate's ID, title, aliases, claims,\n  relationships and links then resolve to the survivor; nothing is corrected one\n  by one. Undo a mistaken merge with `knowledge_unmerge`.\n\nAn explicit user correction can supply evidence: retain their exact statement\nwith `knowledge_attach`, attribute it to the user, and reference its verified\nlocator. Use `assertion_origin: user_belief` to distinguish a user assertion from\nan independently sourced statement; do not claim documentary verification.\nAgent inference still needs retained premise evidence, not an invented quote.\n\n## Resolve a handle or mistaken identity\n\nUse `knowledge-entities` to find and read the handle profile, the established\nperson and their connected records. Retain the user's exact identification as\nevidence. Update supported aliases and identity context on the existing pages;\npreserve unrelated content and describe the connection to the established person.\nUse that person's existing ID for future enrichment. When the handle already has\nits own page, merge it into the established person's page with `knowledge_merge`\ninstead of writing a pointer page, withdrawing it, or correcting its claims one by\none. Merge only on identity evidence (the user's statement, a self-introduction, a\nshared stable account ID), never on name similarity; `knowledge_diagnostics`\n`mergeCandidates` lists pages to check, not pages to merge. Retain the identity\nevidence with `knowledge_attach` and pass it as `evidence`.\n\nInspect affected prose, claims and relationships, including source notes, within the correction\nscope. Correct mistaken attribution and unresolved identity where the new evidence\nsupports it, using the page\u002Fassertion operations above; preserve source labels,\nverbatim quotes, event dates and correction provenance. A confirmed author identity\ndoes not independently verify that author's factual claims.\n\nChanges go through these tools, not manual Markdown edits, browser forms, SQL,\nor separate “create then withdraw” calls. No additional approval ritual applies\nto an unambiguous user-authorized correction. Follow publication retry\u002Fconflict\nhandling; a receipt in accepted\u002Fconflict state is not a completed repair.\n\n## Inspect propagation and report honestly\n\nThe receipt's `impact.items` identifies known scoped direct\u002Ftransitive dependents\nat acceptance. It does not update them. Read affected records by exact ID and\ninspect their evidence. Repair only supported changes within the request's scope;\ndo not blindly replace dependency IDs or source quotes with the new claim.\nRecords depending on an inactive assertion are withheld from current discovery\nuntil repaired; exact record\u002Fhistory inspection remains available.\n\nSearch for plausible prose copies as a supplementary check. Search misses,\nunlinked prose, hidden scopes and incomplete indexes prevent a universal “all\ncopies fixed” promise. Do not alter unrelated memory or identity systems as an\nautomatic consequence of a Knowledge correction.\n\nRead back the original and replacement (or withdrawn target), verify lifecycle\nand evidence, and verify current lookup excludes the old assertion. Reply with\nthe receipt\u002Frequest ID, affected record IDs, the correction\u002Fretraction reason,\nand repaired versus unresolved dependencies. Mention retained history only when\nrelevant; never promise erasure from originals, exports or backups.\n",{"name":5,"description":7},"main","f1c93577085244aa96aa87b53a2df9b59d293bd7","extensions\u002Fknowledge\u002Fskills\u002Fknowledge-correct",82862,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw","https:\u002F\u002Fopenclaw.ai","https:\u002F\u002Fgithub.com\u002Fopenclaw","Your personal, open source AI assistant.","2026-11-11 08:46:30",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add openclaw\u002Fopenclaw --skill knowledge-correct",{"tool":63,"command":64},"bunx","bunx skills add openclaw\u002Fopenclaw --skill knowledge-correct",{"tool":66,"command":67},"pnpm","pnpm dlx skills add openclaw\u002Fopenclaw --skill knowledge-correct","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fextensions\u002Fknowledge\u002Fskills\u002Fknowledge-correct\u002FSKILL.md",true,[71,77,81,85,89,93,97,101,105,109,113,117],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fassertions.md","REFERENCE","参考文档",4745,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fextensions\u002Fknowledge\u002Fskills\u002Fknowledge-correct\u002Freferences\u002Fassertions.md",{"path":78,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fconventions.md",14676,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fextensions\u002Fknowledge\u002Fskills\u002Fknowledge-correct\u002Freferences\u002Fconventions.md",{"path":82,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fidentity.md",4903,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fextensions\u002Fknowledge\u002Fskills\u002Fknowledge-correct\u002Freferences\u002Fidentity.md",{"path":86,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fmeeting-entity-example.md",6838,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fextensions\u002Fknowledge\u002Fskills\u002Fknowledge-correct\u002Freferences\u002Fmeeting-entity-example.md",{"path":90,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fprofiles.md",5775,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fextensions\u002Fknowledge\u002Fskills\u002Fknowledge-correct\u002Freferences\u002Fprofiles.md",{"path":94,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fpublication.md",22868,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fextensions\u002Fknowledge\u002Fskills\u002Fknowledge-correct\u002Freferences\u002Fpublication.md",{"path":98,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fpublish.md",5259,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fextensions\u002Fknowledge\u002Fskills\u002Fknowledge-correct\u002Freferences\u002Fpublish.md",{"path":102,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Frecovery.md",1998,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fextensions\u002Fknowledge\u002Fskills\u002Fknowledge-correct\u002Freferences\u002Frecovery.md",{"path":106,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fsetup.md",1788,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fextensions\u002Fknowledge\u002Fskills\u002Fknowledge-correct\u002Freferences\u002Fsetup.md",{"path":110,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fsources.md",3108,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fextensions\u002Fknowledge\u002Fskills\u002Fknowledge-correct\u002Freferences\u002Fsources.md",{"path":114,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fverify.md",2743,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fextensions\u002Fknowledge\u002Fskills\u002Fknowledge-correct\u002Freferences\u002Fverify.md",{"path":118,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":119,"sourceHtmlUrl":120},"references\u002Fwriting.md",1958,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fextensions\u002Fknowledge\u002Fskills\u002Fknowledge-correct\u002Freferences\u002Fwriting.md",[122,128,150,168,190,212],{"skillNo":123,"name":124,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":43},"01M698VP84FNM6G9MR1HPX7MF7","lobster","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fextensions\u002Flobster\u002FSKILL.md",[],[124],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":43},"01M698YY8QGQ7S8TJNKJG6VTPH","xurl","xurl CLI for authenticated X posts, replies, reads\u002Fsearch, DMs, media upload, followers, auth status, or raw v2 API calls.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Fxurl\u002FSKILL.md",[],[130,30,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149],"api","calls","replies","posts","upload","tap","install","brew","node","Media","search","npm","status","auth","cli",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":43},"01M698YWT1CJ0WK88WB909R9RT","weather","Current weather and forecasts with web_fetch, falling back to wttr.in curl for locations, rain, temperature, travel planning.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Fweather\u002FSKILL.md",[],[152,157,158,141,159,142,160,161,162,163,164,165,30,166,167],"travel planning","travel","fetch","curl","https","help","planning","web","back","temperature","with",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":179,"publishedAt":43},"01M698YV2Q0R0JJKAWGFS21K0N","visualize","Create inline visuals for code and explanations, or author persistent OpenClaw dashboard widgets with show_widget.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Fvisualize\u002FSKILL.md",[174],{"categoryNo":175,"categoryName":176,"taxonomyType":177,"taxonomyTypeDesc":178},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[170,180,181,182,183,30,167,184,185,186,187,188,9,189],"widgets","openclaw dashboard","author","inline","show","code","create","visuals","dashboard","widget",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":202,"publishedAt":43},"01M698YS2TRJH9ENG28HD9CD87","trello","Manage Trello boards, lists, and cards via the Trello REST API.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Ftrello\u002FSKILL.md",[196,199],{"categoryNo":197,"categoryName":198,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":200,"categoryName":201,"taxonomyType":177,"taxonomyTypeDesc":178},"01JBSEEDCAT000000000000030","开发工程师",[192,161,203,204,205,206,207,208,141,142,209,160,135,210,211],"cloud","manage","via","rest api","token","atlassian","jq","REST","developer",{"skillNo":213,"name":214,"nameZh":6,"description":215,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":216,"categories":217,"keywords":218,"publishedAt":43},"01M698YQ9Q3M4W78EWV2KSCSVW","tmux","Control tmux sessions\u002Fpanes for interactive CLIs: list, capture output, send keys, paste text, monitor prompts.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fopenclaw\u002Fblob\u002Fmain\u002Fskills\u002Ftmux\u002FSKILL.md",[],[214,141,219,220,30,221,222,223,224,225,226,227,142,228,229,230,231,232,233],"send","darwin","keys","paste","output","control","prompts","interactive","list","capture","panes","text","monitor","sessions","linux"]