[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E8FRQJPGDMP1K3Y8YN3HT8":3,"skill-same:01M7E8FRQJPGDMP1K3Y8YN3HT8":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},"01M7E8FRQJPGDMP1K3Y8YN3HT8","ln-21-system-design-baseline-builder",null,"Defines measurable architecture drivers and constraints before system design; edits architecture docs only.","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-21-system-design-baseline-builder\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ln-21-system-design-baseline-builder\ndescription: \"Defines measurable architecture drivers and constraints before system design; edits architecture docs only.\"\nsource: \"https:\u002F\u002Fgithub.com\u002Flevnikolaevich\u002Fclaude-code-skills\"\nsource_repository: \"levnikolaevich\u002Fclaude-code-skills\"\nsource_path: \"plugins\u002Farchitecture-suite\u002Fskills\u002Fln-21-system-design-baseline-builder\u002FSKILL.md\"\nlicense: \"MIT\"\nimported_at: \"2026-09-20\"\n---\n\n# System Design Baseline Builder\n\n**Goal:** Create or update one durable source of truth for the project's architecture-driving requirements and constraints. Change only the approved architecture document; do not design the solution, review a plan, audit implementation, edit product code, or invent missing targets.\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| Repository rules and document conventions | Native file reads plus focused search | User-provided convention with an explicit limitation |\n| Existing requirements and architecture artifacts | Narrow repository search and direct reads | Conversation evidence marked with its source |\n| Current workload or service evidence | Metrics, dashboards, logs, manifests, or checked-in reports | Mark `UNKNOWN`; never manufacture production numbers |\n| Current external limits or standards | Official documentation or specifications | Mark the claim `UNVERIFIED` |\n| Document mutation | Minimal patch to the approved Markdown artifact | Return `BLOCKED` if no safe writable path is authorized |\n\nUse external research only when a time-sensitive fact changes a constraint. Do not browse for values that must come from product owners, operators, the repository, or measured workload.\n\n## Artifact Rules\n\n- Prefer an existing unambiguous architecture-requirements document.\n- Otherwise use `docs\u002Farchitecture\u002Fsystem-design-baseline.md`.\n- Read before writing, preserve unrelated content, and update facts in place instead of creating parallel truth.\n- Classify applicability separately as `APPLICABLE` or `NOT_APPLICABLE`, with evidence for exclusions.\n- Rank each applicable item as `DRIVER`, `SUPPORTING`, or `INFORMATIONAL`.\n- Classify evidence separately as `CONFIRMED`, `ASSUMED`, or `UNKNOWN`.\n- Separate observed current values, required targets, hard limits, and future evolution triggers.\n- Express quality attributes through observable scenarios and response measures; record undecided targets as missing decisions rather than inventing numbers.\n- Treat the baseline as versioned project knowledge, not an immutable promise.\n\n## Checklist\n\n### 1. Establish Scope and Destination\n\n- [ ] Resolve the project, business outcome, intended readers, approved documentation scope, and language.\n- [ ] Read applicable repository instructions and inspect Git state so unrelated changes remain untouched.\n- [ ] Search for existing requirement, architecture, SLO, recovery, security, cost, and ownership documents.\n- [ ] Select one canonical artifact: reuse a clear equivalent or choose the default path; explain why no duplicate will be created.\n- [ ] Return `BLOCKED` if the destination is ambiguous and choosing one could split project truth.\n\n### 2. Build the Evidence Ledger\n\n- [ ] Collect business goals, actors, journeys, scope, non-goals, and decision horizon with their sources and confidence for the driver analysis; do not create a second context inventory.\n- [ ] Record sources for current workload, data volume, service behavior, platform limits, and existing commitments.\n- [ ] Separate repository facts from stakeholder choices and estimates.\n- [ ] Detect contradictions between documents, code, configuration, and stated requirements; preserve both claims until resolved.\n- [ ] Ask only for choices whose absence materially changes architecture; mark all other gaps `UNKNOWN`.\n\n### 3. Define and Prioritize Architecture Drivers\n\n- [ ] **Business and scope:** Record actors, critical journeys, business horizon, scope, non-goals, and externally committed outcomes.\n- [ ] **Demand and data scale:** Record current and target users, rates, concurrency, payloads, growth, retention, and forecast horizon where relevant.\n- [ ] **User-observable service quality:** Define SLIs and SLOs for availability, latency, throughput, error rate, correctness, or freshness with measurement windows.\n- [ ] **Data semantics and recovery:** Define consistency, ordering, idempotency, reconciliation, durability, backup, RTO, RPO, and acceptable data loss at affected boundaries.\n- [ ] **Security, privacy, and compliance:** Define trust boundaries, data classification, residency, access, audit, and destructive-action constraints.\n- [ ] **Operations and economics:** Define ownership, operational capacity, cost envelope, supported regions, delivery cadence, and platform or vendor constraints.\n- [ ] **Evolution:** Record thresholds, business events, or evidence that justify revisiting an assumption, target, or deferred capability.\n- [ ] Separate applicability, criticality, and evidence status; do not use `UNKNOWN` to mean unimportant or `NOT_APPLICABLE`.\n- [ ] Prioritize the few scenarios most likely to shape architecture and express each as source\u002Fstimulus\u002Fenvironment\u002Fartifact\u002Fresponse\u002Fmeasure.\n\n### 4. Write the Baseline\n\n- [ ] Create or update the artifact with: identity and status; business context; scope and non-goals; critical scenarios; workload and data; quality targets; recovery; consistency; security; cost and operations; constraints; assumptions and unknowns; review triggers.\n- [ ] Give material parameters their theme, applicability, criticality, evidence status, value\u002Frange, source, owner, as-of date, and review trigger. State shared metadata once with explicit inheritance; use `UNKNOWN` for missing ownership or values.\n- [ ] Keep calculations reproducible and label estimates separately from observed measurements.\n- [ ] Link shared architecture artifacts only by repository path or document title; never require a particular workflow or tool.\n- [ ] Preserve historical context needed to understand changed requirements instead of silently rewriting prior commitments.\n\n### 5. Validate and Report\n\n- [ ] Re-read the written artifact and verify that no unknown was converted into a confident fact.\n- [ ] Check that targets are measurable, internally consistent, and proportionate to the evidenced business horizon.\n- [ ] Check that every architecture-critical gap has an owner or exact next evidence action.\n- [ ] Link architecture drivers to their source product requirements; preserve the product source as owner of functional rules rather than copying a second requirements baseline.\n- [ ] Use `READY` only when the baseline is usable for decisions and no material unknown lacks a safe handling rule; use `INCOMPLETE` for a useful artifact with consequential open drivers; use `BLOCKED` when scope, authority, or destination prevents safe creation.\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, established drivers and prioritized quality scenarios, applicable constraints, and changed sections. The artifact owns the driver register: theme\u002Fparameter, applicability, criticality, evidence status, value\u002Fmeasure, source\u002Fowner, as-of date, and review trigger. Summarize only decision-changing gaps; do not copy the register into the response.\n","# System Design Baseline Builder\n\n**Goal:** Create or update one durable source of truth for the project's architecture-driving requirements and constraints. Change only the approved architecture document; do not design the solution, review a plan, audit implementation, edit product code, or invent missing targets.\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| Repository rules and document conventions | Native file reads plus focused search | User-provided convention with an explicit limitation |\n| Existing requirements and architecture artifacts | Narrow repository search and direct reads | Conversation evidence marked with its source |\n| Current workload or service evidence | Metrics, dashboards, logs, manifests, or checked-in reports | Mark `UNKNOWN`; never manufacture production numbers |\n| Current external limits or standards | Official documentation or specifications | Mark the claim `UNVERIFIED` |\n| Document mutation | Minimal patch to the approved Markdown artifact | Return `BLOCKED` if no safe writable path is authorized |\n\nUse external research only when a time-sensitive fact changes a constraint. Do not browse for values that must come from product owners, operators, the repository, or measured workload.\n\n## Artifact Rules\n\n- Prefer an existing unambiguous architecture-requirements document.\n- Otherwise use `docs\u002Farchitecture\u002Fsystem-design-baseline.md`.\n- Read before writing, preserve unrelated content, and update facts in place instead of creating parallel truth.\n- Classify applicability separately as `APPLICABLE` or `NOT_APPLICABLE`, with evidence for exclusions.\n- Rank each applicable item as `DRIVER`, `SUPPORTING`, or `INFORMATIONAL`.\n- Classify evidence separately as `CONFIRMED`, `ASSUMED`, or `UNKNOWN`.\n- Separate observed current values, required targets, hard limits, and future evolution triggers.\n- Express quality attributes through observable scenarios and response measures; record undecided targets as missing decisions rather than inventing numbers.\n- Treat the baseline as versioned project knowledge, not an immutable promise.\n\n## Checklist\n\n### 1. Establish Scope and Destination\n\n- [ ] Resolve the project, business outcome, intended readers, approved documentation scope, and language.\n- [ ] Read applicable repository instructions and inspect Git state so unrelated changes remain untouched.\n- [ ] Search for existing requirement, architecture, SLO, recovery, security, cost, and ownership documents.\n- [ ] Select one canonical artifact: reuse a clear equivalent or choose the default path; explain why no duplicate will be created.\n- [ ] Return `BLOCKED` if the destination is ambiguous and choosing one could split project truth.\n\n### 2. Build the Evidence Ledger\n\n- [ ] Collect business goals, actors, journeys, scope, non-goals, and decision horizon with their sources and confidence for the driver analysis; do not create a second context inventory.\n- [ ] Record sources for current workload, data volume, service behavior, platform limits, and existing commitments.\n- [ ] Separate repository facts from stakeholder choices and estimates.\n- [ ] Detect contradictions between documents, code, configuration, and stated requirements; preserve both claims until resolved.\n- [ ] Ask only for choices whose absence materially changes architecture; mark all other gaps `UNKNOWN`.\n\n### 3. Define and Prioritize Architecture Drivers\n\n- [ ] **Business and scope:** Record actors, critical journeys, business horizon, scope, non-goals, and externally committed outcomes.\n- [ ] **Demand and data scale:** Record current and target users, rates, concurrency, payloads, growth, retention, and forecast horizon where relevant.\n- [ ] **User-observable service quality:** Define SLIs and SLOs for availability, latency, throughput, error rate, correctness, or freshness with measurement windows.\n- [ ] **Data semantics and recovery:** Define consistency, ordering, idempotency, reconciliation, durability, backup, RTO, RPO, and acceptable data loss at affected boundaries.\n- [ ] **Security, privacy, and compliance:** Define trust boundaries, data classification, residency, access, audit, and destructive-action constraints.\n- [ ] **Operations and economics:** Define ownership, operational capacity, cost envelope, supported regions, delivery cadence, and platform or vendor constraints.\n- [ ] **Evolution:** Record thresholds, business events, or evidence that justify revisiting an assumption, target, or deferred capability.\n- [ ] Separate applicability, criticality, and evidence status; do not use `UNKNOWN` to mean unimportant or `NOT_APPLICABLE`.\n- [ ] Prioritize the few scenarios most likely to shape architecture and express each as source\u002Fstimulus\u002Fenvironment\u002Fartifact\u002Fresponse\u002Fmeasure.\n\n### 4. Write the Baseline\n\n- [ ] Create or update the artifact with: identity and status; business context; scope and non-goals; critical scenarios; workload and data; quality targets; recovery; consistency; security; cost and operations; constraints; assumptions and unknowns; review triggers.\n- [ ] Give material parameters their theme, applicability, criticality, evidence status, value\u002Frange, source, owner, as-of date, and review trigger. State shared metadata once with explicit inheritance; use `UNKNOWN` for missing ownership or values.\n- [ ] Keep calculations reproducible and label estimates separately from observed measurements.\n- [ ] Link shared architecture artifacts only by repository path or document title; never require a particular workflow or tool.\n- [ ] Preserve historical context needed to understand changed requirements instead of silently rewriting prior commitments.\n\n### 5. Validate and Report\n\n- [ ] Re-read the written artifact and verify that no unknown was converted into a confident fact.\n- [ ] Check that targets are measurable, internally consistent, and proportionate to the evidenced business horizon.\n- [ ] Check that every architecture-critical gap has an owner or exact next evidence action.\n- [ ] Link architecture drivers to their source product requirements; preserve the product source as owner of functional rules rather than copying a second requirements baseline.\n- [ ] Use `READY` only when the baseline is usable for decisions and no material unknown lacks a safe handling rule; use `INCOMPLETE` for a useful artifact with consequential open drivers; use `BLOCKED` when scope, authority, or destination prevents safe creation.\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, established drivers and prioritized quality scenarios, applicable constraints, and changed sections. The artifact owns the driver register: theme\u002Fparameter, applicability, criticality, evidence status, value\u002Fmeasure, source\u002Fowner, as-of date, and review trigger. Summarize only decision-changing gaps; do not copy the register into the response.\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-21-system-design-baseline-builder\u002FSKILL.md","levnikolaevich\u002Fclaude-code-skills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Farchitecture\u002Fln-21-system-design-baseline-builder","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-21-system-design-baseline-builder",{"tool":40,"command":41},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill ln-21-system-design-baseline-builder",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill ln-21-system-design-baseline-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Farchitecture\u002Fln-21-system-design-baseline-builder\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",[],[]]