CtrlK
BlogDocsLog inGet started
Tessl Logo

carrier-relationship-management

Codified expertise for managing carrier portfolios, negotiating freight rates, tracking carrier performance, allocating freight, and maintaining strategic carrier relationships.

66

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is carrier-relationship-management in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a dense, highly actionable expert playbook with strong progressive disclosure into real reference files. Its main weakness is mild verbosity from a duplicated 'When to Use' section and a few expandable rhetorical asides.

DimensionReasoningScore

Conciseness

The body is dense with domain-specific facts Claude does not already know (FMCSA insurance tiers, OTRI thresholds, scorecard targets), but minor redundancy such as the duplicated 'When to Use' section and a few rhetorical flourishes could be trimmed.

4 / 5

Actionability

Guidance is fully actionable throughout: named tools (DAT RateView, Greenscreens, FMCSA SAFER), specific thresholds (OTD >=95%, tender acceptance >=90%, claims <0.5%), numeric decision cutoffs, and concrete escalation timelines.

5 / 5

Workflow Clarity

Multi-step processes (RFP, carrier selection, exit criteria) are clearly sequenced with checkpoints like the 30-day trial review and 30-day parallel cutover, but not every workflow has an explicit validate-then-retry feedback loop.

4 / 5

Progressive Disclosure

The body is an overview with three clearly signaled, one-level-deep references (edge-cases.md, communication-templates.md, decision-frameworks.md) that are real files, with brief inline summaries deferring full detail to those files.

5 / 5

Total

18

/

20

Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and clearly niched, but it omits any explicit 'when to use' guidance, which caps its completeness. Adding a concrete trigger clause would lift the strongest dimension that is currently weakest.

Suggestions

Append a 'Use when...' clause naming concrete triggers (e.g., 'Use when running freight RFPs, renegotiating linehaul or fuel surcharge tables, building carrier scorecards, or vetting FMCSA compliance').

Add natural synonyms users say such as 'RFP', 'routing guide', 'tender acceptance', and 'brokerage' to broaden trigger-term coverage.

Keep the current concrete action list but pair each with the trigger context so both 'what' and 'when' are explicit in one sentence.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions across the full carrier lifecycle ('managing carrier portfolios, negotiating freight rates, tracking carrier performance, allocating freight, and maintaining strategic carrier relationships'), matching the comprehensive-coverage anchor.

5 / 5

Completeness

The 'what' is clearly and specifically stated, but there is no 'Use when...' or equivalent trigger clause, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Natural domain terms like 'negotiating freight rates', 'carrier performance', and 'allocating freight' are present, but common synonyms such as 'RFP', 'routing guide', and 'scorecards' are absent, so it falls just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

It targets a narrow freight/transportation niche with distinct triggers and minimal overlap risk with unrelated skills, matching the clear-niche anchor.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.