正在加载视频...

视频加载失败

加载此视频时出现问题。这可能是由于临时网络问题，或视频可能不可用。

Most Obsidian vaults fail at the same place: capture works, return never happens. You save ideas, highlights, numbers, hooks, screenshots. Then 6 months later the vault has 400 notes and no idea what to write next. Build the return path instead: 1. Use 5 folders 00-INBOX 01-CAPTURES 02-CONNECTIONS 03-BRIEFS... 04-PUBLISHED 2. Sort captures by type, not topic > observations > reactions > patterns > questions > numbers Topic folders hide useful collisions. Type folders help Claude connect "attention psychology" to "X hook performance." 3. Put Claude Code files where Claude actually reads them > ./CLAUDE.md or ./.claude/CLAUDE.md > .claude/skills/process-inbox/SKILL.md > .claude/skills/weekly-connections/SKILL.md > .claude/skills/generate-brief/SKILL.md > .claude/skills/write-content/SKILL.md 4. Log performance in every published post > impressions > bookmarks > hook_used > top_comment > what_worked Build the path that turns saved notes into briefs, posts, and performance data: capture -> connection -> brief -> post -> result -> next briefshow more

Alpha Batcher

51,230 subscribers

50,997 次观看 • 6 个月前 •via X (Twitter)

科学技术教育

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Andrej Karpathy quietly shipped the best second brain idea in years not an app. a pattern. let an llm maintain a wiki of your notes. you dump sources, it reads them, links them, files them. knowledge compounds like interest. someone built it into a free claude code plugin. setup is two commands: claude plugin marketplace add AgriciDaniel/claude-obsidian claude plugin install claude-obsidian@agricidaniel-claude-obsidian then open obsidian, open claude code in the same folder, type /wiki. that's it. your notes are now queryable by claude and they get richer every time you read something. bookmark this. best thing you'll build this weekend.

Andrej Karpathy quietly shipped the best second brain idea in years not an app. a pattern. let an llm maintain a wiki of your notes. you dump sources, it reads them, links them, files them. knowledge compounds like interest. someone built it into a free claude code plugin. setup is two commands: claude plugin marketplace add AgriciDaniel/claude-obsidian claude plugin install claude-obsidian@agricidaniel-claude-obsidian then open obsidian, open claude code in the same folder, type /wiki. that's it. your notes are now queryable by claude and they get richer every time you read something. bookmark this. best thing you'll build this weekend.

Avid

339,848 次观看 • 5 个月前

New: Use skills with local agents! Keep your skills in Notion as your source of truth, then download them to Claude Code, Codex, Cursor, Gemini, or Grok. You’ll get a SKILL.md plus any approved files. So you can use your skills wherever you work.

New: Use skills with local agents! Keep your skills in Notion as your source of truth, then download them to Claude Code, Codex, Cursor, Gemini, or Grok. You’ll get a SKILL.md plus any approved files. So you can use your skills wherever you work.

Notion

146,855 次观看 • 2 个月前

ABSOLUTE F*CKING GOLDMINE AND EVERY ONE FREE Claude Code Pro costs $20 a month. antigravity alone lists 2,750+ installable skills in its catalog, VoltAgent holds 161+ ready subagents across 10 categories, and none charges you extra 10 GitHub repos that staff your Claude Code session: 01 anthropics/skills → Anthropic's own SKILL.md reference folders for Claude Code. shows the canonical format so every custom skill you write loads on the first try 02 awesome-claude-code-subagents → VoltAgent's collection of 161+ ready subagents across 10 categories. copy a reviewer, debugger or architect instead of writing the role prompt yourself 03 claude-skills → ships 398 production-ready skills and plugins for 13 AI coding tools. one install replaces hunting across dozens of repos 04 claude-code-templates → ready configs for agents, commands, hooks and MCP servers. starts a new project with a working .claude folder instead of a blank directory 05 awesome-claude-code → curated index of skills, hooks, plugins and developer tooling. finds the vetted piece without scrolling through GitHub search results 06 ui-ux-pro-max-skill → design intelligence skill for building professional layouts across platforms. gets sane palettes and spacing without a separate designer pass on every screen 07 planning-with-files → persistent file-based plans that survive long sessions and context resets. stops the agent from losing the map when memory clears mid-task 08 marketingskills → marketing-focused skills covering copy, SEO and launch checklists. fills the prompt gap when a codebase agent has to write a landing page 09 vercel-labs/skills → the CLI for the open agent skills ecosystem. one command pulls any published skill into Claude Code, no manual file copying 10 antigravity-awesome-skills → catalogs 2,750+ installable SKILL.md playbooks with a local search engine. searches and previews a plan before the agent touches your codebase pick one recurring task that drains your time every week. install the skill for it, run it once and read what the agent actually did before you schedule the next one source → vet → install → staff → ship every skill runs with your plan's usage and permissions, and community packs are not audited by Anthropic. read a SKILL.md before installing save this and check the full breakdown below ↓

