SKILLEMALL.ai

AC meeting-os

Auto meeting notes and action item execution loop. Trigger this skill whenever the user mentions meeting notes, meeting summary, action items, follow-up, transcript, recording, Zoom summary, Teams meeting, Tencent Meeting, Feishu meeting, WeCom meeting, upload audio, upload video, meeting template, task creation.

ClawHub Agent Skills author: DTTNpole-commits v1.0.9 MIT-0 13 files body ≈ 1 214 tokens Open the sourceclawhub.ai analyzed 4 d ago

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

TemplateNotionPersonal productivityWriting and documentsInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
78
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

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: 12. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 5, column 16: argument-hint: Free: 10 meetings/month. Pro billing via SkillPay: skillpay.me ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value

    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
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 7 mutating operations with no state check
    • 40Consistency. Frontmatter name (meeting-os) differs from the folder (meetingos)
    • 60Tools and files. Uses tools (python) that frontmatter does not declare
    • 60Failures and branches. 2 branches
    • 70When it triggers. States when to use, but not when not to
    • 100Steps. 44 steps
    • 100Execution cost. Instruction body is 1214 tokens
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

    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)
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +3Description length 314: enough signal without eating the budget
    • +4Structure: 7 headings
    • +3Step-by-step instructions: 44 items
    • +4Has examples (4 code blocks)
    • +3All 7 scripts are documented
    • +1License stated

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

    External checks

    ClawHub: suspicious
    This meeting automation skill is not clearly malicious, but it needs review because it can send meeting content to external workplace tools under broad triggers and has inconsistent packaging and disclosure.
    LLM: suspicious (high) · VirusTotal: · 29 May 2026