agent-supply-chain-newsletter
Generate the Agent Supply Chain newsletter by researching team activity on GitHub and Confluence, then creating a Confluence draft and Gmail draft
61
72%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/agent-supply-chain-newsletter/SKILL.mdQuality
Discovery
67%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 about what it does and names a clear, distinctive workflow involving multiple concrete tools and outputs. Its main weakness is the lack of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The trigger terms are adequate but narrowly tied to the specific newsletter name.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user asks to generate, draft, or prepare the Agent Supply Chain newsletter or team activity digest.'
Include natural trigger term variations such as 'weekly newsletter', 'team update', 'supply chain digest', or 'activity summary' to improve matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: researching team activity on GitHub and Confluence, creating a Confluence draft, and creating a Gmail draft. These are clear, actionable steps. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (generate newsletter by researching and drafting), but lacks an explicit 'Use when...' clause. The when is only implied by the task description itself, which caps this at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'newsletter', 'GitHub', 'Confluence', 'Gmail draft', and the specific name 'Agent Supply Chain'. However, it's very specific to one newsletter name and may miss variations like 'weekly update', 'team digest', or 'supply chain report'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'Agent Supply Chain newsletter' and the unique combination of GitHub research, Confluence drafting, and Gmail drafting. Very unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with a clear multi-step workflow, concrete tool invocations, and specific parameters throughout. Its main weakness is that all content is in a single file with no supporting bundle files, which means the newsletter format guide and configuration details are inline rather than referenced. Minor verbosity in the format description section could be trimmed.
Suggestions
Extract the newsletter format template (header structure, section organization, footer) into a separate NEWSLETTER_FORMAT.md reference file to reduce inline bulk and allow independent updates.
Consider creating a TEAM_CONFIG.md with space IDs, email addresses, and other configuration constants that may change over time, keeping the main skill focused on workflow logic.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and avoids explaining concepts Claude already knows, but some sections could be tightened—e.g., the newsletter format description in Step 2 is somewhat redundant given that it also instructs Claude to read past newsletters for format reference. The step-by-step structure is appropriate for the complexity but has minor verbosity. | 2 / 3 |
Actionability | The skill provides fully concrete, executable commands (gh CLI calls, specific MCP tool names with parameters, exact CQL queries, specific space IDs, email addresses, and content types). Every step has copy-paste-ready guidance with specific tool invocations and parameters. | 3 / 3 |
Workflow Clarity | The 7-step workflow is clearly sequenced with logical dependencies (gather members → read format → research GitHub → research Confluence → synthesize → create outputs → present). It includes validation checkpoints: asking the user about exclusions in Step 1, applying a filter criterion in Step 5, and a review/verification checklist in Step 7 (send to self first, get review before publishing). | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but everything is inline in a single file. Given the complexity (newsletter format guide, team member lists, space IDs, etc.), some content like the newsletter format template or the list of Confluence spaces could be split into referenced files. However, no bundle files exist to support this, and the inline content is reasonably organized. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- DataDog/datadog-agent
- Commit
a41685a
- 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.