ABSOLUTE F*CKING GOLDMINE AND EVERY ONE FREE Claude Code Pro costs $20 a month. antigravity alone lists 2,750+ installable skills in its catalog, VoltAgent holds 161+ ready subagents across 10 categories, and none charges you extra 10 GitHub repos that staff your Claude Code session: 01 anthropics/skills → Anthropic's own SKILL.md reference folders for Claude Code. shows the canonical format so every custom skill you write loads on the first try 02 awesome-claude-code-subagents → VoltAgent's collection of 161+ ready subagents across 10 categories. copy a reviewer, debugger or architect instead of writing the role prompt yourself 03 claude-skills → ships 398 production-ready skills and plugins for 13 AI coding tools. one install replaces hunting across dozens of repos 04 claude-code-templates → ready configs for agents, commands, hooks and MCP servers. starts a new project with a working .claude folder instead of a blank directory 05 awesome-claude-code → curated index of skills, hooks, plugins and developer tooling. finds the vetted piece without scrolling through GitHub search results 06 ui-ux-pro-max-skill → design intelligence skill for building professional layouts across platforms. gets sane palettes and spacing without a separate designer pass on every screen 07 planning-with-files → persistent file-based plans that survive long sessions and context resets. stops the agent from losing the map when memory clears mid-task 08 marketingskills → marketing-focused skills covering copy, SEO and launch checklists. fills the prompt gap when a codebase agent has to write a landing page 09 vercel-labs/skills → the CLI for the open agent skills ecosystem. one command pulls any published skill into Claude Code, no manual file copying 10 antigravity-awesome-skills → catalogs 2,750+ installable SKILL.md playbooks with a local search engine. searches and previews a plan before the agent touches your codebase pick one recurring task that drains your time every week. install the skill for it, run it once and read what the agent actually did before you schedule the next one source → vet → install → staff → ship every skill runs with your plan's usage and permissions, and community packs are not audited by Anthropic. read a SKILL.md before installing save this and check the full breakdown below ↓

Ridark

15,483 次观看 • 15 天前

No Netflix this Sunday, instead Spend 50 minutes on this Claude tutorial (You’ll learn how to build Claude Skills from scratch) Chapters: 0:00 - Full Claude Skills Guide 0:41 - What are Claude Skills 10:16 - Using Claude Cowork 11:12 - What are Connectors 12:52 - Claude’s Skill Creator 14:07 - The First Claude Skill Idea 14:55 - Installing DBS Framework 15:51 - Creating a Skill using Claude 20:00 - Testing the Skills on Claude 22:10 - Reviewing Skill Evaluations 23:12 - First Claude Skill Complete 24:00 - Using the Claude Skill 25:35 - Complex Claude Skill Idea 27:00 - Enabling Gamma 27:35 - Creating the Complex Claude Skill 29:14 - Answering Claude’s Questions 30:59 - Adding Brand Guide to References 32:05 - Reviewing Skill Draft 32:46 - Testing New Claude Skill 35:40 - Editing the Claude Skill 36:50 - Reviewing Skill Edits 38:10 - Finalizing the Claude Skill 39:30 - Using the Presentation Skill Live 42:15 - Scheduling a Claude Skill 43:55 - Organizing Skills in Departments 45:28 - The Best Way to Master Claude Skills

ZARA

79,405 次观看 • 6 个月前

Obsidian + Claude just killed the $20K/year executive assistant Reads everything you read Remembers everything you forget Briefs you at 6am Compounds for 6 months until your competitors can’t catch up KJRainey shipped the cleanest walkthrough I’ve seen Here’s the 4-evening setup I built on top 👇 Set up the stack like this: > Install Obsidian → create 9 type-based folders (00 CAPTURE → 08 ARCHIVE) > Drop CLAUDE.md into 07 SYSTEM - your model’s operating manual > Telegram bot + Make dot com → 7-second capture from any device > Readwise Official plugin → highlights pipe straight into the vault > Claude Desktop + Filesystem MCP → Claude can read every note > N8N on a $5 droplet → schedules the 2am process + 6am brief First prompt to Claude: > Read every file in 00 - CAPTURE/ > Classify each as observation / quote / question / pattern / decision > Move to the right typed folder, rename YYYY-MM-DD-slug > Add YAML frontmatter (type, captured, source, topics) > Don’t paraphrase. Move and tag only. After it works, tune: > CLAUDE.md priorities + rules of thumb > daily brief length (under 400 words) > the “surprise me” connection prompt > weekly synthesis depth (7 days vs 30 days) > capture friction - if it’s above 7 seconds, kill it > output preferences (tone, format, what NOT to do) The numbers: → 8 minutes/day of capture → $0 in tools (or $25/mo for Claude Pro) → 4 evenings to build (~6 hours total) → Day 30 first surprise. Day 180 uncopyable. - The moat in 2026 isn’t prompts - It isn’t the model - It isn’t the skill library It’s the 6 months of structured context only you have Full breakdown - my synthesis of CyrilXBT, Dami-Defi, and 6 months of running this myself is here Reply “VAULT” + RT and I’ll send you my full CLAUDE.md template + the 4 prompt files (nightly process, daily brief, weekly synthesis, monthly review)

Obsidian + Claude just killed the $20K/year executive assistant Reads everything you read Remembers everything you forget Briefs you at 6am Compounds for 6 months until your competitors can’t catch up KJRainey shipped the cleanest walkthrough I’ve seen Here’s the 4-evening setup I built on top 👇 Set up the stack like this: > Install Obsidian → create 9 type-based folders (00 CAPTURE → 08 ARCHIVE) > Drop CLAUDE.md into 07 SYSTEM - your model’s operating manual > Telegram bot + Make dot com → 7-second capture from any device > Readwise Official plugin → highlights pipe straight into the vault > Claude Desktop + Filesystem MCP → Claude can read every note > N8N on a $5 droplet → schedules the 2am process + 6am brief First prompt to Claude: > Read every file in 00 - CAPTURE/ > Classify each as observation / quote / question / pattern / decision > Move to the right typed folder, rename YYYY-MM-DD-slug > Add YAML frontmatter (type, captured, source, topics) > Don’t paraphrase. Move and tag only. After it works, tune: > CLAUDE.md priorities + rules of thumb > daily brief length (under 400 words) > the “surprise me” connection prompt > weekly synthesis depth (7 days vs 30 days) > capture friction - if it’s above 7 seconds, kill it > output preferences (tone, format, what NOT to do) The numbers: → 8 minutes/day of capture → $0 in tools (or $25/mo for Claude Pro) → 4 evenings to build (~6 hours total) → Day 30 first surprise. Day 180 uncopyable. - The moat in 2026 isn’t prompts - It isn’t the model - It isn’t the skill library It’s the 6 months of structured context only you have Full breakdown - my synthesis of CyrilXBT, Dami-Defi, and 6 months of running this myself is here Reply “VAULT” + RT and I’ll send you my full CLAUDE.md template + the 4 prompt files (nightly process, daily brief, weekly synthesis, monthly review)

