[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D399YWD4SW4X4SE463B149":3,"skill-same:01M7D399YWD4SW4X4SE463B149":63},{"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":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7D399YWD4SW4X4SE463B149","deprecate",null,"Human-started command: it runs only when the human's message begins with `\u002Fak:deprecate`. On any other request do not load or follow it; tell the human to type that command. Plans and carries out the retirement of a surface other code depends on: the decision, consumer evidence, a notice and migration guide, incremental migration, and a removal held behind its own gate. Use when a human runs \u002Fak:deprecate to sunset an API, a feature, a library or a schema shape. Not for deleting code nothing consumes.","Pibomeister\u002Fagent-kit","Pibomeister","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11633791?v=4","01M7D2NBHEKARMHN9MPV2J80XD","Eduardo Picazo","01M7D2NBJ3Z33SGSYCZ0KBD5DE",0,"MIT","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Fskills\u002Fdeprecate\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: deprecate\ndescription: >-\n  Human-started command: it runs only when the human's message begins with `\u002Fak:deprecate`. On any\n  other request do not load or follow it; tell the human to type that command. Plans and carries out\n  the retirement of a surface other code depends on: the decision, consumer evidence, a notice and\n  migration guide, incremental migration, and a removal held behind its own gate. Use when a human\n  runs \u002Fak:deprecate to sunset an API, a feature, a library or a schema shape. Not for deleting code\n  nothing consumes.\nlicense: MIT\nmetadata:\n  ak_catalog_id: deprecate\n---\n\nPlan and execute an approved retirement or migration with compatibility, sequencing, rollback and\nconsumer evidence. Irreversible steps stay separately gated.\n\n## When to use\n\n- An old API, library, feature or service has a replacement and its consumers need moving.\n- A schema shape must change in production — a rename, a drop, a split — without downtime.\n- Code with active consumers has no owner, and the choice is to invest in it or retire it.\n\n## Not for\n\n- Deleting code nothing consumes and nothing exports. That is cleanup, `simplify`.\n- Building the replacement. A retirement with no working alternative stops here until one exists.\n- Removing anything on the strength of this skill's own invocation. The removal step has its own\n  gate, below.\n- Deciding product direction. Whether a feature should exist is a `strategy` question.\n\n## Authority\n\nAuthority: `explicit`. A human starts this skill with `\u002Fak:deprecate`. It may start model-invoked\nskills only. The invocation authorizes the decision, the notice, the migration plan and the\nconsumer migrations; it does not authorize removal. Removing a public surface is\n`public-contract-change` and dropping data is `destructive-data`: each needs an explicit charter\nentry a human approved up front, naming the action and exactly what is permitted, bound to that\ncharter's hash (ruling `sensitive-actions-need-approved-charter-entry`). An approved deprecation plan\nis not such an entry.\n\n## Inputs\n\n- The surface to retire and its replacement. No replacement: `needs-input`, naming the replacement as\n  work that comes first.\n- Consumer evidence through the knowledgebase adapter's `requestImpactAnalysis`, with its coverage\n  statement. Unavailable: `needs-input`; this skill never substitutes its own guess at a consumer\n  count. A partial graph is a stated limitation, and zero consumers on a partial graph is not zero.\n- Existing decisions for the area, through `readContext`.\n- The system of record for migration tickets, decided by configuration and never by reachability\n  (`adapters\u002Ftracker\u002FCONTRACT.md` §2; ruling `tracker-of-record-falls-back-to-kb`): the bound tracker\n  where the project folder binds one and the project record agrees; the knowledgebase where there is\n  no binding and the record names it or there is no record; `needs-input` otherwise. The chain is\n  in the [tracker-of-record reference pack](..\u002F..\u002Freferences\u002Ftracker-of-record\u002FREFERENCE.md).\n- At the removal step only: the charter (`schemas\u002Fcharter.schema.json`) with its approval bound to\n  its hash. Absent, removal does not happen.\n\n## Workflow\n\n1. **Check how this run was started**, before any other step and before any tool call. It is started\n   only when the human's message begins with `\u002Fak:deprecate`; no grant starts it. A request in prose\n   is not a start, even when it names this skill or the command. Otherwise, stop here: make no tool\n   call, say that this command is human-started, and give the human the line to type,\n   `\u002Fak:deprecate` and their request.\n2. **Decide.** Answer five questions before anything else: does it still provide unique value (then\n   keep it); does a replacement exist (if not, stop); how many consumers depend on it, from the\n   impact analysis; what does each consumer's migration cost; what does keeping it cost.\n3. **Choose advisory or compulsory.** Default to advisory. Compulsory is for a security problem, a\n   blocker or unsustainable upkeep, and it ships migration tooling, not only a deadline.\n4. **Choose a migration pattern** from [the migration patterns](references\u002Fmigration-patterns.md):\n   strangler, adapter, feature flag, or expand and contract for any schema change.\n5. **Publish the plan.** The decision as a proposed `adr`; the notice and migration guide, from\n   [the notice template](assets\u002Fdeprecation-notice.md), as a `process` page; one migration `ticket`\n   per consumer in the system of record, through `createTicket` and `linkRecord`.\n6. **Migrate incrementally.** One consumer at a time: find every touchpoint, move it to the\n   replacement, verify behavior matches, remove its references to the old surface, confirm no\n   regression. The owner of the retiring surface migrates its consumers; announcing and leaving them\n   to it is not migration.\n7. **Stop at the removal checkpoint.** Report the consumers migrated and those remaining. Removal is\n   not the next step of the same pass.\n8. **Remove, only under its gate.** When a charter entry covers the action and a fresh impact\n   analysis with full coverage shows zero active consumers: remove the code, its tests, its\n   configuration and its notices, destructive schema steps last and in their own deploy. The\n   [`pack-delete` pack](..\u002F..\u002Fpacks\u002Fpack-delete\u002FPACK.md) attaches to that diff; it constrains the\n   removal and never starts one.\n\n## Hard gates\n\nGate: no retirement without a working replacement.\n\nGate: no consumer count without the impact analysis. An unavailable or partial analysis is reported,\nnever filled with a guess.\n\nGate: removal needs an approved charter entry for the named action, bound to the charter's hash,\nplus zero active consumers on a fresh, full-coverage analysis. Without both, the run stops before\nremoving anything.\n\nGate: a schema change is never made in place. Additive first; destructive last and alone; every\nmigration has a tested down path.\n\n| The thought | Why it is wrong | Do this instead |\n|---|---|---|\n| \"The plan was approved, so removing the old API finishes the job.\" | Approval of a plan is not a charter entry for `public-contract-change` or `destructive-data` (ruling `sensitive-actions-need-approved-charter-entry`). | Stop at the removal checkpoint and name the entry removal needs. |\n| \"Nobody uses it anymore.\" | Hyrum's law: every observable behavior has a dependent, and a belief is not evidence. | Run the impact analysis and report its coverage. |\n| \"Just rename the column, it's one line.\" | During the rollout old and new code run together, and one queries a column that no longer exists. | Expand and contract; never rename in place. |\n| \"Add the new column and drop the old one in the same migration.\" | That couples a safe add to a destructive drop. | Drops get their own deploy after no code reads the old shape. |\n| \"We'll write the rollback if we need it.\" | A migration with no down path is a deploy you cannot reverse. | Write and run the down path before the migration merges. |\n| \"Consumers will migrate on their own.\" | They will not; the owner of the retiring surface migrates them. | Cut a ticket per consumer and migrate them one at a time. |\n\n## Outputs\n\n- A proposed `adr` for the retirement decision and a `process` page for the notice and migration\n  guide, published through the knowledgebase adapter's `publishArtifact` under `kb-document`\n  placements scoped to the project. The knowledgebase resolves the location; this skill writes no\n  notice or decision file into the working repository (ruling `central-kb-owns-project-artifacts`).\n- One migration `ticket` (`schemas\u002Fticket.schema.json`) per consumer, in the system of record.\n- Consumer migrations in the workspace, verified one at a time, for the lane that owns integration.\n- A removal-checkpoint report: consumers migrated, consumers remaining, the analysis coverage, and\n  the charter entry removal would need.\n\n## Side effects\n\n`workspace-write`, `process-exec`, `scratch-write`, `kb-draft`, `kb-publish`, `tracker-write`,\n`artifact-write`. `artifact-write` is the migration `ticket`s, run artifacts bound to their hash.\nThe removal step is `public-contract-change` or `destructive-data`, and happens only under an\napproved charter entry naming it (ruling `sensitive-actions-need-approved-charter-entry`).\n\n`kb-publish` and `tracker-write` are remote side effects. The idempotency key for each derives from\nthe run, the operation, the record's stable remote identity and the artifact's hash; the read-back is\nthe record the write returns, read before the write and confirmed after it\n(`adapters\u002Frunner-contract\u002FCONTRACT.md`, \"Idempotency\"). A write whose read-back cannot be performed\nis `failed`, never complete.\n\n## Stop conditions\n\n- `complete` — the plan is published, the consumers in scope are migrated, and the run stopped at the\n  removal checkpoint; or, under a covering charter entry, removal is done and verified.\n- `complete` — the decision gate showed the surface still provides unique value; nothing retires.\n- `needs-input` — not started with `\u002Fak:deprecate`, no replacement, no impact analysis, no system of\n  record, or removal requested without a covering charter entry.\n- `failed` — a write's read-back cannot be performed, or a consumer migration broke verification and\n  could not be reverted.\n- `cancelled` — the human withdrew; published records stay, and nothing is removed.\n\n## Limits\n\n- Removal: never in the same pass as migration, and never without a covering charter entry (gate).\n- Consumers migrated at a time: one, verified before the next (gate).\n- Advisory by default; compulsory only for security, a blocker or unsustainable upkeep (guidance).\n","Plan and execute an approved retirement or migration with compatibility, sequencing, rollback and\nconsumer evidence. Irreversible steps stay separately gated.\n\n## When to use\n\n- An old API, library, feature or service has a replacement and its consumers need moving.\n- A schema shape must change in production — a rename, a drop, a split — without downtime.\n- Code with active consumers has no owner, and the choice is to invest in it or retire it.\n\n## Not for\n\n- Deleting code nothing consumes and nothing exports. That is cleanup, `simplify`.\n- Building the replacement. A retirement with no working alternative stops here until one exists.\n- Removing anything on the strength of this skill's own invocation. The removal step has its own\n  gate, below.\n- Deciding product direction. Whether a feature should exist is a `strategy` question.\n\n## Authority\n\nAuthority: `explicit`. A human starts this skill with `\u002Fak:deprecate`. It may start model-invoked\nskills only. The invocation authorizes the decision, the notice, the migration plan and the\nconsumer migrations; it does not authorize removal. Removing a public surface is\n`public-contract-change` and dropping data is `destructive-data`: each needs an explicit charter\nentry a human approved up front, naming the action and exactly what is permitted, bound to that\ncharter's hash (ruling `sensitive-actions-need-approved-charter-entry`). An approved deprecation plan\nis not such an entry.\n\n## Inputs\n\n- The surface to retire and its replacement. No replacement: `needs-input`, naming the replacement as\n  work that comes first.\n- Consumer evidence through the knowledgebase adapter's `requestImpactAnalysis`, with its coverage\n  statement. Unavailable: `needs-input`; this skill never substitutes its own guess at a consumer\n  count. A partial graph is a stated limitation, and zero consumers on a partial graph is not zero.\n- Existing decisions for the area, through `readContext`.\n- The system of record for migration tickets, decided by configuration and never by reachability\n  (`adapters\u002Ftracker\u002FCONTRACT.md` §2; ruling `tracker-of-record-falls-back-to-kb`): the bound tracker\n  where the project folder binds one and the project record agrees; the knowledgebase where there is\n  no binding and the record names it or there is no record; `needs-input` otherwise. The chain is\n  in the [tracker-of-record reference pack](..\u002F..\u002Freferences\u002Ftracker-of-record\u002FREFERENCE.md).\n- At the removal step only: the charter (`schemas\u002Fcharter.schema.json`) with its approval bound to\n  its hash. Absent, removal does not happen.\n\n## Workflow\n\n1. **Check how this run was started**, before any other step and before any tool call. It is started\n   only when the human's message begins with `\u002Fak:deprecate`; no grant starts it. A request in prose\n   is not a start, even when it names this skill or the command. Otherwise, stop here: make no tool\n   call, say that this command is human-started, and give the human the line to type,\n   `\u002Fak:deprecate` and their request.\n2. **Decide.** Answer five questions before anything else: does it still provide unique value (then\n   keep it); does a replacement exist (if not, stop); how many consumers depend on it, from the\n   impact analysis; what does each consumer's migration cost; what does keeping it cost.\n3. **Choose advisory or compulsory.** Default to advisory. Compulsory is for a security problem, a\n   blocker or unsustainable upkeep, and it ships migration tooling, not only a deadline.\n4. **Choose a migration pattern** from [the migration patterns](references\u002Fmigration-patterns.md):\n   strangler, adapter, feature flag, or expand and contract for any schema change.\n5. **Publish the plan.** The decision as a proposed `adr`; the notice and migration guide, from\n   [the notice template](assets\u002Fdeprecation-notice.md), as a `process` page; one migration `ticket`\n   per consumer in the system of record, through `createTicket` and `linkRecord`.\n6. **Migrate incrementally.** One consumer at a time: find every touchpoint, move it to the\n   replacement, verify behavior matches, remove its references to the old surface, confirm no\n   regression. The owner of the retiring surface migrates its consumers; announcing and leaving them\n   to it is not migration.\n7. **Stop at the removal checkpoint.** Report the consumers migrated and those remaining. Removal is\n   not the next step of the same pass.\n8. **Remove, only under its gate.** When a charter entry covers the action and a fresh impact\n   analysis with full coverage shows zero active consumers: remove the code, its tests, its\n   configuration and its notices, destructive schema steps last and in their own deploy. The\n   [`pack-delete` pack](..\u002F..\u002Fpacks\u002Fpack-delete\u002FPACK.md) attaches to that diff; it constrains the\n   removal and never starts one.\n\n## Hard gates\n\nGate: no retirement without a working replacement.\n\nGate: no consumer count without the impact analysis. An unavailable or partial analysis is reported,\nnever filled with a guess.\n\nGate: removal needs an approved charter entry for the named action, bound to the charter's hash,\nplus zero active consumers on a fresh, full-coverage analysis. Without both, the run stops before\nremoving anything.\n\nGate: a schema change is never made in place. Additive first; destructive last and alone; every\nmigration has a tested down path.\n\n| The thought | Why it is wrong | Do this instead |\n|---|---|---|\n| \"The plan was approved, so removing the old API finishes the job.\" | Approval of a plan is not a charter entry for `public-contract-change` or `destructive-data` (ruling `sensitive-actions-need-approved-charter-entry`). | Stop at the removal checkpoint and name the entry removal needs. |\n| \"Nobody uses it anymore.\" | Hyrum's law: every observable behavior has a dependent, and a belief is not evidence. | Run the impact analysis and report its coverage. |\n| \"Just rename the column, it's one line.\" | During the rollout old and new code run together, and one queries a column that no longer exists. | Expand and contract; never rename in place. |\n| \"Add the new column and drop the old one in the same migration.\" | That couples a safe add to a destructive drop. | Drops get their own deploy after no code reads the old shape. |\n| \"We'll write the rollback if we need it.\" | A migration with no down path is a deploy you cannot reverse. | Write and run the down path before the migration merges. |\n| \"Consumers will migrate on their own.\" | They will not; the owner of the retiring surface migrates them. | Cut a ticket per consumer and migrate them one at a time. |\n\n## Outputs\n\n- A proposed `adr` for the retirement decision and a `process` page for the notice and migration\n  guide, published through the knowledgebase adapter's `publishArtifact` under `kb-document`\n  placements scoped to the project. The knowledgebase resolves the location; this skill writes no\n  notice or decision file into the working repository (ruling `central-kb-owns-project-artifacts`).\n- One migration `ticket` (`schemas\u002Fticket.schema.json`) per consumer, in the system of record.\n- Consumer migrations in the workspace, verified one at a time, for the lane that owns integration.\n- A removal-checkpoint report: consumers migrated, consumers remaining, the analysis coverage, and\n  the charter entry removal would need.\n\n## Side effects\n\n`workspace-write`, `process-exec`, `scratch-write`, `kb-draft`, `kb-publish`, `tracker-write`,\n`artifact-write`. `artifact-write` is the migration `ticket`s, run artifacts bound to their hash.\nThe removal step is `public-contract-change` or `destructive-data`, and happens only under an\napproved charter entry naming it (ruling `sensitive-actions-need-approved-charter-entry`).\n\n`kb-publish` and `tracker-write` are remote side effects. The idempotency key for each derives from\nthe run, the operation, the record's stable remote identity and the artifact's hash; the read-back is\nthe record the write returns, read before the write and confirmed after it\n(`adapters\u002Frunner-contract\u002FCONTRACT.md`, \"Idempotency\"). A write whose read-back cannot be performed\nis `failed`, never complete.\n\n## Stop conditions\n\n- `complete` — the plan is published, the consumers in scope are migrated, and the run stopped at the\n  removal checkpoint; or, under a covering charter entry, removal is done and verified.\n- `complete` — the decision gate showed the surface still provides unique value; nothing retires.\n- `needs-input` — not started with `\u002Fak:deprecate`, no replacement, no impact analysis, no system of\n  record, or removal requested without a covering charter entry.\n- `failed` — a write's read-back cannot be performed, or a consumer migration broke verification and\n  could not be reverted.\n- `cancelled` — the human withdrew; published records stay, and nothing is removed.\n\n## Limits\n\n- Removal: never in the same pass as migration, and never without a covering charter entry (gate).\n- Consumers migrated at a time: one, verified before the next (gate).\n- Advisory by default; compulsory only for security, a blocker or unsustainable upkeep (guidance).\n",{"name":5,"license":15,"metadata":24,"description":7},{"ak_catalog_id":5},"main","e0232821c4abbcd4338d6018c20fb70f1b74336b","skills\u002Fdeprecate",3,"https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit","https:\u002F\u002Fgithub.com\u002FPibomeister","www.eduardopicazoenriquez.com","2026-11-15 00:56:58",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Pibomeister\u002Fagent-kit --skill deprecate",{"tool":39,"command":40},"bunx","bunx skills add Pibomeister\u002Fagent-kit --skill deprecate",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Pibomeister\u002Fagent-kit --skill deprecate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Fskills\u002Fdeprecate\u002FSKILL.md",true,[47,53,59],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"assets\u002Fdeprecation-notice.md","ASSET","资产文件",1134,"https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Fskills\u002Fdeprecate\u002Fassets\u002Fdeprecation-notice.md",{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fmigration-patterns.md","REFERENCE","参考文档",4086,"https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Fskills\u002Fdeprecate\u002Freferences\u002Fmigration-patterns.md",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"skill.yaml",11654,"https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Fskills\u002Fdeprecate\u002Fskill.yaml",[64,71,76,81,86,91],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7D3JZP2026RGY6XX1MC3NQQ","alpha","Human-started command: it runs only when the human's message begins with `\u002Fak:alpha`. On any other request do not load or follow it; tell the human to type that command. Runs the alpha workflow when a human asks for it.","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvalid\u002Fminimal\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":72,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7D3JA593Q3RBYJXKVZ37Y2K","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid\u002F25-article-tier-outside-vocabulary\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":77,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7D3HQDDAZTAPGWCPGDPNVBQ","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid\u002F24-article-without-triggers\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":82,"name":66,"nameZh":6,"description":67,"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},"01M7D3HK074TK3ZWK1ZZNQVPB0","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid\u002F23-enforced-by-without-predicate\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":87,"name":66,"nameZh":6,"description":67,"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},"01M7D3HGHQM5C5TBSXBCE2WFHW","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid\u002F22-article-without-source-span\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":92,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7D3HDV6HMK2ZHRM0P368KNT","https:\u002F\u002Fgithub.com\u002FPibomeister\u002Fagent-kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid\u002F21-fragment-redeclares-id\u002Fskills\u002Falpha\u002FSKILL.md",[],[]]