apm-communication

Agent communication standards and file-based Message Bus protocol for structured inter-agent messaging.

Quality

55%

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 ./templates/skills/apm-communication/SKILL.md

Quality

Content

57%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 well-structured, lean standards document with some genuinely concrete guidance, but it has actionable gaps (the promised message formats are not shown), reads more as a reference than a workflow, and ships with a dangling reference and unresolved template placeholders. Resolving the placeholders, including a concrete message-format example, and adding the missing bundle file would lift the weaker dimensions.

Suggestions

Add a concrete example of a bus message format inline, since the overview claims the skill covers "shared message formats" but none is shown.

Resolve the {VERSION} and {NEW_CHAT_GUIDANCE} placeholders (or move version info to a versioned section) so the file is not left with template tokens.

Provide the referenced `bus-integration.md` bundle file, or remove/inline the reference so progressive disclosure is not left dangling.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence without explaining basic concepts, though sections like §2.2 Visible Reasoning run slightly long and could be trimmed, placing it at 4 rather than 5.	4 / 5
Actionability	Concrete guidance exists (slug derivation "Frontend Agent" → "frontend-agent", path patterns `.apm/bus/<agent-slug>/`, ID resolution order), but the overview promises "shared message formats" that are never shown in the body, a notable gap keeping it at 3.	3 / 5
Workflow Clarity	Sequencing exists for bus writes ("clears its incoming bus file" then read-before-write) and ID resolution, but this reads as a standards reference rather than a sequenced workflow with explicit validation checkpoints, so 3 rather than 4.	3 / 5
Progressive Disclosure	Sections are well organized and the bus-integration reference is one level deep and clearly signaled, but `bus-integration.md` is not present in the bundle and unresolved placeholders ({VERSION}, {NEW_CHAT_GUIDANCE}) undermine navigation, holding it to 3.	3 / 5
	Total	13 / 20 Passed

Description

53%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 third-person, specific to its niche, and distinguishable from generic skills, but it lacks an explicit "Use when" trigger clause and offers only minimal concrete action enumeration. Adding trigger guidance and one or two more concrete actions would raise completeness and specificity.

Suggestions

Append an explicit trigger clause, e.g. "Use when coordinating multiple agents via the file-based Message Bus or when an unmanaged agent needs to join bus communication."

Name 1-2 more concrete actions (e.g. "resolves agent IDs, validates bus identity, derives agent slugs") to lift specificity from 3 to 4.

Include natural synonyms or phrasings users might say (e.g. "agent messaging", "bus directory") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("agent communication standards", "file-based Message Bus protocol") and the concrete capability of "structured inter-agent messaging", but states what the skill defines rather than enumerating multiple concrete actions, so it stops at 3 rather than 4.	3 / 5
Completeness	It clearly states what the skill does (defines communication standards and the Message Bus protocol) but provides no "Use when..." trigger clause; per the rubric a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant niche terms like "agent communication", "Message Bus", and "inter-agent messaging" are present, but there are no synonyms, file extensions, or common user phrasings, keeping it at 3 rather than 4.	3 / 5
Distinctiveness Conflict Risk	"File-based Message Bus protocol for structured inter-agent messaging" carves a clear niche with distinct triggers and low conflict risk, but within a family of related APM skills some overlap remains, so 4 rather than 5.	4 / 5
	Total	13 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: sdi2200262/agentic-project-management
Path: templates/skills/apm-communication/SKILL.md
Commit: 096fa79

Reviewed: 2 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.