ZEUS⚡️

54,511 次观看 • 5 个月前

Obsidian + Claude just killed my $200/month productivity stack - Notion - dead - Readwise - folded into the vault - X bookmarks - replaced by a Telegram bot - Browser bookmarks - gone - ChatGPT for quick analysis - Claude does it now against my actual notes 5 tools. 5 locked rooms with no master key. One vault. One model. One brain. KJRainey shipped the cleanest walkthrough I’ve seen. Here’s the kill-list + the rebuild 👇 What to delete this weekend? > Notion → replace with Obsidian + 9 type-based folders > Readwise → keep account, install the Obsidian Official plugin, kill the separate app > X bookmarks → Telegram bot + Make dot com pushes every forward into 00 - CAPTURE/ > Browser bookmarks → forward the URL to the same bot, never lose a tab again > ChatGPT for analysis → Claude Desktop + Filesystem MCP reads your vault directly What to build instead? > CLAUDE.md in 07 - SYSTEM/ - your model’s operating manual > 9 folders by note type, not by topic (the one decision that breaks vaults) > N8N on a $5 droplet → schedules the 2am process + 6am brief > Daily brief: 3 things to know + 1 connection that would surprise you > Weekly synthesis: 30 days of notes, only non-obvious connections After it works, tune: > capture friction - if it’s above 7 seconds, kill it > CLAUDE.md priorities + rules of thumb > daily brief length (under 400 words) > the “surprise me” connection prompt > weekly synthesis depth (7 days vs 30) > output preferences (tone, format, what NOT to do) The numbers: → 5 subscriptions cancelled → $200/month back in your pocket → 8 minutes/day of capture instead of 5 apps to babysit → Day 30 first surprise. Day 180 uncopyable. The mistake everyone made for 3 years: buying more tools to manage information The unlock in 2026: one place for everything + a model that reasons across all of it Reply “OBSIDIAN” + RT and I’ll send you the migration checklist (Notion → Obsidian, Readwise → plugin, X → Telegram bot) + my CLAUDE.md template

Obsidian + Claude just killed my $200/month productivity stack - Notion - dead - Readwise - folded into the vault - X bookmarks - replaced by a Telegram bot - Browser bookmarks - gone - ChatGPT for quick analysis - Claude does it now against my actual notes 5 tools. 5 locked rooms with no master key. One vault. One model. One brain. KJRainey shipped the cleanest walkthrough I’ve seen. Here’s the kill-list + the rebuild 👇 What to delete this weekend? > Notion → replace with Obsidian + 9 type-based folders > Readwise → keep account, install the Obsidian Official plugin, kill the separate app > X bookmarks → Telegram bot + Make dot com pushes every forward into 00 - CAPTURE/ > Browser bookmarks → forward the URL to the same bot, never lose a tab again > ChatGPT for analysis → Claude Desktop + Filesystem MCP reads your vault directly What to build instead? > CLAUDE.md in 07 - SYSTEM/ - your model’s operating manual > 9 folders by note type, not by topic (the one decision that breaks vaults) > N8N on a $5 droplet → schedules the 2am process + 6am brief > Daily brief: 3 things to know + 1 connection that would surprise you > Weekly synthesis: 30 days of notes, only non-obvious connections After it works, tune: > capture friction - if it’s above 7 seconds, kill it > CLAUDE.md priorities + rules of thumb > daily brief length (under 400 words) > the “surprise me” connection prompt > weekly synthesis depth (7 days vs 30) > output preferences (tone, format, what NOT to do) The numbers: → 5 subscriptions cancelled → $200/month back in your pocket → 8 minutes/day of capture instead of 5 apps to babysit → Day 30 first surprise. Day 180 uncopyable. The mistake everyone made for 3 years: buying more tools to manage information The unlock in 2026: one place for everything + a model that reasons across all of it Reply “OBSIDIAN” + RT and I’ll send you the migration checklist (Notion → Obsidian, Readwise → plugin, X → Telegram bot) + my CLAUDE.md template

ZEUS⚡️

19,031 次观看 • 5 个月前

99% of AI engineers still don't know about Claude skills. Andrew Ng just dropped a 2 hour course with Anthropic on building AI agentic skills from scratch. • 00:00 - build agentic skills with Claude • 22:29 - Claude pre-built skills • 41:04 - skills vs MCP and subagents • 1:06:03 - skills for long running agents • 1:51:59 - live demo to build agentic skills Prompting is dead. Claude skills is how top engineers build AI agents now. I watched it last night. Halfway through, I realized I have been using Claude completely wrong for years. Bookmark this and read the article below.

