Session Overview
Campus VIP working session held Friday, February 13, 2026 (85 minutes). Attendees: James (host), Barry, Sabrina, Kelly, and group members. The session focused on the Skills Library ecosystem — installation, live skill creation, branding customization — plus community space admin, micro-credentialing as a course structure, and treating Claude skills as "digital employees" with defined roles.
Date: Friday, February 13, 2026
Duration: 85 minutes
Vimeo: https://vimeo.com/1164767898/39b27b2a56
Key Concepts
Skills as Digital Employees
Each Claude skill has a role, a set of tools, and a defined output. Thinking of skills as employees (rather than features or prompts) changes how you build them: you define what they’re responsible for, what they have access to, and what "done" looks like. A skill for creating tutorial posts from transcripts is effectively a "Tutorial Editor" on your team.
Live Skill Creation (No Coding)
You don’t need to know how to code to create a new skill. Describe your task to Claude in plain language → ask it to "write this as a reusable skill" → it generates the skill markdown → you upload it as a .plugin file → done. This was demonstrated live with a custom website-setup helper skill built during the session.
Micro-Credentialing
Short-form certifications on a single skill or topic. Lower barrier to entry than a full course. Typically 4–6 lessons plus a simple assessment. Issues a completion badge. Converts well because learners can see the finish line. Good for building a progression from free → micro-credential → full program.
Client Data Privacy in Claude
Claude’s sandboxed Project feature keeps data isolated. Client-specific data (contracts, strategies, proprietary info) stays in its own project and doesn’t cross-contaminate other sessions. For most coaching/consulting use cases, this is sufficient. Truly sensitive regulated data should stay off AI entirely.
Community Space Visibility Types
- Public — Anyone can see and join
- Private — Visible to members, requires enrollment or approval to access content
- Secret — Completely hidden from the directory; only accessible by invitation
Step-by-Step Workflows
Installing a Skill from the Skills Library
- Go to trainingsites.io/skills
- Find the skill you want and click Download (.plugin file)
- Open Claude Cowork (desktop app)
- Settings → Skills → Upload
- Select the .plugin file
- The skill appears in your skill list
- Test with a sample task prompt
Creating a Custom Skill (No Code)
- Open Claude (Cowork or desktop)
- Describe the task: "I want to automate [specific task]. Here’s what it should do: [steps]"
- Ask: "Write this as a reusable Claude skill in markdown format"
- Review the generated skill
- Save as a .md file, rename to .plugin
- Upload to Cowork → Settings → Skills
- Test and refine as needed
Tutorial Creation Pipeline
- Provide YouTube URL to Claude
- Claude extracts transcript via YouTube MCP
- Generates structured tutorial (title, summary, steps, tools, timestamps)
- Creates WordPress draft via AI Engine MCP
- Drafts email announcement in FluentCRM
- Posts discussion to FluentCommunity space
- All from one Cowork task command
Micro-Credentialing Build
- Choose one narrow, specific skill (not a full subject)
- Create 4–6 short lessons (15–20 min each)
- Add a short quiz or assignment at the end
- Issue a completion badge or certificate
- Price lower than your full program ($47–97 range)
- Use as a stepping stone to full enrollment
Tools Mentioned
| Tool | Purpose |
|---|---|
| TrainingSites Skills Library | Free skill downloads — trainingsites.io/skills |
| Claude Cowork | Skill execution and workflow orchestration |
| Gamma AI | Presentation generation from documents; MCP connector available |
| Canva + MCP | Automated design creation using brand templates |
| Universal GPT Clipboard | System for storing/reusing high-performing prompts |
| FluentCommunity | Space visibility admin (public/private/secret) |
| Claude Projects | Sandboxed client-specific data environments |
Q&A Highlights
Q: How do I add my branding to skill outputs?
Two approaches: (1) Add brand guidelines (colors, fonts, tone, company name) directly into the skill’s system prompt. (2) Create a "Brand Guidelines" skill and chain it to any output-producing workflow in Cowork so every deliverable auto-applies your branding.
Q: Is it safe to put client data into Claude?
Claude’s sandboxed Projects keep data isolated per project. For most coaching and consulting use cases, this is sufficient. The key rule: use a dedicated project for each client, and don’t mix proprietary client data across sessions.
Q: What’s the difference between a skill and a plugin?
A skill = one task. A plugin (workflow) = multiple skills chained together with connectors that pass data between steps. Build skills first, then chain them into workflows.
Q: Can I build a skill without knowing how to code?
Yes — describe what you want in plain English and ask Claude to write it as a skill. It outputs the markdown. You upload it. No coding needed at any step.
Teachable Moments
Naming matters. Calling Claude features "digital employees" instead of "skills" or "prompts" changes how people think about them — and how they build them. The vocabulary you use shapes the strategy.
Micro-credentials solve the "too big" problem. Many creators lose sales because prospects are intimidated by a full course. A micro-credential on one specific outcome gives them a win they can see clearly — and a natural path to your larger program.
Live skill creation is the best demo. Watching a skill get built from scratch in 10 minutes removes the mystique. Members consistently report that seeing it done live is what convinced them to try it themselves.