[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C6XB13HHMYTNFAQZGVEQ5F":3,"skill-same:01M7C6XB13HHMYTNFAQZGVEQ5F":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7C6XB13HHMYTNFAQZGVEQ5F","benchmark-methodology",null,"Use after competitive-platform-analysis has produced a tiered competitor set. Scores each competitor across nine weighted dimensions (positioning, voice, visual craft, offer packaging, evidence, enterprise-readiness, thought leadership, pricing, client's strategic tension) with explicit 1 to 5 rubrics and a tension-plot. Precedes competitive-report-structure.","amine-elhanine\u002Fnexus-code","amine-elhanine","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F98957228?v=4","01M7C6VS3WWT3P8YTC5S1A3GTH","01M7C6VS4EVADV081SG9T5VHHV",1,"MIT","https:\u002F\u002Fgithub.com\u002Famine-elhanine\u002Fnexus-code\u002Fblob\u002Fmain\u002Fplugins\u002Fskills\u002Fcontent-engine\u002Fskills\u002Fcontent-engine\u002Fbenchmark-methodology\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: benchmark-methodology\ndescription: Use after competitive-platform-analysis has produced a tiered competitor set. Scores each competitor across nine weighted dimensions (positioning, voice, visual craft, offer packaging, evidence, enterprise-readiness, thought leadership, pricing, client's strategic tension) with explicit 1 to 5 rubrics and a tension-plot. Precedes competitive-report-structure.\nlicense: MIT\n---\n\n# Benchmark Methodology\n\nUse this skill to turn a scoped competitor set into **comparable, defensible\nscores**. Each competitor is assessed on the same nine dimensions, with\nexplicit 1–5 rubrics, then captured in a uniform profile card. Consistency is\nthe point: scores are only useful if the same evidence would earn the same\nnumber for any competitor.\n\n## When to Activate\n\n- A scoped, tiered competitor set from competitive-platform-analysis is ready to score.\n- Need comparable, evidence-anchored scores across competitors — not gut-feel rankings.\n- Client's strategic tension (the paired axes defining their target white-space) has been established.\n- Preparing to produce profile cards for assembly in competitive-report-structure.\n\n## Client positioning brief (establish first)\n\nBefore scoring, establish the client's positioning brief. It supplies:\n\n- **Strategic tension** — the two axes (e.g., memorability × hireability) whose\n  intersection marks the client's target white-space. Dimension 9 is always\n  the client's named tension; report both poles separately, never averaged.\n- **Differentiator** — what makes the client's moat. This informs which\n  dimensions matter most for the client's positioning argument.\n- **Brand balance** — the intended mix of distinct strategic emphases. Strategic\n  recommendations must not break this balance without flagging it.\n\n## Why these dimensions\n\nThe client competes on a **specific tension held across two poles**, not on\nservice breadth. The dimensions are weighted to reflect that moat. Two\ndimensions — the tension poles — are scored **separately and never averaged\ntogether**, because the client's strategic question is precisely whether a rival\nachieves both simultaneously.\n\n## The nine dimensions (with weights)\n\nWeights guide synthesis emphasis, not a single blended score (avoid a false\ncomposite — see Bias controls). Sum = 100%.\n\n1. **Positioning clarity & distinctiveness** (18%) — Is the studio's position\n   sharp, ownable, and instantly legible? Or generic?\n2. **Brand voice \u002F verbal distinctiveness** (15%) — Does the copy have an\n   ownable register, or is it interchangeable agency-speak?\n3. **Visual identity & site craft** (15%) — Quality and ownership of the visual\n   system; site as proof-of-craft.\n4. **Service offer & packaging** (12%) — Productized and legible (named\n   sprints\u002Faudits) vs vague. Packaging maturity.\n5. **Evidence & credibility** (12%) — Named clients, quantified outcomes,\n   case-study depth. Proof beyond assertion.\n6. **Enterprise-readiness \u002F commercial maturity** (10%) — Signals they can land\n   and hold SaaS\u002Ffintech\u002FB2B\u002Fenterprise work (process, logos, scale, contracts).\n7. **Thought leadership \u002F content presence** (8%) — Owned POV: writing, talks,\n   newsletters, frameworks. Depth over volume.\n8. **Pricing transparency & engagement model** (5%) — Is pricing\u002Fengagement\n   legible? Productized vs bespoke vs opaque.\n9. **[Client's strategic tension]** (5% as a flag; **score BOTH poles,\n   report separately**) — Read the tension name and axis descriptions from the\n   client's positioning brief. Plot both; the gap is the insight. The client's\n   target quadrant is the single most important finding: who else is already\n   there?\n\n## Scoring rubric (1–5, applies to dimensions 1–8)\n\nAnchor every score to observable evidence. Generic descriptors below; adapt the\nspecifics per dimension but keep the level meaning constant.\n\n- **1 — Absent \u002F generic.** No discernible position or craft; indistinguishable\n  from a template. Active liability.\n- **2 — Below par.** Some intent but inconsistent, derivative, or unconvincing.\n  Wouldn't survive a side-by-side.\n- **3 — Competent \u002F table-stakes.** Solid, professional, unremarkable. Meets\n  expectation, ownable by nobody.\n- **4 — Strong \u002F distinctive.** Clearly above peers; a real strength a buyer\n  would notice and cite.\n- **5 — Category-defining.** Best-in-class, ownable, hard to imitate. Sets the\n  bar others react to.\n\n### Tension axes (dimension 9) — score each 1–5\n\nRead the axis labels and their 1\u002F3\u002F5 anchors from the client's positioning\nbrief. Example anchors for a memorability × credibility tension:\n\n- **Memorability** — 1: forgotten instantly · 3: recognizable in context ·\n  5: unforgettable, talked-about, distinctively owned.\n- **Credibility** — 1: feels risky\u002Famateur · 3: safe, competent,\n  unexciting · 5: enterprise-trusted, obvious safe choice.\n\nPlot competitors on the tension 2×2. The client's target quadrant is named in\nthe positioning brief. Who else occupies that quadrant is the single most\nimportant finding of the benchmark.\n\n## How to collect the data\n\nFor each competitor, work the dimensions in this order (cheapest signal first):\n\n1. **Competitor's own site** — positioning, voice, offer packaging, pricing\n   posture, named clients, manifesto\u002FPOV. Screenshot the homepage + one case\n   study.\n2. **Case studies \u002F work** — evidence depth, quantified outcomes, client names.\n   Distinguish *asserted* (\"we delivered X\") from *proven* (metrics, named,\n   verifiable).\n3. **Review directories** — corroborate clients, project size, engagement model\n   → credibility & enterprise-readiness (e.g. Clutch.co or the niche equivalent).\n4. **LinkedIn** — team size\u002Fmodel, founder narrative, content cadence →\n   thought leadership, model.\n5. **Portfolio \u002F craft platforms** — craft register (use the showcase native to\n   the niche: design boards, showreels, published samples, etc.).\n6. **Content channels** — newsletter\u002Ftalks\u002Fwriting → thought-leadership depth.\n\n**What to record per dimension:** the score, one-line justification, and the\nsource link\u002Fscreenshot that earned it. No score without evidence.\n\n## Bias controls\n\n- **No single composite score.** Report dimension scores and the tension plot\n  separately. A weighted average hides the asymmetry that matters.\n- **Asserted vs proven.** Downgrade credibility\u002Fevidence scores for\n  self-reported claims with no corroboration. Site copy is marketing, not fact.\n- **Aesthetic affinity bias.** Reviewers may over-score studios whose aesthetic\n  they share and under-score rivals' commercial strength. Score craft and\n  credibility independently; a \"boring\" site may be winning bigger clients.\n- **Recency \u002F flashiness bias.** Award-winning, showpiece work dazzles but may\n  lack commercial depth — verify with directories\u002Fclients before scoring\n  credibility.\n- **Survivorship.** The visible, well-marketed studios aren't the whole market;\n  note strong-but-quiet operators found via directories\u002Freviews.\n- **Calibrate across the set, not in isolation.** Before finalizing, re-read\n  scores side-by-side — a \"4\" must mean the same thing for every competitor.\n  Adjust outliers.\n\n## Competitor profile card (output format)\n\nProduce one card per profiled competitor — the atomic unit the report assembles\nfrom:\n\n```\n## \u003CCompetitor name>\n- **Profile \u002F Tier:** \u003Cpositioning stance · specialization · size band> \u002F \u003CDirect | Adjacent | Aspirational>\n- **One-liner:** \u003Chow they position themselves, in their words>\n- **Model \u002F size \u002F geography:** \u003Csolo|micro|boutique> · \u003Cregion> · \u003Cpricing\u002Fengagement model>\n- **Notable clients \u002F evidence:** \u003Cnamed, with proven\u002Fasserted tag>\n\n### Dimension scores\n| Dimension | Score (1–5) | Justification (1 line) | Source |\n|---|---|---|---|\n| Positioning clarity & distinctiveness | | | |\n| Brand voice \u002F verbal distinctiveness | | | |\n| Visual identity & site craft | | | |\n| Service offer & packaging | | | |\n| Evidence & credibility | | | |\n| Enterprise-readiness \u002F commercial maturity | | | |\n| Thought leadership \u002F content presence | | | |\n| Pricing transparency & engagement model | | | |\n\n### Tension plot\n- **[Axis 1 from positioning brief]:** \u003C1–5> — \u003Cwhy>\n- **[Axis 2 from positioning brief]:** \u003C1–5> — \u003Cwhy>\n- **Quadrant:** \u003Chigh\u002Fhigh | high-1\u002Flow-2 | low-1\u002Fhigh-2 | low\u002Flow>\n\n### Read for [client]\n- **Strength to learn from:** \u003C…>\n- **Weakness to exploit \u002F white-space it exposes:** \u003C…>\n- **Threat to [client]:** \u003C…>\n```\n\nHand the completed cards plus the tension plot to `competitive-report-structure`.\n\n## Anti-Patterns\n\n- **Averaging the tension axes.** The two poles of the client's strategic tension must be scored and reported separately. Averaging destroys the insight — the gap between poles is the finding.\n- **Scoring without evidence.** Every score requires a one-line justification and a source link. A score without evidence is an opinion, not a benchmark.\n- **Creating a single composite score.** Report dimension scores individually. A weighted average hides the asymmetric strengths that matter for positioning.\n- **Applying generic rubric anchors without adapting.** The 1–5 anchors must be calibrated to the specific dimension and competitor set. The generic descriptions are a starting point, not a fixed standard.\n- **Running before the competitor set is scoped.** Use competitive-platform-analysis first to produce a tiered, pruned set. Scoring an unscoped list wastes effort on irrelevant competitors.\n\n## Related Skills\n\n- `competitive-platform-analysis` — the prerequisite; produces the tiered competitor set this skill scores.\n- `competitive-report-structure` — the next step; assembles the scored profile cards into a client-deliverable report.\n","# Benchmark Methodology\n\nUse this skill to turn a scoped competitor set into **comparable, defensible\nscores**. Each competitor is assessed on the same nine dimensions, with\nexplicit 1–5 rubrics, then captured in a uniform profile card. Consistency is\nthe point: scores are only useful if the same evidence would earn the same\nnumber for any competitor.\n\n## When to Activate\n\n- A scoped, tiered competitor set from competitive-platform-analysis is ready to score.\n- Need comparable, evidence-anchored scores across competitors — not gut-feel rankings.\n- Client's strategic tension (the paired axes defining their target white-space) has been established.\n- Preparing to produce profile cards for assembly in competitive-report-structure.\n\n## Client positioning brief (establish first)\n\nBefore scoring, establish the client's positioning brief. It supplies:\n\n- **Strategic tension** — the two axes (e.g., memorability × hireability) whose\n  intersection marks the client's target white-space. Dimension 9 is always\n  the client's named tension; report both poles separately, never averaged.\n- **Differentiator** — what makes the client's moat. This informs which\n  dimensions matter most for the client's positioning argument.\n- **Brand balance** — the intended mix of distinct strategic emphases. Strategic\n  recommendations must not break this balance without flagging it.\n\n## Why these dimensions\n\nThe client competes on a **specific tension held across two poles**, not on\nservice breadth. The dimensions are weighted to reflect that moat. Two\ndimensions — the tension poles — are scored **separately and never averaged\ntogether**, because the client's strategic question is precisely whether a rival\nachieves both simultaneously.\n\n## The nine dimensions (with weights)\n\nWeights guide synthesis emphasis, not a single blended score (avoid a false\ncomposite — see Bias controls). Sum = 100%.\n\n1. **Positioning clarity & distinctiveness** (18%) — Is the studio's position\n   sharp, ownable, and instantly legible? Or generic?\n2. **Brand voice \u002F verbal distinctiveness** (15%) — Does the copy have an\n   ownable register, or is it interchangeable agency-speak?\n3. **Visual identity & site craft** (15%) — Quality and ownership of the visual\n   system; site as proof-of-craft.\n4. **Service offer & packaging** (12%) — Productized and legible (named\n   sprints\u002Faudits) vs vague. Packaging maturity.\n5. **Evidence & credibility** (12%) — Named clients, quantified outcomes,\n   case-study depth. Proof beyond assertion.\n6. **Enterprise-readiness \u002F commercial maturity** (10%) — Signals they can land\n   and hold SaaS\u002Ffintech\u002FB2B\u002Fenterprise work (process, logos, scale, contracts).\n7. **Thought leadership \u002F content presence** (8%) — Owned POV: writing, talks,\n   newsletters, frameworks. Depth over volume.\n8. **Pricing transparency & engagement model** (5%) — Is pricing\u002Fengagement\n   legible? Productized vs bespoke vs opaque.\n9. **[Client's strategic tension]** (5% as a flag; **score BOTH poles,\n   report separately**) — Read the tension name and axis descriptions from the\n   client's positioning brief. Plot both; the gap is the insight. The client's\n   target quadrant is the single most important finding: who else is already\n   there?\n\n## Scoring rubric (1–5, applies to dimensions 1–8)\n\nAnchor every score to observable evidence. Generic descriptors below; adapt the\nspecifics per dimension but keep the level meaning constant.\n\n- **1 — Absent \u002F generic.** No discernible position or craft; indistinguishable\n  from a template. Active liability.\n- **2 — Below par.** Some intent but inconsistent, derivative, or unconvincing.\n  Wouldn't survive a side-by-side.\n- **3 — Competent \u002F table-stakes.** Solid, professional, unremarkable. Meets\n  expectation, ownable by nobody.\n- **4 — Strong \u002F distinctive.** Clearly above peers; a real strength a buyer\n  would notice and cite.\n- **5 — Category-defining.** Best-in-class, ownable, hard to imitate. Sets the\n  bar others react to.\n\n### Tension axes (dimension 9) — score each 1–5\n\nRead the axis labels and their 1\u002F3\u002F5 anchors from the client's positioning\nbrief. Example anchors for a memorability × credibility tension:\n\n- **Memorability** — 1: forgotten instantly · 3: recognizable in context ·\n  5: unforgettable, talked-about, distinctively owned.\n- **Credibility** — 1: feels risky\u002Famateur · 3: safe, competent,\n  unexciting · 5: enterprise-trusted, obvious safe choice.\n\nPlot competitors on the tension 2×2. The client's target quadrant is named in\nthe positioning brief. Who else occupies that quadrant is the single most\nimportant finding of the benchmark.\n\n## How to collect the data\n\nFor each competitor, work the dimensions in this order (cheapest signal first):\n\n1. **Competitor's own site** — positioning, voice, offer packaging, pricing\n   posture, named clients, manifesto\u002FPOV. Screenshot the homepage + one case\n   study.\n2. **Case studies \u002F work** — evidence depth, quantified outcomes, client names.\n   Distinguish *asserted* (\"we delivered X\") from *proven* (metrics, named,\n   verifiable).\n3. **Review directories** — corroborate clients, project size, engagement model\n   → credibility & enterprise-readiness (e.g. Clutch.co or the niche equivalent).\n4. **LinkedIn** — team size\u002Fmodel, founder narrative, content cadence →\n   thought leadership, model.\n5. **Portfolio \u002F craft platforms** — craft register (use the showcase native to\n   the niche: design boards, showreels, published samples, etc.).\n6. **Content channels** — newsletter\u002Ftalks\u002Fwriting → thought-leadership depth.\n\n**What to record per dimension:** the score, one-line justification, and the\nsource link\u002Fscreenshot that earned it. No score without evidence.\n\n## Bias controls\n\n- **No single composite score.** Report dimension scores and the tension plot\n  separately. A weighted average hides the asymmetry that matters.\n- **Asserted vs proven.** Downgrade credibility\u002Fevidence scores for\n  self-reported claims with no corroboration. Site copy is marketing, not fact.\n- **Aesthetic affinity bias.** Reviewers may over-score studios whose aesthetic\n  they share and under-score rivals' commercial strength. Score craft and\n  credibility independently; a \"boring\" site may be winning bigger clients.\n- **Recency \u002F flashiness bias.** Award-winning, showpiece work dazzles but may\n  lack commercial depth — verify with directories\u002Fclients before scoring\n  credibility.\n- **Survivorship.** The visible, well-marketed studios aren't the whole market;\n  note strong-but-quiet operators found via directories\u002Freviews.\n- **Calibrate across the set, not in isolation.** Before finalizing, re-read\n  scores side-by-side — a \"4\" must mean the same thing for every competitor.\n  Adjust outliers.\n\n## Competitor profile card (output format)\n\nProduce one card per profiled competitor — the atomic unit the report assembles\nfrom:\n\n```\n## \u003CCompetitor name>\n- **Profile \u002F Tier:** \u003Cpositioning stance · specialization · size band> \u002F \u003CDirect | Adjacent | Aspirational>\n- **One-liner:** \u003Chow they position themselves, in their words>\n- **Model \u002F size \u002F geography:** \u003Csolo|micro|boutique> · \u003Cregion> · \u003Cpricing\u002Fengagement model>\n- **Notable clients \u002F evidence:** \u003Cnamed, with proven\u002Fasserted tag>\n\n### Dimension scores\n| Dimension | Score (1–5) | Justification (1 line) | Source |\n|---|---|---|---|\n| Positioning clarity & distinctiveness | | | |\n| Brand voice \u002F verbal distinctiveness | | | |\n| Visual identity & site craft | | | |\n| Service offer & packaging | | | |\n| Evidence & credibility | | | |\n| Enterprise-readiness \u002F commercial maturity | | | |\n| Thought leadership \u002F content presence | | | |\n| Pricing transparency & engagement model | | | |\n\n### Tension plot\n- **[Axis 1 from positioning brief]:** \u003C1–5> — \u003Cwhy>\n- **[Axis 2 from positioning brief]:** \u003C1–5> — \u003Cwhy>\n- **Quadrant:** \u003Chigh\u002Fhigh | high-1\u002Flow-2 | low-1\u002Fhigh-2 | low\u002Flow>\n\n### Read for [client]\n- **Strength to learn from:** \u003C…>\n- **Weakness to exploit \u002F white-space it exposes:** \u003C…>\n- **Threat to [client]:** \u003C…>\n```\n\nHand the completed cards plus the tension plot to `competitive-report-structure`.\n\n## Anti-Patterns\n\n- **Averaging the tension axes.** The two poles of the client's strategic tension must be scored and reported separately. Averaging destroys the insight — the gap between poles is the finding.\n- **Scoring without evidence.** Every score requires a one-line justification and a source link. A score without evidence is an opinion, not a benchmark.\n- **Creating a single composite score.** Report dimension scores individually. A weighted average hides the asymmetric strengths that matter for positioning.\n- **Applying generic rubric anchors without adapting.** The 1–5 anchors must be calibrated to the specific dimension and competitor set. The generic descriptions are a starting point, not a fixed standard.\n- **Running before the competitor set is scoped.** Use competitive-platform-analysis first to produce a tiered, pruned set. Scoring an unscoped list wastes effort on irrelevant competitors.\n\n## Related Skills\n\n- `competitive-platform-analysis` — the prerequisite; produces the tiered competitor set this skill scores.\n- `competitive-report-structure` — the next step; assembles the scored profile cards into a client-deliverable report.\n",{"name":5,"license":14,"description":7},"main","042b877a2d8a36e89f5ed68cb8e96a6d85a5c08d","plugins\u002Fskills\u002Fcontent-engine\u002Fskills\u002Fcontent-engine\u002Fbenchmark-methodology",0,"https:\u002F\u002Fgithub.com\u002Famine-elhanine\u002Fnexus-code","https:\u002F\u002Fgithub.com\u002Famine-elhanine","2026-11-13 11:19:03",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add amine-elhanine\u002Fnexus-code --skill benchmark-methodology",{"tool":36,"command":37},"bunx","bunx skills add amine-elhanine\u002Fnexus-code --skill benchmark-methodology",{"tool":39,"command":40},"pnpm","pnpm dlx skills add amine-elhanine\u002Fnexus-code --skill benchmark-methodology","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Famine-elhanine\u002Fnexus-code\u002Fblob\u002Fmain\u002Fplugins\u002Fskills\u002Fcontent-engine\u002Fskills\u002Fcontent-engine\u002Fbenchmark-methodology\u002FSKILL.md",true,[],[45,52,59],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M7C735EDGA959324QSDXVVS2","recursive-decision-ledger","Use when the user asks for repeated rollouts, marked decision processes, high-dimensional search, stochastic optimization, local-optima exploration, ensemble comparison, or recursive reasoning with a visible evidence trail.","https:\u002F\u002Fgithub.com\u002Famine-elhanine\u002Fnexus-code\u002Fblob\u002Fmain\u002Fplugins\u002Fskills\u002Frecursive-decision-ledger\u002Fskills\u002Frecursive-decision-ledger\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M7C70R8MQV4HQQSGM8JQ5RQ9","latency-critical-systems","Use for latency-sensitive systems such as realtime dashboards, market data, streaming agents, execution gateways, queues, caches, or HFT-like infrastructure where freshness and p95 latency matter. Use when p95 latency or data freshness matters — realtime dashboards, market data, streaming agents, queues, or caches.","https:\u002F\u002Fgithub.com\u002Famine-elhanine\u002Fnexus-code\u002Fblob\u002Fmain\u002Fplugins\u002Fskills\u002Flatency-critical-systems\u002Fskills\u002Flatency-critical-systems\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":63,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7C6XPX800FCR9S57FJYNS4S","carrier-relationship-management","Codified expertise for managing carrier portfolios, negotiating freight rates, tracking carrier performance, allocating freight, and maintaining strategic carrier relationships. Informed by transportation managers with 15+ years experience. Includes scorecarding frameworks, RFP processes, market intelligence, and compliance vetting. Use when managing carriers, negotiating rates, evaluating carrier performance, or building freight strategies.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Famine-elhanine\u002Fnexus-code\u002Fblob\u002Fmain\u002Fplugins\u002Fskills\u002Fcontent-engine\u002Fskills\u002Fcontent-engine\u002Fcarrier-relationship-management\u002FSKILL.md",[],[]]