99% of AI engineers still don't know about Claude skills. Andrew Ng just dropped a 2 hour course with Anthropic on building AI agentic skills from scratch. • 00:00 - build agentic skills with Claude • 22:29 - Claude pre-built skills • 41:04 - skills vs MCP and subagents • 1:06:03 - skills for long running agents • 1:51:59 - live demo to build agentic skills Prompting is dead. Claude skills is how top engineers build AI agents now. I watched it last night. Halfway through, I realized I have been using Claude completely wrong for years. Bookmark this and read the article below.

Roan

22,509 次观看 • 3 个月前

It is becoming f*cking dangerous: when Anthropic shipped CLAUDE.md, they didn't even realize they were opening a Pandora's box 1. Make an empty folder on your computer, call it SECOND BRAIN 2. Open Claude Code inside it 3. Add subfolders: MEMORY/, notes/, people/, projects/ 4. Drop a CLAUDE.md in the root with one rule: save every key fact to MEMORY, one topic per file 5. Add @-links in CLAUDE.md so key files load into context every session 6. Run claude mcp add to connect Playwright MCP, now Claude controls a real browser 7. Build a skill in .claude/skills/ so one command runs the entire routine Folder setup: about 5 minutes Your Claude becomes a second brain: it keeps every key fact between sessions, loads your main files by itself and drives a real browser Full guide in the article below

It is becoming f*cking dangerous: when Anthropic shipped CLAUDE.md, they didn't even realize they were opening a Pandora's box 1. Make an empty folder on your computer, call it SECOND BRAIN 2. Open Claude Code inside it 3. Add subfolders: MEMORY/, notes/, people/, projects/ 4. Drop a CLAUDE.md in the root with one rule: save every key fact to MEMORY, one topic per file 5. Add @-links in CLAUDE.md so key files load into context every session 6. Run claude mcp add to connect Playwright MCP, now Claude controls a real browser 7. Build a skill in .claude/skills/ so one command runs the entire routine Folder setup: about 5 minutes Your Claude becomes a second brain: it keeps every key fact between sessions, loads your main files by itself and drives a real browser Full guide in the article below

plusxbt

69,401 次观看 • 17 天前

Boris Cherny: "My job is to write loops." 5-day version you can copy for Claude Code Day 1: repo memory - write CLAUDE.md - include stack, test commands, code style, release rules, gotchas - add .claude/settings.json with the shell commands Claude can run Day 2: verification skill - pick 1 flow Claude keeps breaking - put the browser/API test in .claude/skills/ /scripts/ - make it return: pass/fail, failing step, screenshot/log path Day 3: commands Add these files: .claude/commands/babysit.md - checks your PRs - reads CI - handles obvious review nits - surfaces design questions .claude/commands/triage-issues.md - labels new issues - dedupes against existing ones - assigns owners .claude/commands/deploy-watch.md - checks the live app - reports regressions - avoids touching production Day 4: loops > /loop 5m /babysit > /loop 15m /triage-issues > /loop 5m /deploy-watch Day 5: overnight work - schedule /morning-report - schedule /deep-audit - write results to .claude/inbox/ - let your morning loop read from that folder The rule: every code-writing loop gets a separate verifier. Builder makes the change. Verifier runs the real app. You read the diff. Skip that and you wake up to 14 broken PRs with very confident summaries. Video: "Reflecting on a year of Claude Code" with Boris Cherny & Cat Wu

Boris Cherny: "My job is to write loops." 5-day version you can copy for Claude Code Day 1: repo memory - write CLAUDE.md - include stack, test commands, code style, release rules, gotchas - add .claude/settings.json with the shell commands Claude can run Day 2: verification skill - pick 1 flow Claude keeps breaking - put the browser/API test in .claude/skills/ /scripts/ - make it return: pass/fail, failing step, screenshot/log path Day 3: commands Add these files: .claude/commands/babysit.md - checks your PRs - reads CI - handles obvious review nits - surfaces design questions .claude/commands/triage-issues.md - labels new issues - dedupes against existing ones - assigns owners .claude/commands/deploy-watch.md - checks the live app - reports regressions - avoids touching production Day 4: loops > /loop 5m /babysit > /loop 15m /triage-issues > /loop 5m /deploy-watch Day 5: overnight work - schedule /morning-report - schedule /deep-audit - write results to .claude/inbox/ - let your morning loop read from that folder The rule: every code-writing loop gets a separate verifier. Builder makes the change. Verifier runs the real app. You read the diff. Skip that and you wake up to 14 broken PRs with very confident summaries. Video: "Reflecting on a year of Claude Code" with Boris Cherny & Cat Wu

Alpha Batcher

141,110 次观看 • 5 个月前

THIS IS A PURE F*CKING GOLD Anthropic made Agent Skills an open spec and GitHub filled up with entire Claude Code engineering teams for free one repo ships 380 skills, 30+ agents and 70+ commands. another one watches your spend in real time so the team you just installed doesn't quietly eat your weekly limit. nobody is charging for any of it 10 GitHub repos worth opening tonight: 01 wshobson/agents → a plugin marketplace that installs the same agents into Claude Code, Codex, Cursor and Copilot, so your setup survives switching tools 02 subinium/awesome-claude-code → a curated list of tools, skills, plugins and MCP servers. the map before you start downloading 03 rohitg00/awesome-claude-code-toolkit → 135 agents, 35 curated skills, 42 commands, 176+ plugins, 20 hooks and 14 MCP configs in one place 04 anthropics/skills → the official Agent Skills repo. start here to see the shape of a working SKILL.md before you copy anyone else's 05 alirezarezvani/claude-skills → 380+ skills, 30+ agents and 70+ commands, portable to Codex, Gemini CLI, Cursor and eight more agents 06 disler/claude-code-hooks-mastery → the hooks reference. this is where you learn to make the agent stop on your rules instead of stopping to ask you 07 muhammadusmangm/claude-code-best-practices → setup, CLAUDE.md templates, multi-agent patterns and cost optimization, written as a wiki instead of a dump 08 Maciek-roboblog/Claude-Code-Usage-Monitor → real-time usage monitor with predictions and warnings, so you find the wall before you hit it 09 Scorpio3310/claude-code-usage-statusline → daily and monthly spend, 5h and weekly limit meters, per-model quotas, all local, no API key 10 eugeniughelbur/obsidian-second-brain → persistent memory as plain markdown in an Obsidian vault, shared across Claude Code, Codex and six other agents install the statusline before you install the agents. you want to watch what the fleet costs while it runs, not find out on Sunday when the weekly meter is already flat then hand the first team one job with an obvious finish line: one reviewed PR, one brief, one red test turned green keep the pieces that changed the result and delete the rest the same day. a config you did not write is a config you cannot debug at 2am the repos cost nothing. four agents repeating the same investigation is where the money actually goes save this one, the list only gets longer from here the article below shows how to keep context small, reuse finished work and contain retries, so more of your budget reaches the finished result ↓

