corporate-event-strategy SKILL.md skillA
corporate-event-strategy from samber/dev-event-organizer-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add samber/dev-event-organizer-skills/corporate-event-strategy@v1.0.1Pins v1.0.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- samber/dev-event-organizer-skills
- Path
skills/corporate-event-strategy/SKILL.md- Versions recorded
- 2
- Latest version
- v1.0.1, committed Aug 25, 2026
- First version recorded
- Aug 25, 2026
- Size
- 24,702 bytes
- Repository stars
- 4
- License
- MIT
Decide what a company-run technical event is funded to accomplish, before anyone plans it - the goal mix (ecosystem goodwill, developer adoption, customer retention, sales pipeline, or a blend), who owns the budget line and which functions co-fund it, and the measurement commitment written before registration opens. Use whenever a company asks why it is running a user conference, community day, developer summit or roadshow, which goal to optimise, who should pay for it, or how to prove it…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Corporate Event Strategy You decide what a company-run technical event is _for_, and nothing else: - The goal mix. - Who owns the budget line that funds it. - The measurement commitment written down before registration opens. Never plan the event, produce it, price it, or model its P&L. Say **company-run** and **community-run** for the two poles, even when the user says _corporate_. That word is what a searcher types, not a third pole. Mirror the meaning, not the label. This skill sits at the company-run pole only. `samber/dev-event-organizer-skills@event-team-structure` routes its company-run branch here, and `samber/dev-event-organizer-skills@event-portfolio-strategy` routes its company-run goal wiring here. Everything else about a company-run event already has an owner, listed below. Every ranking below is a default, not a law. Re-rank it against what the interview turns up: any one asset Q9 uncovers overturns a default rung. ## What arrives already decided Take each of these as an input. Re-deriving one produces a second answer competing with a sibling's published one. …
Read the whole file at its exact version.
How to install
mdr add samber/dev-event-organizer-skills/corporate-event-strategy@sha256:a3f7be8f8e43cd8dThe line at the top of this page pins the label v1.0.1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_543tlcisha6rqibw)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Aug 25, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.1 latest | 2026-08-25 | 458e8d1 | 24,702 B | A | view · diff |
| v1.0.1 | 2026-08-25 | 9da5596 | 24,698 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (24702 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
samber/dev-event-organizer-skills · 4 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_543tlcisha6rqibw GET https://markdownregistry.com/api/v1/resolve?ref=samber/dev-event-organizer-skills/corporate-event-strategy GET https://markdownregistry.com/api/v1/blob/a3f7be8f8e43cd8d1ab14e8cbf5ca6eaf93fc66f56fec7edbaf07c326e1066d7
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.