Automated summary

Turns calendar invites and email threads into a one-page brief before an external meeting: who is in the room, what was left open, recent company news, and three questions to ask.

Strengths

Requires a source and a date for every line, and bans adjectives lifted from the prospect's homepage
Ships an explicit escape hatch ("nothing has changed since your last call") so briefs are never padded
Delivers the brief to the meeting owner only, never to external attendees
Fixed four-part structure (attendees, open items, changes, three questions) makes the output predictable

Limitations

Assumes google_calendar and gmail tools are connected and the workspace domain is known, which is how it decides who counts as external
Reads only the most recent thread and six months of news, with no web search, so recent changes can be missed
Produces the brief alone — no follow-up tracking or CRM logging

When to use it

Right before an external client or prospect call when you need a fast, sourced one-pager.

When not to use it

For internal meetings, or when the situation demands full due diligence and financial analysis rather than a quick brief.

Security analysis

Safe

Quality score86/100

The skill only uses the two declared tools (google_calendar, gmail) for their stated purpose: read the next external meeting, read prior threads, and send a brief to the meeting owner. There is no bash or shell access, no network calls, no credential handling, no obfuscation, and no destructive or exfiltration behavior; the frontmatter allowed-tools match the declared tools. The only meaningful side effect is an outbound email, and the text constrains recipients to the meeting owner and forbids sending to attendees. No instructions embedded in the content attempt to redirect the auditor.

Findings

•Autonomously sends email (Gmail) without a confirmation step; scope is limited by an explicit rule to the meeting owner only, so impact is low but the send is still an unconfirmed side effect.
•The brief is synthesized from untrusted external inputs (calendar invites and email threads from outside the workspace domain), so injected instructions in an attendee's message could influence the generated brief that is then emailed internally; no instruction to act on email content exists, which limits the risk.

How this analysis is made

Examples

Pre-call brief

Brief me before my next call with an external company — pull the invite from my calendar and tell me who I'm meeting.

Who is in the room

Who am I meeting tomorrow at 10am, and what's been going on at their company in the last six months?

Research a prospect

Research this company before my call: check our last email thread with them, note anything new since then, and send me a one-page brief with three questions to ask.

name: research-a-company-before-a-call description: "Use before an external meeting: read the calendar invite, work out who is in the room and what their company has been doing, and send a one-page brief to the person whose meeting it is." license: Apache-2.0 compatibility: ">=1.0" metadata: display_name: Research a company before a call author: Alfera triggers: - brief me before this call - who am I meeting - research this company allowed-tools:

google_calendar
gmail

Research a company before a call

Name: Research a company before a call
Author: Skills Guide Bot

What to do

Take the next external meeting from the calendar. External means at least one attendee outside the workspace domain.
Find the last thread with any of those attendees. Whatever was promised or left open there is the top of the brief.
Find what changed at their company in the last six months: a hire, a launch, a raise, a move. Date everything.
Write one page: who is in the room, what is open from last time, what changed, and three questions worth asking.

Rules

Everything on the page has a source and a date. No adjectives from their homepage.
If you found nothing worth saying, say "nothing has changed since your last call" and stop. A padded brief gets skimmed once and then never opened again.
Send it to the meeting owner only. Never to the attendees.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/research-a-company-before-a-call-mvda87hw/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/research-a-company-before-a-call-mvda87hw' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/research-a-company-before-a-call-mvda87hw/download' --output '.skill-downloads/research-a-company-before-a-call-mvda87hw/SKILL.md.part' && mv '.skill-downloads/research-a-company-before-a-call-mvda87hw/SKILL.md.part' '.skill-downloads/research-a-company-before-a-call-mvda87hw/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Environment declared by the author: >=1.0

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code

test -f '.skill-downloads/research-a-company-before-a-call-mvda87hw/SKILL.md' && test -s '.skill-downloads/research-a-company-before-a-call-mvda87hw/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/research-a-company-before-a-call' && cp -R '.skill-downloads/research-a-company-before-a-call-mvda87hw' '.claude/skills/research-a-company-before-a-call'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation

openskills install './.skill-downloads/research-a-company-before-a-call-mvda87hw'

openskills read 'research-a-company-before-a-call-mvda87hw'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/research-a-company-before-a-call-mvda87hw/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

PDF Reader

Productivity

Read and extract text from PDF files, including documents, reports, contracts, and spreadsheets. Works with local files, URLs, and WhatsApp attachments. Use whenever PDF content is needed, even if not explicitly requested.

Claude CodeCursorCodexbeginnerSafe 20,122

Skills Guide Bot