THIS IS A PURE F*CKING GOLD Anthropic made Agent Skills an open spec and GitHub filled up with entire Claude Code engineering teams for free one repo ships 380 skills, 30+ agents and 70+ commands. another one watches your spend in real time so the team you just installed doesn't quietly eat your weekly limit. nobody is charging for any of it 10 GitHub repos worth opening tonight: 01 wshobson/agents → a plugin marketplace that installs the same agents into Claude Code, Codex, Cursor and Copilot, so your setup survives switching tools 02 subinium/awesome-claude-code → a curated list of tools, skills, plugins and MCP servers. the map before you start downloading 03 rohitg00/awesome-claude-code-toolkit → 135 agents, 35 curated skills, 42 commands, 176+ plugins, 20 hooks and 14 MCP configs in one place 04 anthropics/skills → the official Agent Skills repo. start here to see the shape of a working SKILL.md before you copy anyone else's 05 alirezarezvani/claude-skills → 380+ skills, 30+ agents and 70+ commands, portable to Codex, Gemini CLI, Cursor and eight more agents 06 disler/claude-code-hooks-mastery → the hooks reference. this is where you learn to make the agent stop on your rules instead of stopping to ask you 07 muhammadusmangm/claude-code-best-practices → setup, CLAUDE.md templates, multi-agent patterns and cost optimization, written as a wiki instead of a dump 08 Maciek-roboblog/Claude-Code-Usage-Monitor → real-time usage monitor with predictions and warnings, so you find the wall before you hit it 09 Scorpio3310/claude-code-usage-statusline → daily and monthly spend, 5h and weekly limit meters, per-model quotas, all local, no API key 10 eugeniughelbur/obsidian-second-brain → persistent memory as plain markdown in an Obsidian vault, shared across Claude Code, Codex and six other agents install the statusline before you install the agents. you want to watch what the fleet costs while it runs, not find out on Sunday when the weekly meter is already flat then hand the first team one job with an obvious finish line: one reviewed PR, one brief, one red test turned green keep the pieces that changed the result and delete the rest the same day. a config you did not write is a config you cannot debug at 2am the repos cost nothing. four agents repeating the same investigation is where the money actually goes save this one, the list only gets longer from here the article below shows how to keep context small, reuse finished work and contain retries, so more of your budget reaches the finished result ↓

delost

12,765 次观看 • 16 天前

THE CEO OF OBSIDIAN JUST SHIPPED THE PATCH THAT LETS CLAUDE CODE DRIVE YOUR VAULT INSTEAD OF JUST READING IT. THE REPO PASSED 12,000 STARS BEFORE THE OFFICIAL ANNOUNCEMENT WENT UP 5 SKILL.md files. 1 MIT license. 0 lines of glue code drop .claude/skills/ into any vault. Claude Code registers Markdown, Bases, Canvas, CLI, and Webclipper on next session boot from that moment Claude opens the app, writes a Base view with the correct YAML, drops nodes on a Canvas, follows wikilinks correctly, clips URLs the way a power-user would. every action is a native Obsidian operation, not a text munge three formats that used to require a plugin developer or a paid template. now they get emitted by the same agent that writes your notes no MCP server. no vector db. no plugin store. no daemon in the background three years since kepano wrote "File over app". now the file has an agent that respects it you're reading this on a device that could clone the repo into your vault's .claude/skills/ folder and have Claude Code writing your first Base by lunch

THE CEO OF OBSIDIAN JUST SHIPPED THE PATCH THAT LETS CLAUDE CODE DRIVE YOUR VAULT INSTEAD OF JUST READING IT. THE REPO PASSED 12,000 STARS BEFORE THE OFFICIAL ANNOUNCEMENT WENT UP 5 SKILL.md files. 1 MIT license. 0 lines of glue code drop .claude/skills/ into any vault. Claude Code registers Markdown, Bases, Canvas, CLI, and Webclipper on next session boot from that moment Claude opens the app, writes a Base view with the correct YAML, drops nodes on a Canvas, follows wikilinks correctly, clips URLs the way a power-user would. every action is a native Obsidian operation, not a text munge three formats that used to require a plugin developer or a paid template. now they get emitted by the same agent that writes your notes no MCP server. no vector db. no plugin store. no daemon in the background three years since kepano wrote "File over app". now the file has an agent that respects it you're reading this on a device that could clone the repo into your vault's .claude/skills/ folder and have Claude Code writing your first Base by lunch

chewa.

13,367 次观看 • 3 个月前

