Doc Coauthoring
aws-samples/sample-strands-agent-with-agentcore
Guide users through a structured workflow for co-authoring documentation.
Brief an event supplier so they quote accurately and deliver what you pictured — the outcome, the constraints, the deliverables, and the questions you need answered in the quote.
Install Event Vendor Brief
$ npx skills add mohitagw15856/pm-claude-skills --skill event-vendor-brief -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills event-vendor-brief --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/event-vendor-brief .claude/skills/event-vendor-brief && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "event-vendor-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/event-vendor-brief into .claude/skills/event-vendor-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-vendor-brief", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/event-vendor-briefType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill event-vendor-brief -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills event-vendor-brief --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/event-vendor-brief .agents/skills/event-vendor-brief && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "event-vendor-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/event-vendor-brief into .agents/skills/event-vendor-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-vendor-brief", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill event-vendor-brief -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills event-vendor-brief --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/event-vendor-brief .cursor/skills/event-vendor-brief && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "event-vendor-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/event-vendor-brief into .cursor/skills/event-vendor-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-vendor-brief", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/event-vendor-brief--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill event-vendor-brief -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills event-vendor-brief --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/event-vendor-brief .gemini/skills/event-vendor-brief && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "event-vendor-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/event-vendor-brief into .gemini/skills/event-vendor-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-vendor-brief", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills event-vendor-briefInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill event-vendor-brief -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/event-vendor-brief .github/skills/event-vendor-brief && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "event-vendor-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/event-vendor-brief into .github/skills/event-vendor-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-vendor-brief", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill event-vendor-brief -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills event-vendor-brief --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/event-vendor-brief .opencode/skills/event-vendor-brief && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "event-vendor-brief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/event-vendor-brief into .opencode/skills/event-vendor-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "event-vendor-brief", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
event-vendor-brief- GitHub stars
- 1.4k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 763 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Brief an event supplier so they quote accurately and deliver what you pictured — the outcome, the constraints, the deliverables, and the questions you need answered in the quote.
- Works in 7 steps: Brief the outcome first. 'Guests should… → Then fix the variables that move price.… → Give a budget range. Withholding it… → …
- Asked to brief an event supplier
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: Brief the Outcome,… and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Event Vendor Brief is an agent skill from mohitagw15856/pm-claude-skills. Brief an event supplier so they quote accurately and deliver what you pictured — the outcome, the constraints, the deliverables, and the questions you need answered in the quote. Use when asked to brief an event supplier, write a vendor brief for caterers, AV, or production, send an RFP for an event, or compare supplier quotes that are not comparable. Produces the outcome brief, the deliverables and constraints, the quote-response template that makes bids comparable, the evaluation criteria, and the questions…
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Sales & Support, covering Proposals and quotes. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to brief an event supplier
- Write a vendor brief for caterers
- Send an RFP for an event
- Compare supplier quotes that are not comparable
Example prompts
- “/event-vendor-brief”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Brief the outcome first. 'Guests should be able to hold a conversation while eating' tells a supplier more than a speaker specification…
- Then fix the variables that move price. Headcount, duration, service style, access window, and get-out time. Any of these left vague and…
- Give a budget range. Withholding it produces quotes aimed at an imagined number and wastes two rounds. A range is not a weakness.
- Mandate the response format. Same line items, same order, same inclusions and exclusions. This single step is what makes comparison…
- State the evaluation criteria and weights. Suppliers respond to what is measured, and it keeps your own decision honest later.
- Ask what they need from you. The good suppliers answer this well, and it surfaces your own gaps early.
- Send the same brief to everyone, at the same time. Otherwise you are comparing responses to different questions.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Event Vendor Brief loads about 1.5k tokens when it runs. Until then it costs about 140 tokens; SKILL.md has 763 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 763 words, ~1,461 tokens.
Download SKILL.mdSave it as
.claude/skills/event-vendor-brief/SKILL.md (or your agent's skills folder).- name
- event-vendor-brief
- description
- Brief an event supplier so they quote accurately and deliver what you pictured — the outcome, the constraints, the deliverables, and the questions you need answered in the quote. Use when asked to brief an event supplier, write a vendor brief for caterers, AV, or production, send an RFP for an event, or compare supplier quotes that are not comparable. Produces the outcome brief, the deliverables and constraints, the quote-response template that makes bids comparable, the evaluation criteria, and the questions each supplier must answer.
Event Vendor Brief
Three quotes that cannot be compared is a briefing failure, not a supplier one. Each priced a different event because each was told a different amount. This writes the brief that fixes the variables — outcome, constraints, deliverables, and the exact response format — so the quotes come back on the same basis and the cheapest one is actually the cheapest.
What This Skill Produces
- The outcome brief — what the supplier is being asked to achieve, not just to provide
- Deliverables and constraints — the specifics that drive price: quantities, timings, access, and restrictions
- A quote-response template — the structure every supplier must return, which is what makes bids comparable
- Evaluation criteria with weights — stated up front, including how price is weighted against everything else
- The questions each supplier must answer — capability, capacity, contingency, and what they need from you
- The information they need from you — venue details, access, timings, and contacts, supplied once rather than repeatedly
Required Inputs
Ask for these if not provided:
- The event — type, date, venue, headcount, format, and the feel you are aiming for
- The scope for this supplier — what you want them to cover, and what someone else is covering
- The constraints — budget range, venue restrictions, access times, power, noise limits, curfew
- The deadline — when quotes are needed and when you will decide
- What matters most — price, reliability, creativity, sustainability, or experience with this venue
Framework: Brief the Outcome, Fix the Variables, Standardise the Response
- Brief the outcome first. 'Guests should be able to hold a conversation while eating' tells a supplier more than a speaker specification, and lets them bring expertise you do not have.
- Then fix the variables that move price. Headcount, duration, service style, access window, and get-out time. Any of these left vague and every quote will assume differently.
- Give a budget range. Withholding it produces quotes aimed at an imagined number and wastes two rounds. A range is not a weakness.
- Mandate the response format. Same line items, same order, same inclusions and exclusions. This single step is what makes comparison possible.
- State the evaluation criteria and weights. Suppliers respond to what is measured, and it keeps your own decision honest later.
- Ask what they need from you. The good suppliers answer this well, and it surfaces your own gaps early.
- Send the same brief to everyone, at the same time. Otherwise you are comparing responses to different questions.
Output Format
Show full SKILL.md (355 more words)Show less
Supplier brief: [discipline] · [event] · [date]
Event: [type, date, venue, headcount, format] · The feel: [in a sentence]
Outcome sought: [what success looks like from the guest's point of view]
Scope
- In scope for you: [list]
- Covered by others: [list, and who]
Constraints: venue [access window, load-in route, lift, power available, noise limit, curfew] · budget range [amount–amount] · [other]
Required response format — please return exactly these headings
- Approach — [how you would achieve the outcome]
- Itemised costs — [line, quantity, unit, total] with inclusions and exclusions stated separately
- Crew — [number, roles, arrival and departure times]
- Equipment/materials — [list]
- Contingency — [what you do if X fails]
- What you need from us — [access, power, information, decisions and by when]
- References — [two comparable events]
Evaluation: [criterion — weight]% each, totalling 100
Dates: questions by [date] · quotes by [date] · decision [date] · event [date]
Contact: [name, email, phone]
Quality Checks
- The outcome is briefed before the specification
- Every price-moving variable is fixed: headcount, duration, service style, access, get-out
- A budget range is given
- A mandatory response format is specified so bids arrive comparable
- Evaluation criteria and weights are stated up front
- Suppliers are asked what they need from you
- The identical brief went to every supplier at the same time
Anti-Patterns
- Specifying equipment instead of outcome. Buys you the supplier's stock list, not their expertise.
- Withholding the budget. Costs two rounds of quoting and produces irrelevant proposals.
- No mandated response format. Guarantees incomparable quotes and a decision made on presentation quality.
- Leaving access and get-out vague. The two largest hidden cost drivers in event supply.
- Different briefs to different suppliers. Whatever you learn from the comparison is noise.
- Not asking what they need from you. The gaps surface on the day instead.
- Choosing on headline price. The exclusions are where the difference actually is.
Example Trigger Phrases
- "Write a brief for an AV supplier for our conference"
- "Our catering quotes are impossible to compare — what should the brief have said?"
- "Write an RFP for event production"
- "How do I brief a supplier when I do not know the technical details?"
- "What should I ask suppliers to include in their quote?"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/event-vendor-brief of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Event Vendor Brief next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Event Vendor Brief this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Doc Coauthoringaws-samples/sample-strands-agent-with-agentcore | 195 | 40 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Audit Onboarding Proposalhoangnb24/repository-harness | 1.2k | — | ~4k | Automated safety check: Pass | MIT | |
| No Negative EchoLB623/no-negative-echo | 900 | — | ~965 | Automated safety check: Pass | MIT | |
| GEO Service Proposal Generatorzubair-trabzada/geo-seo-claude | 11k | — | ~3k | Automated safety check: Notes | MIT | |
| Architectural ProposalsFritzAndFriends/SharpSite | 145 | 2 repos | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
- Official
Audit Onboarding Proposal
hoangnb24/repository-harness
Use only when the user explicitly invokes $audit-onboarding-proposal.
No Negative Echo
LB623/no-negative-echo
Prevent 此地无银三百两式 residue: finalize artifacts without echoing rejected session-only alternatives into labels, metadata, commits, PRs, or handoffs.
GEO Service Proposal Generator
zubair-trabzada/geo-seo-claude
Builds a client-ready AI-search-optimization proposal from an existing GEO audit, with pricing tiers, an ROI estimate and a markdown document ready to send.
Architectural Proposals
FritzAndFriends/SharpSite
How to write comprehensive architectural proposals that drive alignment before code is written
Counter Proposal Generator
zubair-trabzada/ai-legal-claude
Generates specific counter-proposals for every unfavorable clause, with replacement language, negotiation talking points, and a ready-to-send email template
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Event Vendor Brief
What does Event Vendor Brief do?
Brief an event supplier so they quote accurately and deliver what you pictured — the outcome, the constraints, the deliverables, and the questions you need answered in the quote. Event Vendor Brief is an agent skill from mohitagw15856/pm-claude-skills. Brief an event supplier so they quote accurately and deliver what you pictured — the outcome, the constraints, the deliverables, and the questions you need answered in the quote.
When should I use Event Vendor Brief?
Event Vendor Brief fits situations like: asked to brief an event supplier; write a vendor brief for caterers; send an RFP for an event; compare supplier quotes that are not comparable.
How do I install Event Vendor Brief in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill event-vendor-brief -a claude-code`. Or copy the skill folder (skills/event-vendor-brief in mohitagw15856/pm-claude-skills) into .claude/skills/event-vendor-brief in your project. Claude Code loads it when a task matches its description.
How do I install Event Vendor Brief in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill event-vendor-brief -a codex`. Or copy the skill folder (skills/event-vendor-brief in mohitagw15856/pm-claude-skills) into .agents/skills/event-vendor-brief in your project. Codex loads it when a task matches its description.
Can I use Event Vendor Brief in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill event-vendor-brief -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/event-vendor-brief, .gemini/skills/event-vendor-brief, .github/skills/event-vendor-brief and .opencode/skills/event-vendor-brief in your project.
What does Event Vendor Brief need to run?
SKILL.md names no scripts, command-line tools or credentials: Event Vendor Brief is instructions for the agent only.
Does Event Vendor Brief access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Event Vendor Brief safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Event Vendor Brief use?
Event Vendor Brief is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Event Vendor Brief use?
About 1.5k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Event Vendor Brief?
Skills that share tags, products or a category with Event Vendor Brief: Doc Coauthoring (aws-samples/sample-strands-agent-with-agentcore, 195 stars), Audit Onboarding Proposal (hoangnb24/repository-harness, 1.2k stars), No Negative Echo (LB623/no-negative-echo, 900 stars) and GEO Service Proposal Generator (zubair-trabzada/geo-seo-claude, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Event Vendor Brief?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.