Emazing Group · AI Skills Program

Company Skills Distribution Tracker

Audited: 5 Slack channels Coverage: Mar 2026 to Jun 15, 2026 Generated: 2026-06-15
TL;DR
7
Shipped company-wide
9
In feedback, not yet shipped
~55
Built, never distributed
5
Channels audited
Shipped sent to the whole company In feedback shared with power users only Not distributed built but never packaged

1. Shipped to the company

Packaged and sent for everyone to install (file, zip, or command plus install instructions). These are the rows for your tracker spreadsheet.

SkillOwnerFirst sentChannelHow it was sharedWhat it does
Company CLAUDE.md baseline Anthony 2026-04-15 phase2, phase3 File plus merge prompt (drag in, paste, reopen) Shared company writing style, tool priorities, and hard rules
Book Retention Quiz Anthony 2026-04-20 phase2 Skill file attached, "give it to your Claude and modify" Weekly 5-question book quiz posted to Basecamp, AI grades answers
/insights Jose 2026-03-31 phase2 Command, run /insights Reviews your stocks and setup, rates 1 to 10, suggests skills to run
Claude Ready Notification Devin (shared by Brian) 2026-03-30 phase2 "Highly recommend everyone install" Notifies you when Claude needs input or is ready for review
Weekly Log Tessla (base), Anthony (official) 2026-04-21 base, 2026-06-12 official phase2, then main Drive SKILL.md, then weekly-log.zip plus full install steps Friday Wins / Stucks / Priorities drafted from Basecamp, Slack, Gmail; posts to Basecamp
claude-stats Jose 2026-05-22 (re-shared 2026-06-08) phase2, phase3, main claude-stats-skill.zip plus install steps and auto-schedule Pulls your local Claude usage, writes a row to the company leaderboard sheet every Friday noon
html-it (team) Anthony 2026-06-12 main html-it-team-skill.zip, ~4-min guided setup Say "html it" to turn any content into a shareable hosted HTML page

2. In feedback, not yet shipped

Shared inside #ai-power-users for feedback before a company rollout, but never confirmed sent out. This is the gap to close: finished work that the rest of the company cannot install yet.

Skill / toolOwnerDate sharedStatus
Skill Builder (emazing-skill-builder)Anthony2026-05-21Anthony said "then I'll get it updated and send this out to the company." Not confirmed shipped.
Skill Optimizer (emazing-skill-optimizer)Anthony2026-06-11"Can I get your feedback on the skill optimizer?" Still in feedback.
Claude BackupAnthony2026-04-15Tested with power users, planned for everyone on shared accounts. Not seen shipped.
EG Skills auto-update repo (ship once, update everywhere)Anthony2026-06-12The distribution mechanism itself, in review with Brian.
Granola Meeting ArchiveJose2026-04-17Setup guide shared to power users; later surfaced only as a personal win, not a company push.
Note-taking toolBrian2026-06-04Testing with Jose.
OKR 1x1 skillBrian2026-04-21v1 shared for feedback.
Email Skill (with customizable hooks)Jose2026-04-16In development, Brian feedback.
Claude Intel (tracks Claude / Anthropic updates)Jose2026-04-12Built and offered to share, no formal rollout.

3. Built, but never distributed

Roughly 55 individual automations were posted as "wins" across the channels and never packaged for anyone else to install. They run on one person's machine. The highest-reuse candidates:

  • Barcode Label Generator (/barcodes), EJ. Pulls qty and price, fetches barcodes, outputs a print-ready file.
  • Shopify Test Order Creator, requested by Jose; Jerome built one. Reusable across all three brands.
  • PO Vendor Email Automation, Arvhiane. Drafts vendor emails, pulls contacts, CCs buyers, tracks confirmations.
  • Morning Briefing (daily Basecamp triage page), Jose. Overdue and due-today across columns on one click-through page.
  • Daily Warehouse Location Sync (Salesforce to ShipStation), Jason. Posts before/after summary daily.
  • Best Deal Extractor and Updater (Amazon), Karlee. Cuts 2.5 to 3.5 hours per deal to ~10 minutes.
  • Create SKU automation, Maryanne. End-to-end SKU entry from the product team Slack drop.
This is the cross-pollination opportunity Jose flagged in the 2026-05-28 AI Power Users agenda: find skills shipped in one department that fit others, and recommend installs.

Data sources and caveats

  • Channels audited: #ai-claude-code-phase2 and #ai-claude-code-phase3 (both archived 2026-05-27), #EG-AI-Lab / main (active), #a-team-department-head-managers (a leadership channel that carries no skill distributions), and the feedback channel #ai-power-users.
  • "Who installed each skill" is not recorded in Slack. Two ways to get it: (a) follow up with each team member individually, or (b) extend the claude-stats skill, already running on most machines and already writing to the company sheet weekly, to also report each machine's installed-skills list. Recommend (b): automatic, no chasing.
  • Shipped vs built: a skill counts as "shipped" only when a file, zip, or command was posted with install instructions for everyone. A "win" describing a personal automation does not count, which is why the shipped list is short.
  • Coverage window: roughly March 2026 through June 15, 2026. Older history predates the skills program.