Important new course: Agent Skills with Anthropic, built with Anthropic and taught by Elie Schoppik! Skills are constructed as folders of instructions that equip agents with on-demand knowledge and workflows. This short course teaches you how to create them following best practices. Because skills follow an open standard format, you can build them once and deploy across any skills-compatible agent, like Claude Code. What you'll learn: - Create custom skills for code generation and review, data analysis, and research - Build complex workflows using Anthropic's pre-built skills (Excel, PowerPoint, skill creation) and custom skills - Combine skills with MCP and subagents to create agentic systems with specialized knowledge - Deploy the same skills across Claude Code, the Claude API, and the Claude Agent SDK Join and learn to equip agents with the specialized knowledge they need for reliable, repeatable workflows.

Important new course: Agent Skills with Anthropic, built with Anthropic and taught by Elie Schoppik! Skills are constructed as folders of instructions that equip agents with on-demand knowledge and workflows. This short course teaches you how to create them following best practices. Because skills follow an open standard format, you can build them once and deploy across any skills-compatible agent, like Claude Code. What you'll learn: - Create custom skills for code generation and review, data analysis, and research - Build complex workflows using Anthropic's pre-built skills (Excel, PowerPoint, skill creation) and custom skills - Combine skills with MCP and subagents to create agentic systems with specialized knowledge - Deploy the same skills across Claude Code, the Claude API, and the Claude Agent SDK Join and learn to equip agents with the specialized knowledge they need for reliable, repeatable workflows.

Andrew Ng

891,429 次观看 • 9 个月前

I am genuinely baffled why everyone is sleeping on this feature: Claude Code can review your CLAUDE.md configuration and weed out outdated legacy rules meant for older iterations 1. Upgrade your Claude Code utility to version v2.1.283 (or newer) via: claude update 2. Navigate into your project workspace and execute: /doctor prompt-audit 3. The tool scans CLAUDE.md, AGENTS.md, custom rules, skills, and command definitions located in .claude/ and ~/.claude/ 4. It flags prompts and guidelines tailored specifically for previous-gen models 5. It spots broken references pointing to missing files or non-existent commands 6. It catches conflicting instructions across your configuration files 7. You get a comprehensive breakdown of suggested fixes, and nothing gets modified until you explicitly tell Claude to apply them Targeting a single directory: /doctor prompt-audit .claude/ skills/deploy Anthropic guidelines state: keep individual CLAUDE.md files under 200 lines. If rules clash with one another, Claude might end up picking one at random Check out the full CLAUDE.md template and directory layout in the linked article below

I am genuinely baffled why everyone is sleeping on this feature: Claude Code can review your CLAUDE.md configuration and weed out outdated legacy rules meant for older iterations 1. Upgrade your Claude Code utility to version v2.1.283 (or newer) via: claude update 2. Navigate into your project workspace and execute: /doctor prompt-audit 3. The tool scans CLAUDE.md, AGENTS.md, custom rules, skills, and command definitions located in .claude/ and ~/.claude/ 4. It flags prompts and guidelines tailored specifically for previous-gen models 5. It spots broken references pointing to missing files or non-existent commands 6. It catches conflicting instructions across your configuration files 7. You get a comprehensive breakdown of suggested fixes, and nothing gets modified until you explicitly tell Claude to apply them Targeting a single directory: /doctor prompt-audit .claude/ skills/deploy Anthropic guidelines state: keep individual CLAUDE.md files under 200 lines. If rules clash with one another, Claude might end up picking one at random Check out the full CLAUDE.md template and directory layout in the linked article below

Bober_smart

15,022 次观看 • 11 天前

Claude Skills are a cheat code for DTC creative teams 🤯 One setup, reusable forever. Claude automatically follows your exact creative process — briefs, hooks, ad copy, research — without you explaining anything twice. Perfect for e-comm brands and agencies who are using Claude for creative work but wasting time re-explaining context every single conversation. Here's the problem: You open Claude: you paste in your brand guidelines, explain your brief format, write the copy, you close the chat. Next day, you do it all over again. Every conversation starts from zero. You're burning 20 minutes on setup before you even get to the actual work. Claude Skills fix this: → Write your creative process once as a Skill (a simple markdown file) → Claude reads it automatically whenever the task comes up → Skills compose — research triggers the research Skill, briefs trigger the brief Skill, copy triggers the copy Skill → All in one conversation, all building on each other → Share across your team so everyone gets the same quality output No re-explaining your brand voice. No pasting the same context every chat. No siloed projects that don't talk to each other. What's in the playbook: → The full architecture (how Skills trigger, chain, and compose) → 5 ready-to-use Skill templates built for DTC and agency creative teams → Step-by-step setup from zero to working Skills → How to write instructions that produce consistent output every time → The composability framework for running multi-step creative workflows in one conversation I put together the complete Claude Skills Playbook for DTC brands and creative agencies. Want it for free? >Like this post >Comment "SKILLS" And I'll send it over (must be following so I can DM)

Mike Futia

32,046 次观看 • 8 个月前

Anthropic dropped a free 59-minute Claude Code course From autocomplete to real agents: 00:00 - From autocomplete to agents 04:50 - How the agentic loop works 14:07 - CLAUDE.md as project memory 26:53 - Why Plan Mode comes first 33:31 - Live task from brief to commit 54:46 - Skills vs CLAUDE.md Most people still use Claude Code like a smarter autocomplete This shows how Anthropic uses it to plan, call tools, test, and ship real work Worth more than 99% of paid Claude Code tutorials Bookmark and watch it later

