event-positioning SKILL.md skillA
event-positioning 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/event-positioning@v1.2.0Pins v1.2.0 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/event-positioning/SKILL.md- Versions recorded
- 3
- Latest version
- v1.2.0, committed Oct 12, 2026
- First version recorded
- Aug 27, 2026
- Size
- 31,228 bytes
- Repository stars
- 4
- License
- MIT
Define a technical event's positioning - what it stands for, against which alternatives, for which audience identity. Covers the governance axis (community-run, foundation, media-run, vendor-owned), competitive-alternative mapping, best-fit attendee and sponsor segments (and when a conference may serve several targets), the business-oriented layer sponsors buy, market-category strategy (head-to-head, subcategory, new category and its education tax), the positioning statement…
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
# Event Positioning You are a positioning strategist for technical events. You decide what the event stands for, against which named alternatives, and for which audience identity - the audience, promise, and brand at the strategic level. Positioning is context, not messaging: an attendee always evaluates the event relative to alternatives, and your job is to choose the frame (audience, category, alternatives) that makes the event's real strengths obvious before any tagline, CFP copy, or logo exists. That framing is borrowed from product positioning (April Dunford's method) rather than an event-industry standard - the named-event evidence in [references/positioning-evidence.md](references/positioning-evidence.md) is what grounds it here. …
Read the whole file at its exact version.
How to install
mdr add samber/dev-event-organizer-skills/event-positioning@sha256:6bafed2c40839bf4The line at the top of this page pins the label v1.2.0, 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_s4f563oeav5ydosb)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 27, 2026 and Oct 12, 2026, about one every 23 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.2.0 latest | 2026-10-12 | 7368d8a | 31,228 B | A | view · diff |
| v1.0.0 | 2026-08-27 | 1783686 | 22,014 B | A | view · diff |
| v1.0.0 | 2026-08-27 | e34399a | 22,011 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 (31228 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_s4f563oeav5ydosb GET https://markdownregistry.com/api/v1/resolve?ref=samber/dev-event-organizer-skills/event-positioning GET https://markdownregistry.com/api/v1/blob/6bafed2c40839bf454a4fdf7cfd0f57dd7da3e31f97bdcc1137e469b085864be
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.