CtrlK
BlogDocsLog inGet started
Tessl Logo

app-server-events-sync

Maintain CodexMonitor and Codex app-server protocol parity. Use when asked to audit supported or missing app-server notifications/requests, trace event routing, diagnose schema drift in app-server payloads, or update docs/app-server-events.md after upstream Codex changes.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 a tight, well-structured runbook: concrete file paths and commands, a sequenced workflow with an explicit validation checkpoint, and clean one-level-deep references. It respects token budget while remaining fully actionable.

DimensionReasoningScore

Conciseness

The body is a lean runbook of workflow steps and file paths with no concept explanation or padding; it assumes Claude's competence and every line earns its place.

3 / 3

Actionability

Cites exact files (e.g. 'src/utils/appServerEvents.ts', '../Codex/codex-rs/app-server-protocol/src/protocol/v2.rs') and executable commands ('npm run typecheck', 'cd src-tauri && cargo check'), with the referenced quick-commands.md providing copy-paste bash.

3 / 3

Workflow Clarity

A clearly sequenced 6-step process culminating in an explicit 'Validate' checkpoint with concrete verification commands, giving a clear feedback loop.

3 / 3

Progressive Disclosure

Clear overview with well-signaled one-level-deep references — 'references/quick-commands.md' (verified present) and 'docs/app-server-events.md' — with detail appropriately split out rather than inlined.

3 / 3

Total

12

/

12

Passed

Description

100%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.

A strong description: third-person, concrete, and explicit about both capability and triggers, scoped to a distinct niche. It names specific actions and natural trigger phrasings without padding or over-claiming.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'audit supported or missing app-server notifications/requests', 'trace event routing', 'diagnose schema drift in app-server payloads', and 'update docs/app-server-events.md' — rather than vague language.

3 / 3

Completeness

Clearly answers both what ('Maintain CodexMonitor and Codex app-server protocol parity') and when via an explicit 'Use when asked to...' clause with enumerated triggers.

3 / 3

Trigger Term Quality

The 'Use when asked to audit... trace event routing... diagnose schema drift' phrasings are natural terms a user of this integration would actually say, with good coverage of the skill's trigger surface.

3 / 3

Distinctiveness Conflict Risk

The niche is tightly scoped to CodexMonitor/Codex app-server protocol parity with distinct, specialized triggers, making conflict with other skills very unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Dimillian/CodexMonitor
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.