Anthropic dropped a free 59-minute Claude Code course From autocomplete to real agents: 00:00 - From autocomplete to agents 04:50 - How the agentic loop works 14:07 - CLAUDE.md as project memory 26:53 - Why Plan Mode comes first 33:31 - Live task from brief to commit 54:46 - Skills vs CLAUDE.md Most people still use Claude Code like a smarter autocomplete This shows how Anthropic uses it to plan, call tools, test, and ship real work Worth more than 99% of paid Claude Code tutorials Bookmark and watch it later

rari🈀

120,991 次观看 • 3 个月前

💥NEW AI CODING TUTORIAL: 12 Months of Claude Code Lessons in 46 Minutes Claude Code just turned 1. So here's 52 lessons on how to get the most out of Claude Code, organized into 3 levels: Beginner, Intermediate, and Master. TIMESTAMPS 00:00 12 Months of building with Claude Code 02:01 LEVEL 1: Beginner 02:09 Installation and Setup 04:55 Models and Modes 09:04 CLAUDE.md (and what to put in) 10:30 Context Management 11:31 Debugging with Claude 12:22 Version control 14:12 Prompting, Just ask Claude 16:01 LEVEL 2: Intermediate 16:24 Customizations (Skills, Plugins, MCPs) 24:42 Workflows: Plan, Build, Test 29:52 Verifying and Documenting with Claude 33:10 LEVEL 3: Master 34:17 Multi-Agent Development (multi-clauding with git worktrees) 37:07 Self-improving Systems 38:45 Ralph Wiggum Agent Loops 40:11 Async Task Delegation 42:00 Agent Teams, Pre-configure permissions, Hooks 44:42 Continue your learning

💥NEW AI CODING TUTORIAL: 12 Months of Claude Code Lessons in 46 Minutes Claude Code just turned 1. So here's 52 lessons on how to get the most out of Claude Code, organized into 3 levels: Beginner, Intermediate, and Master. TIMESTAMPS 00:00 12 Months of building with Claude Code 02:01 LEVEL 1: Beginner 02:09 Installation and Setup 04:55 Models and Modes 09:04 CLAUDE.md (and what to put in) 10:30 Context Management 11:31 Debugging with Claude 12:22 Version control 14:12 Prompting, Just ask Claude 16:01 LEVEL 2: Intermediate 16:24 Customizations (Skills, Plugins, MCPs) 24:42 Workflows: Plan, Build, Test 29:52 Verifying and Documenting with Claude 33:10 LEVEL 3: Master 34:17 Multi-Agent Development (multi-clauding with git worktrees) 37:07 Self-improving Systems 38:45 Ralph Wiggum Agent Loops 40:11 Async Task Delegation 42:00 Agent Teams, Pre-configure permissions, Hooks 44:42 Continue your learning

Avthar Sewrathan

63,326 次观看 • 8 个月前

THIS IS F*CKING INSANE Anthropic turned Agent Skills into an open spec and GitHub filled up with ready-made Claude Code teams for free one of these repos alone ships 135 agents, 35 skills, 42 commands, 176+ plugins and 20 hooks. another hands you 100+ specialized subagents. none of it costs anything 10 GitHub projects you should open first: 01 wshobson/agents → a plugin marketplace that installs the same agents into Claude Code, Codex, Cursor and Copilot, so your setup survives switching tools 02 VoltAgent/awesome-claude-code-subagents → 100+ specialized subagents covering most of what a normal engineering week throws at you 03 rohitg00/awesome-claude-code-toolkit → 135 agents, 35 curated skills, 42 commands, 176+ plugins, 20 hooks and 14 MCP configs in one place 04 anthropics/skills → the official Agent Skills repo. start here to see the shape of a working SKILL.md before you copy anyone else's 05 netresearch/claude-code-marketplace → curated skills on an open standard, portable across Claude Code, Cursor, Copilot, Codex, Gemini CLI and 30+ other agents 06 disler/claude-code-hooks-mastery → the hooks reference. this is where you learn to make the agent stop on your rules instead of stopping to ask you 07 karanb192/claude-code-hooks → an installable hooks marketplace split into safety, cost, observability and productivity 08 affaan-m/claude-swarm → multi-agent orchestration that decomposes the task, coordinates the agents and shows the whole run in a terminal UI 09 am-will/swarms → orchestration shipped as skills, so the coordination loads only when the job actually calls for it 10 eugeniughelbur/obsidian-second-brain → persistent memory as plain markdown in an Obsidian vault, shared across Claude Code, Codex and six other agents give the first team a job with an obvious finish line: one reviewed PR, one researched brief, one failing test turned green then look at how much of that output you actually kept, and what it cost to produce. a bigger roster earns its place when it moves that number the download is free. paying four agents to repeat the same investigation is not save this before you spend another weekend building a config that already exists the article below shows how to keep context small, reuse finished work and contain retries, so more of your budget reaches the finished result ↓

