JJ Englert
@JJEnglert • 36,860 subscribers
I help non-technical people do more with AI. Enablement Lead at @Tenex_labs (Best AI Consulting Firm) 😎 Join our community for top 1% AI builders 👇🏼
Videos
How to set up Claude Cowork so it actually works like an AI chief of staff (not just another chatbot): 1. Most people open Cowork, type a message, and get generic output. It's not a Claude problem. It's a setup problem. Cowork needs context before it can help you. Who you are. How you work. What you're building. Your team. Your priorities. Give it that, and every session feels like picking up a conversation with an executive assistant. 2. The setup has three layers: a) Global instructions (who you are, how you work, what Claude should never do). b) Connectors (Slack, Gmail, Google Calendar, Notion) c) And a folder structure on your computer that acts as Claude's long-term memory. That combination is what takes it from generic to personalized. 3. Skills are the real leverage. A skill is a markdown file that tells Claude exactly how to do one thing well. Write my newsletter. Coach me on a decision. Review a case study. Each skill lives in its own folder with context, examples, and a definition of what success looks like. 4. We built a CEO coach skill in the video below. Gave it business context, leadership style, company goals. Then tested it with a real decision: should we increase our newsletter from once to twice a week? It came back with trade-offs, second-order consequences, and risk assessment. 5. Then we built a multi-agent advisory board. Five subagents, each with a defined persona: a) the operator b) the skeptic c) the customer advocate d) the finance partner e) the legal/risk advisor. You feed it a decision. Each agent evaluates independently. The main agent synthesizes the feedback. It's like having a board meeting on demand. 6. Third skill: a thought leadership content pipeline. Topic scoring, idea capture, distribution cadence, tone calibration. All built from your actual expertise and audience. Designed so an executive can go from idea to published post without starting from scratch every time. 7. The workspace map is what ties it all together. It's a top-level file that shows Claude how to navigate your entire setup. Which folders exist, what skills live where, how to invoke them. Without it, Claude has to search for everything. With it, Claude goes straight to what it needs. 8. Everything you build is portable. The folder structure works in Cowork, Claude Code, and Codex. Push it to a private GitHub repo and you can access it from your phone through Claude Code, or use Claude Dispatch. 9. The pattern is repeatable. Pick a task you do often. Create a folder. Build a skill. Add examples of what success looks like, and what a bad output looks like. Test it. Workshop it. Move on to the next one. Each skill is like onboarding a new employee who never forgets and never needs to be re-trained. The people who invest in this setup now are the ones who will have a 10x advantage when these tools get even better. And they're getting better fast. I sat down with Alex Lieberman on Human In The Loop and we built all three of these live from scratch. Full breakdown in the video below.. I tried to explain this as clear as possible for my non-developer crowd. Send it to someone who should be using Cowork but isn't yet. Or bookmark it to level up when you're ready. Watch 👇🏼
JJ Englert568,980 görüntüleme • 4 ay önce
I've used Claude Code to build 20+ projects in the last 6 months. Thousands of new users across them. And I've never written a single line of code. I just dropped a 24-min video with my top 10 tips for non-developers — the exact playbook I use every day to run multiple AI agents that handle work that used to take me a full week. This is the best beginner guide to learning and building with Claude Code out right now. Every tutorial I found assumes you're a developer. This one doesn't. I cover everything from first install to running multi-agent workflows — with live demos and real examples for every single tip. How I set up new projects, how I got Claude to match my writing style, how I automate repeatable workflows with one command, and how I run multiple agents working on different tasks at the same time. I also built a full resource repo to go alongside the video — curated video tutorials, the best skill libraries, plugin directories, MCP server guides, written docs, community links, and a starter template you can copy-paste into your first project today. Comment "GUIDE" and I'll send you the full guide with everything you need to learn Claude Code! (make sure we're connected so I can DM you)
JJ Englert419,320 görüntüleme • 5 ay önce
Finally. Claude just merged Chat and Cowork into a single Home tab, and this is the one I've been wanting since Cowork launched. Before this, you had to pick a lane before you even opened a conversation: Chat if you just wanted to talk, Cowork if you needed Claude to read your files and get to work. Now it's one tab, and you just start typing. That's not even the best part of this update. You can now turn any conversation into a Skill, or schedule it to run on its own, every Monday at 9am, no touching it again. If you're on a Team account, it goes further: - Projects are now shared org-wide now. Including Cowork projects, which used to be stuck on one person's laptop. Client files, proposals, timelines, estimates, all in one shared workspace. Skills, connectors, and plugins share across the org too. Artifacts got real sharing. Import from a link, share internally (used to be local-only), grab a share link, pop it out into its own window. Between the Cowork merge + all of the app updates, they pushed a lot of heat with this release. Watch this 9 minute video to get caught up on everything! ↓
JJ Englert49,500 görüntüleme • 23 gün önce
I built the ultimate GTM Engineer AI Toolkit that handles prospect research, outreach writing, meeting prep, and more in minutes. This is a beginner-friendly walkthrough that shows you exactly how to set it up, use it at work, and personalize it to your business. It can: - Research real prospects and companies - Score accounts against your ICP - Write personalized cold outreach sequences - Generate meeting prep briefs before calls - Help you build a repeatable prospecting pipeline - All using a free toolkit + Claude Code / Codex. This is for SDRs, founders, marketers, and GTM operators who want to use AI to do more at work without buying another expensive tool. I break down the full workflow step by step in the video. 👇 Comment "GTM GUIDE" and I’ll send you the full toolkit. (make sure you're following me so I can DM you)
JJ Englert169,834 görüntüleme • 5 ay önce
Once you learn these three things, you can build nearly anything yourself. Skills, chains, and plugins. Learn them once and you can automate a real part of your week yourself. Here's the system: A skill is a standard operating procedure. It's one long, reusable prompt that does one thing well, like writing a newsletter, setting up a PPC campaign, triaging your inbox, or drafting a note to the board. You write it once and reuse it forever. The trick is to feed it your real work. For my writing skill, I gave Claude posts I admire and my own exported analytics with the winners marked, so it could see the patterns. Show it what good looks like and it nails your voice. Skip that step and it guesses. A chain connects skills into an automation. One skill's output feeds the next, in order. A copywriting skill writes the messaging, then hands it to a PPC-setup skill that builds the campaign. That's an automation, and you built it without writing code. A plugin is the harness that holds it all. It bundles your skills and chains into one thing you share with your team. Instead of sending 15 separate prompts around, you send one plugin, and it knows when to use each skill on its own. Skill, chain, plugin. It's one step up the ladder, and once you're up there it's easy. Now the worked example. I call it the Daily Driver. It's five skills chained together: email triage, a writer, Slack triage, a thinking partner, and a setup skill that connects my tools and personalizes everything. I chained them into one morning brief and scheduled it to run at 9am and message me the list. Two things made the biggest difference. Give it memory. I made plain docs for About Me, my Brand Voice, and my working preferences. I had Claude interview me and saved each answer as a file. Now every output sounds like me and knows my projects and my team. Connect your tools. The plugin reads my inbox, Slack, and calendar through MCP connectors for Gmail, Slack, and Google Calendar. That's what turns "summarize my morning" into a real brief instead of an empty wish. This is the highest-ROI thing an operator can set up this week. I run my YouTube channel, podcast, community, and newsletter on plugins I built myself, all on the $100 Max plan with no engineer in sight. I made a full walkthrough that shows the whole build start to finish. Want the Daily Driver plugin to start from? Comment PLUGIN below and I'll send it to you. #AI #automation #ClaudeCode
JJ Englert53,898 görüntüleme • 1 ay önce
Motion graphics used to take me an hour per scene (or more) Now I'm creating them in 3-5 minutes — without After Effects, without Premiere, without writing a single line of code. I'm a former LA filmmaker (still PGA). My entire video stack is now 3 tools: Claude Code + HyperFrames (from HeyGen) + Descript Here's how the workflow runs: 1. Drop my brand style guide into a folder (colors, fonts, components Claude reuses forever) 2. Paste a line from my Descript transcript into Claude Code: "Create a scene for this part of the video" 3. Claude Code reads my brand, generates the HyperFrames scene, renders it to MP4 4. Drag the MP4 into Descript, drop it on the matching line of the transcript 5. Done. 3-5 minutes per scene. The unlock is the brand style guide. Once Claude has your colors, fonts, and reusable components, every scene inherits your look automatically. Bonus — you can take a Claude Design export (.zip), hand it to Claude Code, and it'll convert the HTML into a HyperFrames video you can render and edit. I built a GitHub repo with all the skills pre-loaded. Non-developers can clone it, open Claude Code, and be rendering scenes in under 10 minutes. Full walkthrough (20 min video) below Repo (skills + brand template + music-from-transcript plugin): Bookmark this if you make videos. The brand-style-guide pattern alone will save you hours every week. If you're a creator or operator using AI for content — share this with someone who's still living in After Effects.
JJ Englert102,785 görüntüleme • 3 ay önce
Motion graphics were always the hardest part of making videos for me. Hours in After Effects for 10 seconds of movement. Now I can do them 10x faster without touching a timeline or writing a single line of code. Remotion released a skill that lets Claude Code create videos programmatically. I spent 5 hours building with it so I could show you exactly how it works. What's in the guide: - Installing the Remotion skill (takes 2 minutes) - Creating your first video scene by scene - Auto-editing long videos into clips - Adding animated captions and subtitles - Reframing for TikTok/Reels/Shorts - Stacking multiple skills into a mini production studio This is for content creators, marketers and GTM engineers who want to create more videos, better and faster, without learning video editing software or code. I recorded the full walkthrough. Every step. 👇 Comment "GUIDE" and I'll DM you the repo with all of the skills installed + getting started guide. (Make sure we're connected so I can DM you)
JJ Englert143,162 görüntüleme • 5 ay önce
I built an entire content team in 21 minutes. It writes LinkedIn posts, YouTube scripts, Newsletters, and Tweets. All in my voice. Content used to be the bottleneck. Writing for multiple platforms meant either spending hours on it or hiring someone who never quite sounded like me. I spent weeks refining this system so I could show you exactly how to set it up. What's in the guide: - Setting up your personal AI writer from scratch - The folder structure that makes AI writing actually work - Using successful examples to train your AI's voice - Building and refining custom writing skills - Advanced techniques for scaling across platforms This is for creators, founders, and marketers who want to produce more content, faster, without losing their voice or hiring a team. I recorded the full walkthrough. Every step. Live. Comment "WRITER" and I'll DM you the free GitHub repo with the complete folder structure and skills. (Make sure we're connected so I can DM you)
JJ Englert76,796 görüntüleme • 5 ay önce
Yesterday I dropped a guide on setting up Claude Cowork that blew up. One question kept coming up: how do I use all of this on my phone? Cowork doesn't have a mobile app yet. But there's a simple workaround. Push your Cowork workspace to a private GitHub repo. Open Claude Code on the Anthropic mobile app. Connect the repo. Done. Now every skill file, brain file, and writing style you built for Cowork is accessible on the go. No coding. 5 minutes to set up. Two things to know: This syncs your files and skills, not your connectors (Slack, Gmail, etc.) When you update files locally, push to GitHub to keep mobile current Full walkthrough below. Original Cowork setup guide (with the prompt to build your own system) is reposted below as well. Enjoy!!
JJ Englert55,555 görüntüleme • 4 ay önce
We've partnered with Paul Jankura to host an official Claude Code workshop in NYC and I genuinely cannot stop thinking about how good this is going to be. We've been getting an incredible amount of requests from our enterprise clients for Claude Code training, and we're thrilled to finally be doing something official with Anthropic to meet that demand. This workshop is being run by an Anthropic engineer, one of our senior AI Strategists at tenex, and myself — and we're going all in on teaching you how to orchestrate agents with Claude Code. Getting set up, skills, hooks, plugins, and more. You'll leave having actually built things, not just watched a demo. You'll see the magic of Claude firsthand! We're also pulling back the curtain on how our engineers at Tenex are using Claude Code inside Fortune 500 companies right now to accelerate impact — and we'll take live questions on what implementing Claude Code at scale actually looks like. World-class venue, the right people in the room, and a real hands-on experience your team can bring back and put to work immediately. Free event. 30 spots total. We're accepting up to 2 people per org — usually a senior decision maker and a technical partner. April 10th, New York City. If you're serious about bringing Claude Code into your org, this is the room to be in. Apply here:
JJ Englert41,213 görüntüleme • 4 ay önce
Anthropic released Claude Design TODAY and it's now accessible at I spent the last hour giving it a first look, and shared my thoughts and results in the video below. This is a BIG drop. This is a new design surface from Anthropic, and it changes what "AI design" means. Short version: Claude can now design. Not "describe a design." Not "generate an image of a design." Actual production work — prototypes, wireframes, high-fidelity mocks, slide decks, landing pages — editable, on-brand, and ready to hand off. Here's what stood out on first look: → Real design surfaces Prototypes, wireframes, hi-fi, and slide decks — each with templates and proper structure, not just pretty screenshots. → Comment-based edits Leave a comment on any element and Claude revises it. This is the Figma-style review loop, with the designer replaced by a model that works at 3am. → Brand design systems You can feed it your system — colors, type, components — and it actually respects it. On-brand output, not generic AI slop. → Export anywhere PDF, PowerPoint, Canva, standalone HTML. Plus a built-in handoff straight to Claude Code for engineers to implement. → Import from real tools Figma, GitHub, and captured web elements come in as inputs. Your existing work is the starting line, not the discard pile. → Collaboration Share links for view / comment / edit — the exact tier system teams already expect. What I tested on Opus 4.7: • A 5-slide deck generated from a single screenshot. Claude asked clarifying questions BEFORE generating and shipped speaker notes by default. • A landing page build. Solid first pass, real components, real layout logic. • Multiple chats running concurrently. You can parallelize design work across threads like a small team. Why this matters: PMs, founders, marketers, and non-engineers can now create designs that engineers can actually ship with production-ready output and a claude code handoff built in. The gap between "I have an idea" and "here's a working prototype with my brand applied" just collapsed to minutes. Full walkthrough, live demos, exports, and honest takes on where it breaks below. P.S. • This is an Anthropic Labs product — NOT GA yet. • Claude Design is currently webapp only (no API), and does not yet support the Analytics API, Compliance API, or cost/usage reporting. • Availability: – Default ON for Pro / Max / Team – Default OFF for Enterprise Enterprise admins can toggle it on via RBAC in console (comes with a ~$20/user initial credit).
JJ Englert32,445 görüntüleme • 3 ay önce
I couldn't believe the results of this benchmarking test. I blind-tested 6 frontier models — Sonnet 5, Opus 4.8, Fable 5, GPT 5.5, GLM 5.2, and Kimi 2.5 — on knowledge work, not engineering. Writing. Analysis. Design. Vibe coding. Subagent simulations. The stuff we actually do all day. Same prompts, each model running its own subagent, every output graded blind before the labels were revealed. The results: → GLM 5.2 (the dirt-cheap open-source model from China) took first → Sonnet 5 took second, beating Fable 5 for knowledge work → Opus 4.8 got whooped Then I had Composer 2.5 judge every output independently — and it picked Fable 5 almost across the board. My blind picks and the AI judge completely disagreed. Full breakdown, method, and prompts in the video below. Which model are you running as your daily driver right now?
JJ Englert10,737 görüntüleme • 1 ay önce
One of my favorite upgrades to Claude Cowork right now: Projects Here's the problem it solves: By default, every new thread starts blank Claude has no memory of what you were working on, what other threads figured out, or what your instructions were So you'd re-explain yourself at the start of every session Or your agents would overlap, contradict each other, or miss context that another thread already had If you've been following my Cowork setup guides, you've already solved part of this — local files and a CLAUDE.md get you most of the way there Projects takes it the rest of the way Shared memory across every thread in the project Permanent instructions that apply everywhere — set once, always on Scheduled tasks that prep your work before you open the app One project HQ to launch every agent from The day-one prompt I paste into every new project: "I just created this project. Read every file in the folder. Then summarize what you know about this workspace — what's here, what I probably use it for, and what instructions you'll follow. If anything is unclear, ask me some questions." Run that once and Claude builds its own understanding of your project workspace from scratch Full video with my live build, including my 4 tips for getting Projects right, and where projects still lack. Send to someone whose ready to Do More with AI, or bookmark to implement this weekend!
JJ Englert29,809 görüntüleme • 3 ay önce
Skills are the quickest way to 10x the quality and consistency of what you get from Claude Code. And you don't need to be a developer to use them. Anthropic just published how they use hundreds of skills internally every day. Most skill tutorials are made for developers — if you're in marketing, sales, content ops, or GTM, you probably watched those and moved on. But skills are just as important for non-developers. A skill is just a reusable prompt with clear instructions for a specific task. Instead of prompting Claude the same way over and over, you build it once and invoke it every time. I have a skill for writing on LinkedIn. A different one for YouTube outlines. Another for X. Each platform has different rules, different voice, different structure — so each one gets its own skill. If you're doing something repeatedly, it's time to make a skill. The biggest mistake most people make: building skills as a single .md file. A single file dumps everything into context whether Claude needs it or not. Wastes tokens. Gets worse results. Skills should be folders. Here's the structure that works: skill.md — the orchestrator. Tells Claude which files to read and when. It doesn't contain rules itself — it's the playbook. instructions/ — separate files for voice, structure, scope. Claude only loads the one it needs for the current step. examples/ — good AND bad. Good examples show what success looks like. Bad examples show patterns to avoid — AI writing tells, weak hooks, generic CTAs. Most people skip bad examples. Don't. eval/ — a checklist that scores every output before you see it. "Does it have a clear hook?" "Is it free of AI buzzwords?" Pass or fail on each item. templates/ — output formatting so you get consistent structure every time. The three types of skills that matter most for non-developers: 1. Business automation. Writing a newsletter. Checking reports and drafting follow-ups. Running programmatic ad campaigns. Any workflow you repeat — build a skill for it. 2. Content templates. Landing page copy, meta ads, email sequences, SEO briefs. Each one has specific requirements. Each one gets its own skill. 3. Thinking partners. This is the one people miss. Skills don't have to produce output. They can help you think — an advisory board that reviews your work from your ICP's perspective, a coach that pressure-tests your strategy, an ideation partner that researches competitors before suggesting your next move. If you already have skills as .md files, here's the exact prompt to restructure them in the Anthropic approved format: "I want to restructure my Claude Code skill file. Right now my skill is a single .md file and I want to break it into a folder system following Anthropic's best practices. Read my current skill file, then restructure it into a folder with: a skill.md orchestrator, an instructions/ folder with separate files for each concern (voice, structure, scope), an examples/ folder with good and bad examples, an eval/ folder with a quality checklist, and a templates/ folder for output formatting. Keep all my existing rules and intent — just reorganize them into the modular structure." Paste that into Claude Code pointed at the folder where your skill lives. It handles the rest. A few caveats: 1. Don't add too many skills. Every skill adds context Claude has to process. 50 skills loaded means everything slows down. Start with 3-5 covering your most repeated workflows. 2. Vet skills before downloading. If you grab a skill from the internet, read what's inside first. Skills can include shell commands and scripts. Check what you're running. 3. Share what works. Build a skill that performs well, put it in a shared GitHub repo. Your marketing org gets shared skills for copywriting, SEO, ad copy — new hires invoke the skill instead of learning every playbook from scratch. Onboarding time drops dramatically. 4. Keep your skills updated. When you see output you love, add it as a good example. When you see a pattern you hate, add it as a bad example. The skill gets sharper every time. I made a full video walking through all of this — including a live build of two skills from scratch (no terminal, no code), the exact prompt I use to restructure old skills, and 5 pro tips from Anthropic's internal playbook. Share this with your non-developer friends that want to do more with AI; or bookmark it to come back to at a later time.
JJ Englert29,322 görüntüleme • 4 ay önce
The number one question I get in the Claude Code / Cowork Community: "how do I share my Cowork skills with my team?" Here's the problem. You build a great skill. You zip it up. You drop it in Slack. Your teammate downloads it, uploads it, and maybe it works. Maybe they upload it wrong. Maybe you update the skill next week and nobody gets the new version. You're now maintaining skills through chat messages and hoping for the best. That doesn't scale. I just put out a video breaking down the three methods I've tested for sharing skills and plugins across a team. From dead simple to fully synced. Method 1: Shared drive (Google Drive, SharePoint, etc). You put your skill files in a shared folder. Teammates download and upload them into Cowork. It works, but updates are manual and there's no version control. Method 2: Built-in sharing on Team and Enterprise plans. You can share any skill directly with a colleague or publish it to your org directory. When you update the skill, everyone gets the update automatically. This is the easiest path if you're on a paid plan. The catch: there's no approval workflow for org-wide sharing, so set a clear owner. Method 3: GitHub repo. This is what I use. Your entire Cowork workspace -- skills, plugins, claude.md, folder structure, project files -- lives in a private repo. Teammates clone it. When you push an update, they pull it. Everyone stays in sync. You get version history, access control, and a single source of truth. The GitHub method sounds technical, but it's really just two steps: clone the repo, point Cowork at the folder. I walk through the whole thing in the video, including how to use .gitignore to keep personal files (like your morning briefing) out of the shared repo. This works for Cowork, Claude Code, and Open Codex. The infrastructure is the same. Full video linked below. If you've found a different approach that works for your team, I want to hear about it. Comment or reply and let's figure out the best practices together.
JJ Englert16,176 görüntüleme • 3 ay önce
Daha fazla içerik yok.