supply-chain

Interactive supply chain dashboard mapping suppliers, customers, and financial interdependencies

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/daloopa/skills/supply-chain/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

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

The body is highly actionable with concrete APIs, templates, and citation formats, and its phases are well sequenced, but it suffers from heavy repetition across overlapping sections, lacks explicit validation checkpoints for its large batch data pulls, and is monolithic rather than progressively disclosed into reference files.

Suggestions

De-duplicate the overlapping sections: consolidate the inventory overview, shock analysis, and DOM-safety rules so each appears once and cross-references the canonical location.

Add explicit validate/verify checkpoints for the batch 10-quarter pulls (e.g., confirm series coverage per company and retry on gaps before synthesis), which would lift workflow clarity.

Move the large CSS/HTML template blocks and section scaffolding into reference files under references/ and link to them one level deep, reducing the main SKILL.md to a lean overview.

Dimension	Reasoning	Score
Conciseness	The ~1140-line body reiterates the same material repeatedly (inventory overview in Output Format, Section 5b, and Phase 3b; shock analysis in Output Format, Phases 6b/6c, and Sections 7/7c; DOM-safety stated three times), so while mostly relevant domain content, it could be tightened well beyond its current length.	2 / 3
Actionability	It provides concrete API calls, specific search-keyword lists, copy-paste HTML/CSS/JS templates, exact citation format, file paths, and helper-function definitions, matching the fully-executable score-3 anchor.	3 / 3
Workflow Clarity	Phases 1-6c and the 13-step EXECUTION SEQUENCE are clearly ordered, but the batch 10-quarter pulls across 14-25 companies lack explicit validate/verify checkpoints; per the guidelines missing validation in batch operations caps workflow clarity at 2.	2 / 3
Progressive Disclosure	The skill is monolithic (~1140 lines) with no bundle files and large inline HTML/CSS/section templates that should be split into references, though section structure is clear and external data-access/design-system references are signaled, placing it above a disorganized wall of text.	2 / 3
	Total	9 / 12 Passed

Description

67%Weight 40%Scale 1-3

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 conveys a clear, specific niche and concrete actions but omits any explicit "Use when" trigger guidance and relies on somewhat technical phrasing for the financial angle, capping completeness and trigger-term quality. Adding a trigger clause with common user terms would lift both dimensions.

Suggestions

Append a "Use when..." clause naming natural user triggers, e.g. "Use when the user asks for a supply chain analysis, supplier/customer mapping, or concentration-risk dashboard for a company."

Broaden trigger terms to include common variations like "vendor", "value chain", and "supply chain concentration risk".

Rephrase "financial interdependencies" in plainer terms or pair it with a user-facing phrase to improve trigger-term quality.

Dimension	Reasoning	Score
Specificity	"mapping suppliers, customers, and financial interdependencies" names the supply-chain domain and lists multiple specific concrete actions (mapping three distinct relationship types), matching the score-3 anchor rather than the single-action score-2 example.	3 / 3
Completeness	It clearly states what the skill does ("Interactive supply chain dashboard mapping suppliers, customers, and financial interdependencies") but has no "Use when..." trigger clause; per the judging guidelines a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	It surfaces natural terms ("supply chain dashboard", "suppliers", "customers") but "financial interdependencies" is technical and common variations ("vendor", "value chain", "concentration risk", "supply chain analysis") are missing, so it lands at score 2 rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	Supply-chain mapping with supplier/customer/financial-interdependency triggers is a clear niche unlikely to fire for unrelated skills, matching the score-3 anchor of distinct triggers.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1146 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: openai/plugins
Path: plugins/daloopa/skills/supply-chain/SKILL.md
Commit: 11c74d6

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.