THIS IS F*CKING INSANE Anthropic turned Agent Skills into an open spec and GitHub filled up with ready-made Claude Code teams for free one of these repos alone ships 135 agents, 35 skills, 42 commands, 176+ plugins and 20 hooks. another hands you 100+ specialized subagents. none of it costs anything 10 GitHub projects you should open first: 01 wshobson/agents → a plugin marketplace that installs the same agents into Claude Code, Codex, Cursor and Copilot, so your setup survives switching tools 02 VoltAgent/awesome-claude-code-subagents → 100+ specialized subagents covering most of what a normal engineering week throws at you 03 rohitg00/awesome-claude-code-toolkit → 135 agents, 35 curated skills, 42 commands, 176+ plugins, 20 hooks and 14 MCP configs in one place 04 anthropics/skills → the official Agent Skills repo. start here to see the shape of a working SKILL.md before you copy anyone else's 05 netresearch/claude-code-marketplace → curated skills on an open standard, portable across Claude Code, Cursor, Copilot, Codex, Gemini CLI and 30+ other agents 06 disler/claude-code-hooks-mastery → the hooks reference. this is where you learn to make the agent stop on your rules instead of stopping to ask you 07 karanb192/claude-code-hooks → an installable hooks marketplace split into safety, cost, observability and productivity 08 affaan-m/claude-swarm → multi-agent orchestration that decomposes the task, coordinates the agents and shows the whole run in a terminal UI 09 am-will/swarms → orchestration shipped as skills, so the coordination loads only when the job actually calls for it 10 eugeniughelbur/obsidian-second-brain → persistent memory as plain markdown in an Obsidian vault, shared across Claude Code, Codex and six other agents give the first team a job with an obvious finish line: one reviewed PR, one researched brief, one failing test turned green then look at how much of that output you actually kept, and what it cost to produce. a bigger roster earns its place when it moves that number the download is free. paying four agents to repeat the same investigation is not save this before you spend another weekend building a config that already exists the article below shows how to keep context small, reuse finished work and contain retries, so more of your budget reaches the finished result ↓

delost

96,871 次观看 • 17 天前

Built a 3-layer Memory Stack that wires Claude Code directly into Obsidian with skills so it never forgets your project DNA, your notes, your standards, or your goals. Fixes most of Claude Code's memory issues.

Built a 3-layer Memory Stack that wires Claude Code directly into Obsidian with skills so it never forgets your project DNA, your notes, your standards, or your goals. Fixes most of Claude Code's memory issues.

WorldofAI

115,934 次观看 • 7 个月前

I still don’t understand why people keep building a Claude second brain by hand when these 10 repos already built the whole system They turn your Claude sessions into a wiki, let Claude read and write your vault from your phone, and one of them comes straight from Obsidian’s own CEO 01 llm-wiki → your Claude Code and Codex sessions become a searchable wiki, with an MCP server to query it 02 llm-wiki-claude-skill → one skill file teaches Claude to ingest sources, answer from them, lint the wiki and compile it into clean pages 03 obsidian-skills → Obsidian’s own CEO teaches Claude how Obsidian really works 04 llm-wiki → a Claude Code plugin with init, ingest, compile, query and lint, where every change is committed to git 05 obsidian-dev-second-brain → your tickets, sprints and project docs live in the vault as notes, and Claude keeps them in sync with the code 06 obsidian-mcp-server → 14 tools to read, write, search and surgically edit notes, tags and frontmatter 07 mcpvault → safe vault access with a read-only mode, and Obsidian doesn’t even need to be running 08 obsidian-claude-code-mcp → connect Claude Code to your open vault with one /ide command 09 obsidian-web-mcp → reach your vault from your phone or any MCP client, with OAuth and a Cloudflare Tunnel 10 obsidian-mcp → a git-backed vault with 18 tools, running locally or on AWS Lambda Nobody is going to build your second brain for you, and every chat you close without one is knowledge thrown away. Bookmark this, pick one repo from 01 to 05 and ingest your first source tonight. A month from now you have a wiki, and everyone who skipped it is still opening a blank chat.

I still don’t understand why people keep building a Claude second brain by hand when these 10 repos already built the whole system They turn your Claude sessions into a wiki, let Claude read and write your vault from your phone, and one of them comes straight from Obsidian’s own CEO 01 llm-wiki → your Claude Code and Codex sessions become a searchable wiki, with an MCP server to query it 02 llm-wiki-claude-skill → one skill file teaches Claude to ingest sources, answer from them, lint the wiki and compile it into clean pages 03 obsidian-skills → Obsidian’s own CEO teaches Claude how Obsidian really works 04 llm-wiki → a Claude Code plugin with init, ingest, compile, query and lint, where every change is committed to git 05 obsidian-dev-second-brain → your tickets, sprints and project docs live in the vault as notes, and Claude keeps them in sync with the code 06 obsidian-mcp-server → 14 tools to read, write, search and surgically edit notes, tags and frontmatter 07 mcpvault → safe vault access with a read-only mode, and Obsidian doesn’t even need to be running 08 obsidian-claude-code-mcp → connect Claude Code to your open vault with one /ide command 09 obsidian-web-mcp → reach your vault from your phone or any MCP client, with OAuth and a Cloudflare Tunnel 10 obsidian-mcp → a git-backed vault with 18 tools, running locally or on AWS Lambda Nobody is going to build your second brain for you, and every chat you close without one is knowledge thrown away. Bookmark this, pick one repo from 01 to 05 and ingest your first source tonight. A month from now you have a wiki, and everyone who skipped it is still opening a blank chat.

Ryven

10,722 次观看 • 7 天前

Claude R Perrin Code SDK is under-rated One cool part with Claude Code SDK is that it supports full features out of box: - Skills - Sub agents - Hooks - ... Which means you can use claude code CLI as a debug tool to build agent, and then import to your Claude code powered agent Here is a quick example of a pptx presentation agent using Claude Code SDK + doc skills Code example from AI Builder Club by Kai:

Claude R Perrin Code SDK is under-rated One cool part with Claude Code SDK is that it supports full features out of box: - Skills - Sub agents - Hooks - ... Which means you can use claude code CLI as a debug tool to build agent, and then import to your Claude code powered agent Here is a quick example of a pptx presentation agent using Claude Code SDK + doc skills Code example from AI Builder Club by Kai:

Jason Zhou

11,981 次观看 • 1 年前