Install any skill in seconds. Free to start, no credit card required.
Get Started Free →davekilleen/meeting-prep
Prepare for a specific upcoming meeting by gathering attendee context, history and related topics.
Passed 10 of 17 test cases with the skill, and 3 of 17 without it.
and 10 more in the full report
10 fixed4 passed either way10 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
An attendee named 'Elena Rostova' in an upcoming meeting does not have a person page linked in her calendar invite record. Which vault folders should be searched to locate her person page?
| Checked | Without skill | With skill |
|---|---|---|
| Searches 05-Areas/People/Internal/ and 05-Areas/People/External/ for person page records. | Missed | Passed |
The instructions your model reads when the skill loads.
Run inline in the current conversation by default, so this work can see what the user has already discussed, decided, or settled this session. Do not fork merely because this skill was selected. Only run in the background when the user explicitly asks for a background run or the host has already obtained a specific background-work approval for this run.
This skill stays inline as described above: it keeps session awareness, it asks the user the questions, and it owns every interactive step. What it does NOT do inline is the bulk read-gathering, which on a mature vault (hundreds of notes, thousands of indexed messages, a live calendar and multiple integrations) can be large enough to exhaust the main conversation before the useful work starts.
So the gathering phase is delegated to one general-purpose subagent via the
Agent tool, using the self-contained prompt in this skill's
AGENT_INSTRUCTIONS.md:
.agents/skills/meeting-prep/AGENT_INSTRUCTIONS.md.{{TARGET_DATE}}, {{MEETING_TITLE}},
{{ATTENDEE_RECORDS}}). {{ATTENDEE_RECORDS}} is the filtered JSON array
from the selected invite, preserving name, person_page, email,
status, type, and is_current_user for each attendee. For attendees the
user supplied manually, use the same fields with unknown values set to
null, type set to Person, and is_current_user set to false.subagent_type: "general-purpose", that prompt, and
a short description.Spot-check before presenting: the brief names person pages, projects and past meetings. Confirm a sample of those files actually exist before repeating their content to the user, and drop anything you cannot stand behind. A subagent's report is a claim, not evidence.
The subagent inherits MCP connections, runs in its own context, and that context is freed when it completes, so only its findings reach this conversation.
test cases passed, vs 3 / 17 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.