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.

61

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/carrier-relationship-management/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 body is a dense, highly actionable carrier-management playbook with clear workflows and well-signaled references. Its weakness is verbosity — narrative scene-setting and color commentary could be trimmed for token efficiency.

Suggestions

Tighten the 'Role and Context' paragraph and remove color commentary (e.g. the 'because when the market tightens…' aside) to recover tokens without losing actionable guidance.

Consider pushing the inlined Core Knowledge detail (rate components, scorecard metric definitions) into a reference file so SKILL.md reads more cleanly as an overview.

DimensionReasoningScore

Conciseness

Mostly efficient expert content, but includes narrative color and scene-setting ('because when the market tightens, your carriers' willingness to cover your freight depends on how you treated them…') that could be tightened without losing actionable value.

3 / 5

Actionability

Highly actionable throughout — concrete dollar thresholds, percentage targets, a numbered carrier-selection decision tree, scorecard red flags, and an explicit escalation table with timelines give copy-paste-ready guidance for common cases.

5 / 5

Workflow Clarity

Multi-step processes (RFP, carrier selection, exit criteria) are clearly sequenced with checkpoints such as the 30-day trial review and 30-day parallel routing-guide period; minor validation gaps keep it just below a 5.

4 / 5

Progressive Disclosure

Good structure with three real one-level-deep references (edge-cases.md, decision-frameworks.md, communication-templates.md) clearly signaled via a dedicated Additional Resources section; the inlined body is somewhat heavy, leaving minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

71%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 niche-scoped, listing five concrete capabilities. Its main weakness is the absence of an explicit 'Use when…' trigger clause and the omission of colloquial domain trigger terms.

Suggestions

Add a 'Use when…' clause naming concrete triggers, e.g. running freight RFPs, building routing guides, or creating carrier scorecards.

Include colloquial trigger terms practitioners actually say — 'RFP', 'routing guide', 'scorecard', 'tender', 'linehaul' — alongside the formal phrasing.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'managing carrier portfolios, negotiating freight rates, tracking carrier performance, allocating freight, and maintaining strategic carrier relationships' — with comprehensive coverage of the domain.

5 / 5

Completeness

Clearly answers 'what' with five named actions, but provides no 'Use when…' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Good natural domain keywords ('freight rates', 'carrier performance', 'allocating freight'), but misses colloquial triggers a practitioner would actually say such as RFP, routing guide, scorecard, and tender.

4 / 5

Distinctiveness Conflict Risk

The carrier/freight niche is mostly distinct with minimal conflict risk, though a broad 'strategic carrier relationships' framing leaves minor overlap with adjacent supply-chain or procurement skills.

4 / 5

Total

16

/

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.