SKILLEMALL.ai
GitHub ↗ RU Sign in

BF foundation-meeting-agenda

Produces an attendee-facing agenda that sets what will be discussed, who owns each topic, and how time will be spent. Supports ten meeting type variants (standup, planning, review, decision-making, brainstorm, 1-on-1, stakeholder-review, project-kickoff, working-session, exec-briefing). Emits a shareable summary suitable for Slack or email plus a full agenda with time-boxed topics, type tags, owners, attendee prep, and logistics.

product-on-purpose/pm-skills Agent Skills author: product-on-purpose Apache-2.0 5 files body ≈ 2 459 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Produces an attendee-facing agenda that sets what will be discussed, who owns each topic, and how time will be spent.

As a process F 42/100 · Will not run — References files that are not bundled: ../../docs/reference/skill-families/meeting-skills-contract.md, ../foundation-meeting-brief/SKILL.md, ../foundation-meeting-recap/SKILL.md

GeneratorSlackOperations and projectsWriting and documentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
73
Run on models
none yet
Process rating
F
42/100
Will not run
References files that are not bundled: ../../docs/reference/skill-families/meeting-skills-contract.md, ../foundation-meeting-brief/SKILL.md, ../foundation-meeting-recap/SKILL.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
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: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../../docs/reference/skill-families/meeting-skills-contract.md
  • warning missing-ref reference to a missing file: ../foundation-meeting-brief/SKILL.md
  • warning missing-ref reference to a missing file: ../foundation-meeting-recap/SKILL.md
  • warning missing-ref reference to a missing file: ../foundation-stakeholder-update/SKILL.md

Process rating: all ten parameters 42/100

Will not run. References files that are not bundled: ../../docs/reference/skill-families/meeting-skills-contract.md, ../foundation-meeting-brief/SKILL.md, ../foundation-meeting-recap/SKILL.md
  • 0Tools and files. 4 referenced file(s) missing: ../../docs/reference/skill-families/meeting-skills-contract.md, ../foundation-meeting-brief/SKILL.md, ../foundation-meeting-recap/SKILL.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 4 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 65Failures and branches. 3 branches
  • 85Steps. 62 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2459 tokens

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
  • +4No input/output examples
  • +2Single-language instructions
  • +3Description length 433: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 62 items
  • +4Reference files are cited in the instructions (1 of 2)
  • +1License stated

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