Content
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a thin routing/delegation document that points to other skills and recipes without providing any substantive content about LinkedIn URL lookup itself. It lacks any concrete, actionable guidance—no code, no examples, no validation steps, and no actual instructions for resolving LinkedIn profiles. While the conciseness and structure are acceptable for a delegation pattern, the near-total absence of actionable content severely limits its utility as a standalone skill.
Suggestions
Add concrete, actionable content about the LinkedIn URL lookup process—at minimum, describe the identity validation criteria and expected inputs/outputs so the skill has standalone value.
Include at least one example showing expected input (name + company) and expected output (validated LinkedIn URL) to make the skill actionable.
Add validation/verification steps for identity matching to prevent false positives, as described in the skill's own description.
If this skill is purely a routing shim, consider whether it needs to exist as a separate SKILL.md at all, or consolidate it into the parent meta-skill's routing logic.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Reasonably brief but includes some unnecessary explanation (e.g., 'This is a recipe shortcut' and 'The recipe only covers one part of the task' are somewhat redundant given the instructions). Could be tighter. | 2 / 3 |
Actionability | The skill provides no concrete code, commands, or executable guidance. It is entirely a delegation/routing document that tells Claude to invoke another skill and read another file, with no actual LinkedIn URL lookup instructions or examples. | 1 / 3 |
Workflow Clarity | There is a numbered sequence (invoke meta-skill, follow routing, read recipe), but there are no validation checkpoints, no error handling, and no concrete details about what happens at each step. The workflow is essentially 'go read other files.' | 2 / 3 |
Progressive Disclosure | References a meta-skill and a recipe file with a relative path, which is reasonable structure. However, with no bundle files provided, we cannot verify the referenced paths exist. The skill itself contains almost no substantive content, making it feel like an empty shell rather than a well-structured overview. | 2 / 3 |
Total | 7 / 12 Passed |