https://claude-advanced.manuelqg.people.aws.dev/en/02-sesion-1/index.html Session 1 · Skills and Plugins: standardize your team Info ⏱ Duration: ~2 h (120 min core + optional block) · 🎯 Goal: turn how your team works into reusable skills and package them with plugins. · 📅 Week 1 of 4. Note Cohort assumptions: we assume a Team/Enterprise plan. Blocks marked 🎥 are an instructor demo (the feature isn’t in your plan or is Mac-only). Confirm your plan in Settings before you start. Week 1 of 4. In the basic track you rescued Elektra Rewards working with Cowork yourself. Now the CEO asks for something bigger: that your whole directorate works just as well, not only you. The answer is skills —folders of instructions Claude loads when it needs them— and the plugins that distribute them to your team. Hugo en-US https://claude-advanced.manuelqg.people.aws.dev/en/02-sesion-1/01-anatomia-de-un-skill/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://claude-advanced.manuelqg.people.aws.dev/en/02-sesion-1/01-anatomia-de-un-skill/index.html Info ⏱ Duration: ~25 min · 🎯 Goal: understand what a skill is, how a SKILL.md is built, and why the description decides when Claude invokes it. A skill is, verbatim, a “folder of instructions, scripts, and resources that Claude loads dynamically” to improve at specialized tasks. They work everywhere —regular chats, Projects, and Cowork— and activate automatically when the work calls for them. When a task needs several areas of expertise, Claude combines multiple skills on its own. https://claude-advanced.manuelqg.people.aws.dev/en/02-sesion-1/02-crea-tu-skill-conversando/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://claude-advanced.manuelqg.people.aws.dev/en/02-sesion-1/02-crea-tu-skill-conversando/index.html Info ⏱ Duration: ~35 min · 🎯 Goal: create an “Elektra QBR” skill by talking to Claude, using the templates from the zip, and confirm it invokes on its own. Note 30-second pre-flight: go to Settings > Capabilities and confirm “Code execution and file creation” is on —without it, Claude can’t create or package your skill. On Enterprise the Owner must enable it org-wide; if it shows off in your account and you can’t change it, follow this block as a 🎥 instructor demo. You don’t need to write YAML by hand. The recommended path for executive profiles is to create the skill conversationally: you explain your process to Claude, upload your templates, and it builds the SKILL.md, organizes the materials, and packages everything for you. https://claude-advanced.manuelqg.people.aws.dev/en/02-sesion-1/03-graba-un-skill/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://claude-advanced.manuelqg.people.aws.dev/en/02-sesion-1/03-graba-un-skill/index.html Note 🎥 Instructor demo. For the assumed cohort (Team/Enterprise), Record a skill doesn’t apply: the feature is limited to Cowork on Mac with Pro/Max/Team plans and doesn’t exist on Enterprise. Follow this block as a demonstration; you don’t need to run it on your team. Info ⏱ Duration: ~20 min · 🎯 Goal: learn Record a skill —capturing a flow from your screen— and its permission and privacy rules. Sometimes the easiest way to teach Claude a process is to show it. With Record a skill you record your screen doing the task and Claude proposes a skill from what it saw. https://claude-advanced.manuelqg.people.aws.dev/en/02-sesion-1/04-plugins/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://claude-advanced.manuelqg.people.aws.dev/en/02-sesion-1/04-plugins/index.html Info ⏱ Duration: ~25 min · 🎯 Goal: install a plugin, understand what it bundles, where each piece runs, and how it’s distributed org-wide. A skill standardizes one task. A plugin packages several: verbatim, each plugin bundles skills, connectors, and sub-agents into a single package. It’s the unit you use to bring your way of working to your whole team. Step 1 — Understand where each piece runs Not everything works on every surface: https://claude-advanced.manuelqg.people.aws.dev/en/02-sesion-1/05-cierre-sesion-1/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://claude-advanced.manuelqg.people.aws.dev/en/02-sesion-1/05-cierre-sesion-1/index.html Info ⏱ Duration: ~15 min · 🎯 Goal: consolidate what you learned, validate the session checkpoint, and prepare for Week 2. Week 1 of 4 complete. Today you turned your way of working into a reusable asset: you created an “Elektra QBR” skill by talking, learned Record a skill, and installed your first plugin. The work no longer depends on you being present to get it right; the knowledge lives in the skill. https://claude-advanced.manuelqg.people.aws.dev/en/02-sesion-1/06-si-hay-tiempo/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://claude-advanced.manuelqg.people.aws.dev/en/02-sesion-1/06-si-hay-tiempo/index.html Note ⏱ Optional block (~15 min) · 🎯 Goal: adopt two security habits before your team shares skills at scale. A skill is code and resources that Claude runs on your behalf. That makes it powerful —and a risk vector if you handle it carelessly. Two rules cover most of the risk. Rule 1 — Never put secrets inside a skill Don’t embed API keys, passwords, or tokens in the SKILL.md, in the scripts, or in the resources. A skill is shared and packaged into a ZIP: any secret you write inside travels with it to your whole team (and anyone who receives the file).