Activity
Mon
Wed
Fri
Sun
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
What is this?
Less
More
Build Market Close

396 members • Free

Maker Zero: Claude Code, AI

19.5k members • Free

The AI Workforce

2.3k members • Free

AI Automation Vault

33.2k members • Free

Clief Notes

46.5k members • Free

AI Automation (A-Z)

164.8k members • $7/month

Automate Business AI

6.2k members • $77/month

Samin's Free AI Resource Hub

21.3k members • Free

NextGen AI

53.5k members • Free

7 contributions to Clief Notes
The Clief Notes AI is live 📣
It’s live. Starting today, everyone in Clief Notes has access to the new Clief Notes AI. The easiest way to use it? Don’t overthink it. Ask it the question you would normally ask me. “Where should I start?” “What should I focus on next?” “Where did you talk about [topic]?” It’ll use what’s already inside Clief Notes to help answer you and point you toward the right lesson or resource when there’s something worth going deeper on. The goal isn’t to give you another AI tool to play with. It’s to make everything already inside this community easier to actually use. If you want Access to it Comment "READY" and we'll send you access to it!
1 like • 9d
Ready
"Don't Build Agents, Build Skills Instead"
Sound familiar... Claude Code is the universal interface, the coding agent has many use cases. Barry Zhang and Mahesh Murag from Anthropic, who helped develop "Agent Skills", argue that the future of AI lies in modular, shareable capabilities rather than monolithic agent development. They outline how organizing procedural knowledge into files allows agents to gain domain expertise and evolve through continuous learning. I found this Anthropic talk on YouTube, interesting because its core argument closely matches the design logic behind ICM: don’t keep rebuilding specialized agents; make the operational knowledge reusable, inspectable, and easy to improve. Barry Zhang and Mahesh Murag describe an Agent Skill as an organized folder of procedural knowledge: instructions, references, scripts, and assets, that an agent can load when needed. Their key point is that a generally capable agent often lacks domain-specific expertise; skills package that expertise in a portable form. The agent only loads metadata until the skill is relevant, then pulls in the fuller instructions and supporting files. That keeps context focused while making capabilities composable. The connection to ICM is strong. ICM uses filesystem structure and Markdown to orchestrate focused, multi-stage work: each stage receives only the context it needs, produces a visible intermediate output, and hands that output to the next stage. Both approaches treat folders and plain-language files as the control surface rather than burying workflow knowledge in opaque code or a giant prompt. The main difference is scope. Anthropic Skills are reusable capability packages “how to do a kind of work.” ICM is a human-reviewable workflow architecture, “how this particular job moves through stages.” They fit together naturally: an ICM stage could invoke a relevant skill, while the ICM workspace controls sequencing, scoped context, artifacts, and review points.
ICM "2.0" 🗂️🎂🪎
I have been living inside ICM for a while now, and it changed how I build. Recently I started pairing it with one more idea, and the combination clicked hard enough that I wanted to share it here and see what you all think. Quick version: ICM 2.0 = ICM (the interpretable filesystem) + Colibri style routing (a router that only wakes the experts a task actually needs). One gives you a system you can read. The other gives you a system that stays light. Together they run local and sovereign (this system build ACTUALLY helped me move the needle, i.e. KPI, creating content, closing deals, etc) --- 🗂️ First, why ICM already wins For anyone newer to it, the core of ICM as I understand it: 1. The filesystem is the operating system. Plain-text steps, one job per folder. No black box. 2. It documents itself. Every folder says where you are and what is next, so you never lose the thread. 3. It is resumable. Close the laptop, come back next week, pick up exactly where you were. 4. It is portable. What runs in your head, in an agent, or on a local model is the same folder of plain steps. The magic is interpretability. You can always open the box and see the reasoning. 🐦 The piece I added: Colibri (the router) The problem with a big system is that it gets heavy. You do not want every folder, every expert, every context loaded for every task. A hummingbird does not flap every muscle to hover, it uses only what the moment needs. Colibri is a mixture-of-experts idea applied to a whole life or business: 1. Only a sliver is ever active. Roughly 5 percent at a time, not the whole library. 2. A router picks the ~8 experts the task needs** and wakes only those folders. 3. Core stays pinned, the rest streams in** on demand and caches while it is hot. 4. It learns to predict which experts you will reach for next, so the right context is already warm. 🧬 Put them together and you get ICM 2.0 1. The ICM filesystem becomes the DNA / schema** — the canonical map of every expert the system can call.
ICM "2.0" 🗂️🎂🪎
1 like • 24d
Running Large LLMs Locally: Understanding the Colibrì Inference Engine, ICM, and Hardware Trade-Offs When choosing to run a Local Large Language Model (LLM) on your own machine, the decision usually comes down to data control, hardware limitations, and time. For many professionals and researchers, running a local model is a strict operational requirement. If you handle clients with tight operating procedures, you cannot risk exposing Personally Identifiable Information (PII) or Protected Health Information (PHI) to third-party cloud providers. Keeping data entirely local ensures absolute compliance with privacy standards and regulations. However, standard local runners require massive amounts of compute. The larger the model, the more RAM and dedicated VRAM (Graphics Card memory) you need. This breakdown analyzes how the novel Colibrì engine attempts to solve the hardware bottleneck, how it interacts with frameworks like the Interpretable Context Methodology (ICM), and why standard local alternatives are usually a better choice for daily work. The Colibrì Solution: SSD as RAM Normally, if you do not have enough RAM or a dedicated Graphics Card, you simply cannot load large-scale models. Colibrì changes this by using your Solid State Drive (SSD) to dynamically act as part of your system RAM. Instead of loading a massive model entirely into memory, Colibrì streams the data chunks off your local drive on demand. The Catch: Only One 744B Petameter Model Supported Unlike flexible tools like llama.cpp, Ollama, or, LM Studio Colibrì is not a general-purpose runner. - It is a specialized proof-of-concept custom-coded for exactly one model: GLM-5.2 (a massive 744 Billion parameter Mixture-of-Experts model). - You cannot use it to run standard, smaller models like Llama 3 8B or Mistral 7B. Pros and Cons of the Colibrì System The Pros: - Zero Cloud Exposure: Complete local data privacy for strict PII and PHI compliance workflows. - Extreme Hardware Accessibility: Bypasses the need for expensive enterprise GPU clusters. - Runs Massive Models: Allows standard consumer hardware to execute a 744B parameter architecture.
NEW COURSE: The Archive is live.
Here is the pitch. A lot of you found this community through my recent content. Folder architecture. ICM. Computational orchestration. You are learning systems that work right now. Fair question: will they still work in three years? I recorded videos about AI and education in 2023 and early 2024. Before most people had figured out what ChatGPT was for. Before "context engineering" was a phrase. Before anyone was talking about agent architecture or structured AI workflows. I went back and reviewed every one of those videos or articles against what actually happened. The core ideas held up. Almost all of them. The ones that needed updating got honest revisions. Nothing was glossed over. This course pairs those older videos with written companions that show exactly what I got right, what changed, and where the thinking went. Then Module 3 picks up with slightly more current yet still older articles on computational orchestration, AI ownership, energy infrastructure, and the questions nobody else is asking yet. If you want to know whether the frameworks I teach have staying power, this course is the evidence. Over Three years of receipts. The Archive is free and available now in the classroom. Thanks for all the support, everyone. Happy Learning. LESSON 1.1: Welcome - The Archive · Clief Notes
NEW COURSE: The Archive is live.
2 likes • Apr 4
Thank you!
THANKYOU (Edit of :I need your help but it's optional. )
UPDATE: SHE GOT INTO THE NEXT ROUND THANKYOU ALL SO MUCH. Another round of voting this week if you want it keep voting for us ! Completely unrelated to AI. My stepdaughter is in a competition to meet Jeff corwin. (My childhood hero when it came to animals) And she just needs a vote in a competition everyday for the next few days. Completely free to cast one vote. So if anyone is willing to just click the link and cast a vote that would be super nice. Totally don't have to as I understand this is completely separate from AI lol https://jr-ranger.org/2026/wylder-533c
THANKYOU (Edit of :I need your help but it's optional. )
1 like • Apr 2
Done!
1-7 of 7
Jared Marin
3
42 points to level up
@jared-marin-9907
Creator here to learn.

Active 16h ago
Joined Mar 9, 2026
Powered by