AB Ogment CLI Skill
Securely invoke MCP tools via the Ogment CLI. Access your connected SaaS tools (Linear, Notion, Gmail, PostHog, etc.) through Ogment's governance layer.
Securely invoke MCP tools via the Ogment CLI.
As a process B 65/100 · Nearly there — weak spots: when it triggers, consistency, progress reporting
IntegrationNotionGmailSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
How to improve
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens)
Process rating: all ten parameters 65/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (Ogment CLI Skill) differs from the folder (ogment-agentic-cli)
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 35 steps, 2 vague phrases
- 100Failures and branches. 2 branches, has a failure section
- 100Execution cost. Instruction body is 2142 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 15 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- -214 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 152: enough signal without eating the budget
- +4Structure: 37 headings
- +3Step-by-step instructions: 35 items
- +3Output format is stated explicitly
- +4Has examples (20 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.