[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E8GRDVT9YTM4RSES4QJH2N":3,"skill-same:01M7E8GRDVT9YTM4RSES4QJH2N":48},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7E8GRDVT9YTM4RSES4QJH2N","ln-26-architecture-migration-planner",null,"Plans architecture migrations with compatibility, data safety, rollout and recovery; does not execute them.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Farchitecture\u002Fln-26-architecture-migration-planner\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ln-26-architecture-migration-planner\ndescription: \"Plans architecture migrations with compatibility, data safety, rollout and recovery; does not execute them.\"\nsource: \"https:\u002F\u002Fgithub.com\u002Flevnikolaevich\u002Fclaude-code-skills\"\nsource_repository: \"levnikolaevich\u002Fclaude-code-skills\"\nsource_path: \"plugins\u002Farchitecture-suite\u002Fskills\u002Fln-26-architecture-migration-planner\u002FSKILL.md\"\nlicense: \"MIT\"\nimported_at: \"2026-09-20\"\n---\n\n# Architecture Migration Planner\n\n**Goal:** Plan a safe transition from evidenced current architecture to an explicit target, with reversibility limits and recovery actions. Change only the approved migration document; do not execute migrations, edit product code, build a generic task plan, approve delivery, or hide irreversible steps.\n\n**Execution contract:** The checklist defines completion. Track each item internally as `PENDING`, `PROVEN` with evidence, `CLEARED` with evidence its condition is absent, or `UNPROVEN` with a gap; reading, delegation, or tool failure is not proof. Reconcile after each section. Before returning, resolve all `PENDING`, count only `PROVEN` and `CLEARED`, and apply verdict and approval rules to every gap.\nPreserve intent, scope, and existing authorization. Continue authorized work; ask only for consequential unresolved choices or required external approval. Scale depth to material risk without skipping checks. Preserve dependency and safety order; otherwise choose an appropriate verification method.\nAccept equivalent user or repository evidence; no other skill, named artifact, or complete lifecycle is required. Preserve source requirement and decision IDs. Bind reused evidence to relevant source versions, dirty changes, configuration, and environment; invalidate only affected claims.\nOn continuation, reconcile task, authorization, current state, and unresolved evidence. For long work, return a compact continuation record or update an already authorized artifact; read-only skills do not persist it. Distinguish artifact readiness, verified behavior, and external-action authority.\nPrepare authorized work before required approval. If blocked by an instruction, cite its exact source and unresolved boundary; do not invent approval gates from caution.\n\n\n## Tool Routing\n\n| Need | Preferred capability | Fallback |\n|---|---|---|\n| Current and target states | Repository evidence plus approved architecture artifacts | Explicit user-provided states with limitations |\n| Consumers and compatibility | Language intelligence, schema tools, config search, telemetry, and direct inspection | Conservative inventory marked `UNVERIFIED` |\n| Data scale and runtime risk | Production metrics, checked-in reports, migrations, and workload evidence | Ranges with validation gates before execution |\n| External migration constraints | Official vendor migration and compatibility guidance | Mark dependent phases `BLOCKED` or `UNVERIFIED` |\n| Document mutation | Minimal patch to the approved migration-plan artifact | Return `BLOCKED` when authority or path is unclear |\n\nA migration phase must leave the system in a supported state. Additive and reversible steps precede cutover; destructive cleanup follows verified zero use.\n\n## Artifact Rules\n\n- Reuse a clear architecture migration document; otherwise use `docs\u002Farchitecture\u002Fmigration-plan.md`.\n- Treat current-state, target-design, baseline, decisions, diagrams, interfaces, and telemetry as optional shared evidence.\n- Keep the plan architectural: phases, compatibility, data, topology, gates, rollback, ownership, and removal.\n- Leave file-level implementation tasks to downstream planning.\n- Never describe rollback as \"revert\" when data or external effects are not reversible.\n- Give every destructive step explicit approval, backup, restoration, and zero-consumer evidence requirements.\n\n## Checklist\n\n### 1. Establish the Transition Contract\n\n- [ ] Resolve migration scope, business outcome, current state, target state, non-goals, deadline or horizon, owners, and approved destination.\n- [ ] Read repository instructions, Git state, relevant architecture artifacts, migrations, deployment configuration, and compatibility policies.\n- [ ] Verify that current and target states are specific enough to compute a gap; return `BLOCKED` rather than invent either state.\n- [ ] Identify protected user journeys, invariants, SLOs, recovery objectives, compliance duties, and change windows.\n- [ ] Keep the run read-only except for the approved migration document.\n\n### 2. Build the Gap and Dependency Map\n\n- [ ] Inventory affected modules, deployables, data stores, schemas, APIs, events, configuration, infrastructure, and operational procedures.\n- [ ] Inventory internal and external consumers, owners, versions, traffic, data volume, and evidence quality.\n- [ ] Map current-to-target changes in boundaries, ownership, contracts, data, runtime topology, observability, and failure behavior.\n- [ ] Identify shared mutable resources, sequencing dependencies, long-running work, mixed-version windows, and irreversible effects.\n- [ ] Record unknown consumers or usage as migration risks; absence of search results is not zero usage.\n\n### 3. Design Compatibility and Data Safety\n\n- [ ] Define old\u002Fnew contract compatibility, version negotiation, adapters, dual-read or dual-write behavior, and deprecation policy where relevant.\n- [ ] Use expand\u002Fmigrate\u002Fcontract when mixed versions or online migration require coexistence; separate additive and destructive releases in that case. For an approved offline atomic transition, document the equivalent compatibility, recovery, and downtime controls.\n- [ ] Define backfill selection, batching, throttling, idempotency, checkpoints, retries, reconciliation, and correctness oracle.\n- [ ] Define source of truth during coexistence, concurrent-write conflict handling, and detection, retry, and reconciliation of partial dual-write failure; do not assume two writes are atomic.\n- [ ] Define backup, restore, RPO\u002FRTO impact, privacy, retention, and audit evidence for data movement.\n\n### 4. Build Reversible Phases\n\n- [ ] Define preparation, shadow or coexistence, progressive migration, cutover, stabilization, and old-path removal as independently verifiable phases.\n- [ ] For every phase, state prerequisites, changed architecture state, owner, entry gate, observable success, abort condition, rollback or roll-forward action, and exit evidence.\n- [ ] Define feature flags, routing controls, canary cohorts, rate limits, maintenance windows, and blast-radius controls where justified.\n- [ ] Define metrics, logs, traces, reconciliation reports, dashboards, alerts, and SLO gates needed before traffic or data movement.\n- [ ] Keep old and new versions interoperable through realistic deployment ordering and rollback windows.\n\n### 5. Plan Cutover and Removal\n\n- [ ] Define go\u002Fno-go authority, communication, freeze conditions, exact cutover control, and immediate verification.\n- [ ] Define rollback boundaries separately for code, configuration, traffic, schema, and migrated data, including points of no return and roll-forward recovery when rollback would lose accepted writes.\n- [ ] Before destructive removal, require usage evidence over a window covering relevant schedules and offline consumers, migrated consumers, applicable retention expiry, and explicit approval. A short zero-traffic sample cannot establish zero use.\n- [ ] List old code paths, contracts, flags, adapters, jobs, data, infrastructure, dashboards, and documentation to remove.\n- [ ] Define post-cutover observation period, ownership handoff, incident response, and closure evidence.\n\n### 6. Write and Report\n\n- [ ] Write transition summary, state gap, dependencies, compatibility, data plan, phased sequence, gates, observability, rollback, removal, owners, assumptions, and open decisions.\n- [ ] Link shared artifacts by stable repository path or title without requiring a particular workflow.\n- [ ] Re-read every phase for unsupported zero-downtime, zero-loss, consumer, capacity, or reversibility claims.\n- [ ] Link each transition unit to the protected requirement, current\u002Ftarget boundary, entry evidence, observed success, and irreversible point; identify dependent plans affected by a migration change.\n- [ ] Use `READY` only when phases are safely executable inputs to implementation planning; use `REVISE` for material compatibility, data, gate, or rollback gaps; use `BLOCKED` when current state, target state, authority, or safety evidence is unavailable.\n\n## Self-Check\n\n- [ ] **Reconcile before returning.** Check item-level evidence, requirement coverage, contradictions, scope, verdict, and applicable cleanup. Correct the report or authorized artifacts. Reuse valid evidence; do not automatically rescan the repository or rerun successful commands. Repeat checks only for relevant changes, failures, or unresolved evidence. Disclose remaining gaps.\n\n## Output Contract\n\nReport in the user's language, in this order; retain all five fields and state each fact once. Small results may use one line per field; omit empty tables and do not copy linked artifacts:\n\n1. **Result:** Skill-specific verdict and supported outcome.\n2. **Scope:** Reviewed\u002Fchanged scope, exclusions, baseline, and material assumptions.\n3. **Evidence:** Skill-specific fields below; distinguish facts, inferences, and unverified claims. Link artifacts; use tables when useful.\n4. **Verification:** Checks\u002Fresults, unavailable evidence, and applicable cleanup\u002Fexternal state.\n5. **Completion:** `Checklist: X\u002FY complete`; `Incomplete: None` or each `UNPROVEN` item's reason, outcome impact, and exact next action; residual risks and required decisions.\n\n**Skill-specific evidence:** Artifact path; current\u002Ftarget gap, consumers, dependencies, and protected invariants. Summarize phases with entry gates, changes, success evidence, abort conditions, rollback\u002Froll-forward; data\u002Fcoexistence\u002Freconciliation\u002Fcutover\u002Fremoval proof; and open decisions that affect safety, ordering, or reversibility.\n","# Architecture Migration Planner\n\n**Goal:** Plan a safe transition from evidenced current architecture to an explicit target, with reversibility limits and recovery actions. Change only the approved migration document; do not execute migrations, edit product code, build a generic task plan, approve delivery, or hide irreversible steps.\n\n**Execution contract:** The checklist defines completion. Track each item internally as `PENDING`, `PROVEN` with evidence, `CLEARED` with evidence its condition is absent, or `UNPROVEN` with a gap; reading, delegation, or tool failure is not proof. Reconcile after each section. Before returning, resolve all `PENDING`, count only `PROVEN` and `CLEARED`, and apply verdict and approval rules to every gap.\nPreserve intent, scope, and existing authorization. Continue authorized work; ask only for consequential unresolved choices or required external approval. Scale depth to material risk without skipping checks. Preserve dependency and safety order; otherwise choose an appropriate verification method.\nAccept equivalent user or repository evidence; no other skill, named artifact, or complete lifecycle is required. Preserve source requirement and decision IDs. Bind reused evidence to relevant source versions, dirty changes, configuration, and environment; invalidate only affected claims.\nOn continuation, reconcile task, authorization, current state, and unresolved evidence. For long work, return a compact continuation record or update an already authorized artifact; read-only skills do not persist it. Distinguish artifact readiness, verified behavior, and external-action authority.\nPrepare authorized work before required approval. If blocked by an instruction, cite its exact source and unresolved boundary; do not invent approval gates from caution.\n\n\n## Tool Routing\n\n| Need | Preferred capability | Fallback |\n|---|---|---|\n| Current and target states | Repository evidence plus approved architecture artifacts | Explicit user-provided states with limitations |\n| Consumers and compatibility | Language intelligence, schema tools, config search, telemetry, and direct inspection | Conservative inventory marked `UNVERIFIED` |\n| Data scale and runtime risk | Production metrics, checked-in reports, migrations, and workload evidence | Ranges with validation gates before execution |\n| External migration constraints | Official vendor migration and compatibility guidance | Mark dependent phases `BLOCKED` or `UNVERIFIED` |\n| Document mutation | Minimal patch to the approved migration-plan artifact | Return `BLOCKED` when authority or path is unclear |\n\nA migration phase must leave the system in a supported state. Additive and reversible steps precede cutover; destructive cleanup follows verified zero use.\n\n## Artifact Rules\n\n- Reuse a clear architecture migration document; otherwise use `docs\u002Farchitecture\u002Fmigration-plan.md`.\n- Treat current-state, target-design, baseline, decisions, diagrams, interfaces, and telemetry as optional shared evidence.\n- Keep the plan architectural: phases, compatibility, data, topology, gates, rollback, ownership, and removal.\n- Leave file-level implementation tasks to downstream planning.\n- Never describe rollback as \"revert\" when data or external effects are not reversible.\n- Give every destructive step explicit approval, backup, restoration, and zero-consumer evidence requirements.\n\n## Checklist\n\n### 1. Establish the Transition Contract\n\n- [ ] Resolve migration scope, business outcome, current state, target state, non-goals, deadline or horizon, owners, and approved destination.\n- [ ] Read repository instructions, Git state, relevant architecture artifacts, migrations, deployment configuration, and compatibility policies.\n- [ ] Verify that current and target states are specific enough to compute a gap; return `BLOCKED` rather than invent either state.\n- [ ] Identify protected user journeys, invariants, SLOs, recovery objectives, compliance duties, and change windows.\n- [ ] Keep the run read-only except for the approved migration document.\n\n### 2. Build the Gap and Dependency Map\n\n- [ ] Inventory affected modules, deployables, data stores, schemas, APIs, events, configuration, infrastructure, and operational procedures.\n- [ ] Inventory internal and external consumers, owners, versions, traffic, data volume, and evidence quality.\n- [ ] Map current-to-target changes in boundaries, ownership, contracts, data, runtime topology, observability, and failure behavior.\n- [ ] Identify shared mutable resources, sequencing dependencies, long-running work, mixed-version windows, and irreversible effects.\n- [ ] Record unknown consumers or usage as migration risks; absence of search results is not zero usage.\n\n### 3. Design Compatibility and Data Safety\n\n- [ ] Define old\u002Fnew contract compatibility, version negotiation, adapters, dual-read or dual-write behavior, and deprecation policy where relevant.\n- [ ] Use expand\u002Fmigrate\u002Fcontract when mixed versions or online migration require coexistence; separate additive and destructive releases in that case. For an approved offline atomic transition, document the equivalent compatibility, recovery, and downtime controls.\n- [ ] Define backfill selection, batching, throttling, idempotency, checkpoints, retries, reconciliation, and correctness oracle.\n- [ ] Define source of truth during coexistence, concurrent-write conflict handling, and detection, retry, and reconciliation of partial dual-write failure; do not assume two writes are atomic.\n- [ ] Define backup, restore, RPO\u002FRTO impact, privacy, retention, and audit evidence for data movement.\n\n### 4. Build Reversible Phases\n\n- [ ] Define preparation, shadow or coexistence, progressive migration, cutover, stabilization, and old-path removal as independently verifiable phases.\n- [ ] For every phase, state prerequisites, changed architecture state, owner, entry gate, observable success, abort condition, rollback or roll-forward action, and exit evidence.\n- [ ] Define feature flags, routing controls, canary cohorts, rate limits, maintenance windows, and blast-radius controls where justified.\n- [ ] Define metrics, logs, traces, reconciliation reports, dashboards, alerts, and SLO gates needed before traffic or data movement.\n- [ ] Keep old and new versions interoperable through realistic deployment ordering and rollback windows.\n\n### 5. Plan Cutover and Removal\n\n- [ ] Define go\u002Fno-go authority, communication, freeze conditions, exact cutover control, and immediate verification.\n- [ ] Define rollback boundaries separately for code, configuration, traffic, schema, and migrated data, including points of no return and roll-forward recovery when rollback would lose accepted writes.\n- [ ] Before destructive removal, require usage evidence over a window covering relevant schedules and offline consumers, migrated consumers, applicable retention expiry, and explicit approval. A short zero-traffic sample cannot establish zero use.\n- [ ] List old code paths, contracts, flags, adapters, jobs, data, infrastructure, dashboards, and documentation to remove.\n- [ ] Define post-cutover observation period, ownership handoff, incident response, and closure evidence.\n\n### 6. Write and Report\n\n- [ ] Write transition summary, state gap, dependencies, compatibility, data plan, phased sequence, gates, observability, rollback, removal, owners, assumptions, and open decisions.\n- [ ] Link shared artifacts by stable repository path or title without requiring a particular workflow.\n- [ ] Re-read every phase for unsupported zero-downtime, zero-loss, consumer, capacity, or reversibility claims.\n- [ ] Link each transition unit to the protected requirement, current\u002Ftarget boundary, entry evidence, observed success, and irreversible point; identify dependent plans affected by a migration change.\n- [ ] Use `READY` only when phases are safely executable inputs to implementation planning; use `REVISE` for material compatibility, data, gate, or rollback gaps; use `BLOCKED` when current state, target state, authority, or safety evidence is unavailable.\n\n## Self-Check\n\n- [ ] **Reconcile before returning.** Check item-level evidence, requirement coverage, contradictions, scope, verdict, and applicable cleanup. Correct the report or authorized artifacts. Reuse valid evidence; do not automatically rescan the repository or rerun successful commands. Repeat checks only for relevant changes, failures, or unresolved evidence. Disclose remaining gaps.\n\n## Output Contract\n\nReport in the user's language, in this order; retain all five fields and state each fact once. Small results may use one line per field; omit empty tables and do not copy linked artifacts:\n\n1. **Result:** Skill-specific verdict and supported outcome.\n2. **Scope:** Reviewed\u002Fchanged scope, exclusions, baseline, and material assumptions.\n3. **Evidence:** Skill-specific fields below; distinguish facts, inferences, and unverified claims. Link artifacts; use tables when useful.\n4. **Verification:** Checks\u002Fresults, unavailable evidence, and applicable cleanup\u002Fexternal state.\n5. **Completion:** `Checklist: X\u002FY complete`; `Incomplete: None` or each `UNPROVEN` item's reason, outcome impact, and exact next action; residual risks and required decisions.\n\n**Skill-specific evidence:** Artifact path; current\u002Ftarget gap, consumers, dependencies, and protected invariants. Summarize phases with entry gates, changes, success evidence, abort conditions, rollback\u002Froll-forward; data\u002Fcoexistence\u002Freconciliation\u002Fcutover\u002Fremoval proof; and open decisions that affect safety, ordering, or reversibility.\n",{"name":5,"source":24,"license":15,"description":7,"imported_at":25,"source_path":26,"source_repository":27},"https:\u002F\u002Fgithub.com\u002Flevnikolaevich\u002Fclaude-code-skills","2026-09-20","plugins\u002Farchitecture-suite\u002Fskills\u002Fln-26-architecture-migration-planner\u002FSKILL.md","levnikolaevich\u002Fclaude-code-skills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Farchitecture\u002Fln-26-architecture-migration-planner","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill ln-26-architecture-migration-planner",{"tool":40,"command":41},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill ln-26-architecture-migration-planner",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill ln-26-architecture-migration-planner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Farchitecture\u002Fln-26-architecture-migration-planner\u002FSKILL.md",true,[],[49,57,64,71,78,85],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":56},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":56},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"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":56},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":56},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":56},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":56},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]