SKILLEMALL.ai
GitHub ↗ RU Sign in

AC sales-rhythm-tracker

B2B sales pipeline manager powered by the Alibaba Iron Army (阿里铁军) methodology. Use this skill for daily sales briefings, lead management, pipeline health checks, weekly sprint planning, customer follow-up prioritization, and closing strategy. Triggered by phrases like: "morning sales brief", "add lead", "pipeline review", "who should I call today", "weekly sales plan", "sales update", "close rate", "follow up", "deal stuck", "customer type", "sales sprint".

modbender/skill-library-mcp Hermes author: modbender MIT 9 files · 6 scripts body ≈ 3 075 tokens Open the sourcegithub.com↗ analyzed 2 d ago

B2B sales pipeline manager powered by the Alibaba Iron Army (阿里铁军) methodology.

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureInfrastructureOperations and projectsResearchtype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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: 9. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 463 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)

Process rating: all ten parameters 51/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 7 mutating operations with no state check
  • 55Failures and branches. 1 branches
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 100Steps. 30 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3075 tokens
  • 100Progress reporting. Reports progress
  • low 11 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

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -35 of 6 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 11 example trigger phrases
  • +3Description length 462: enough signal without eating the budget
  • +4Structure: 27 headings
  • +3Step-by-step instructions: 30 items
  • +4Has examples (4 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.