Activity
Mon
Wed
Fri
Sun
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
What is this?
Less
More
Clief Notes
49.2k
5.0
Free
355 contributions to Clief Notes
How to efficiently reference file content in cloud, reducing local copies?
Hi community, I've been building an ICM for my job as a Solution Consultant. One workflow I have is about status updates on customers that require referencing the latest in MS Teams chats/channels and Sharepoint files in a few folders (word, pptx, excel, mp4), among many other tools. In this post I will focus on those two. Workflow descriptions: 1. Workflow that runs the first time I ask about a customer, which searches everything and build the first 'log' for that customer. This one I'm happy with. 2. Workflow that runs on any subsequent request that searches the latest 2 weeks of content, or the latest since the last 'log' on the customer. This one I need help with. ICM structure: - CLAUDE.md: Routes the request to the customer folder context file - /customer/CONTEXT.md: Describes the two workflows and selects which ones to run and steps on how to create the 'log' files in new subfolders. Each workflow references the reference context file to know how to connect to tools like cloud storage to pull content. - /references/CONTEX.md: Has all the descriptions on how to connect to all cloud tools and where to look for info, like hyperlinks to customer notes folders Question: - The problem I'm running into is that sometimes a key fact is missing from the response because of the way the information got parsed by the LLM. I'm not expecting it to read everything, but I do expect it to prioritize certain things when I'm updating how I want the status to look like.Are there some tips you can share with me? I was looking into knowledge graph, but the examples I saw were using files locally. Maybe I need to markdown-ify my content? I want to hear from the community if you have ran into something similar. Thank you!
1 like • 21h
@Carlos Cordova Knowledge graph — I would skip it here. Graphs earn their keep when you need relationships across many entities (who owns what, which SOW ties to which contract). A status log just needs to not drop facts, which is a smaller problem than a graph solves. Markdown-ifying — yes, but not for graph-readiness. It's that Word/PPT/Excel give you inconsistent structure to search against. Flat text lets your workflow grep for exactly what it needs instead of relying on the model to notice it inside formatted Office content. The real fix is splitting extraction from synthesis. Right now your delta workflow probably reads the new content and writes the updated log in one pass, so "what matters" gets decided in the same breath as the narration — that's where a fact slips. Add a step between them: pull facts into fixed buckets first (decisions, blockers, dates, dollar/scope changes, named owners, whatever your log actually tracks) as a structured intermediate file, then write the log from that file instead of the raw source. Filling a named slot loses far fewer facts than free narration does. And since your full-build workflow already works — don't re-narrate the whole customer history on every delta. Run the same bucket-extraction against just the new content since the last log, then merge into the existing file. Smaller surface, fewer places for something to fall out.
Email Automation that runs all the time
So i build an email automation than runs based on some files and folders and the whole system runs all the time even if my PC is off. Used JEV as a decision layer. Used connectors(google drive, gmail and calendar) and Routines. Even this video was created through icm.
Email Automation that runs all the time
1 like • 21h
Brilliant! And great application of multiple Models to work together.
Awesome Resources
Hey Clief Notes fam! 👋 I'm Amy Johnson and I'm happy to be here. 🙋 A little about me: I am a franchisor of a donut business. I have over 50 franchisees and am working on building AI systems for all of us to make business easier. 🎯 My current goal: Building an AI Franchise Kit Biggest Struggle right networking and finding people who can talk ICM with.
1 like • 21h
You arrived at the ICM headquarters, where you can have your fill of questions answered. If you show your build along the way, we would all help contribute ideas. Have you mapped a general idea of this on paper? Like rough work flow? Could be diagram with lines and bubbles, could be a tree, could be a recipe. That will clear where AI fits and where other tools and structures would work better.
Did I Really Lose 2 Weeks Of Code Updates?
I was creating a second version of a pricing engine I built. Claude decided to deploy onto my live site, and then overwrote the local file where the latest updates for that code lived, apparently. The last commit to git was two weeks ago. So, I think I just lost 2 weeks of de-bugging code cause I didn't commit the latest version to git. Is this real? Did I just skip the most important step -- saving my work? This is a real thing, right?
1 like • 21h
[attachment]
Module 4 finally has its new videos 🎉
Apparently “I’ll get those videos out soon” needed a clearer deadline. Preferably one I actually followed. 😂 Sorry these took longer than planned, everyone. The new videos for Foundation lessons 4.1–4.4 are now live! These look quite different from most of my videos. I’m trying a mix of animation, actual app screenshots, highlighted instructions, and worked examples to make the ideas easier to follow—and easier to try yourself. Here’s where to jump in: 👉 4.1: Install and First Use — 5:37 Start here if you’re still getting comfortable working with AI and local files. Grab the Foundation Practice download in Resources so you have something concrete to work with. 👉 4.2: Working With Files — 7:45 Take a few meeting notes and turn them into a decision list you can actually check. Who agreed to what? Where did that deadline come from? What’s still unanswered? 👉 4.3: Think, Then Build — 8:24 For those times when you ask AI for a whole plan before you’ve quite decided what you want. Compare your options, choose an approach, and turn it into a short brief before building. 👉 4.4: Project Instructions — 7:09 Give your AI a useful onboarding note: where to find the context, where the draft should go, and what needs checking. Includes the AGENTS.md / CLAUDE.md connection for people using Codex, Claude Code, or both. You can also follow the exercises with a regular chat tool and save the files yourself. I would love some honest feedback on this style. Does the animation help things click? Are the app screenshots useful? Is anything moving too quickly—or taking too long?
3 likes • 21h
Great videos! And always fun to look back at foundations.
1-10 of 355
Gabriel Azoulay
7
5,884 points to level up
@gabriel-azoulay-3254
Yoga and Thai Massage Teacher turned Ai Architect

Online now
Joined Jul 26, 2026
Khao Lak, Thailand
Powered by