Hey guys, I am battling to find the skill builder files to continue with day 3 of the 7 Day AIS Challenge. Can anyone please help? Thank you!

Note: I can’t share any real data from this build. Everything below describes how it works. I built a weekly task that gives me two things in one go: a performance report and a hygiene check on how the team keeps its records. It runs on its own, once a week. Why I built it: I oversee four teams, each with a manager and reps. Our process is very manual. Reps log their own meetings in trackers and lead sheets and nothing checks whether they’re being kept up. Checking meant opening a lot of files by hand, which took a long time so it kept slipping. The performance report: - The month’s numbers for every rep, every team and the whole region: meetings booked, meetings sat, show rate and opportunities. - A check on whether the account executives are getting a fair share of the meetings, with gaps flagged. The hygiene check - for every rep, it checks that: - Their trackers are up to date in full, with no missing fields and no impossible dates. - Meetings in the past have an outcome recorded - Every meeting has a lead sheet I get a draft per team, ready to forward to each manager, plus a summary for me. Nothing is sent without me. What took the time: It was writing the instructions and pointing Claude to exactly where to go: which folders, which tabs, which files to read and which to ignore, who is on each team and what counts as a problem. The self-improving part: Mine reads a short status file (memory file) at the start and proposes an updated version at the end. It can’t write the file itself and I approve every update. That way it gets better each week without drifting on its own. Model used: Sonnet 5.5 - ran perfectly first time!

I grew up in Pittsburgh and have always followed the Steelers, so my automation was a natural...At 7am each morning research and gather new Steelers articles from a variety of sources. Then I used resend to email to me. One thing that broke...Initially had a deprecated token from Trigger.dev. Walked through and replaced. Also had to tweak my GitHub repository. Added MCP but am waiting before I change to split multiple tasks.

From multi-month consulting contracts and back-to-back UpWork clients to #1 AEO rankings, hackathon wins, and 50 paid signups in 24 hours - the week after AIS Live kept the momentum going. 🚀 Standout Wins of the Week inside AIS+ 👉 @Gerard Vazquez closed a multi-month AI consulting + implementation contract with his first Australian client, working 4 days a week with a 20-person company. 👉 @Dean Razic landed two UpWork clients back-to-back — first a $2K project, then another $3K website build. 👉 @Nicole Jolie took a client from zero visibility to #1 in AEO, with no remaining AEO issues across the site. 👉 @Ronald Addico launched his Skool community and brought in 50 paid members plus 1,084 waitlist signups in under 24 hours — with zero paid ads. 👉 @Jeffery Gyamerah and his teammate won HackIAton, beating 350 teams across Panama, Ecuador, and Argentina. ⸻ 🎥 Super Win Spotlight | @Dennis Hettema Dennis had already spent months building Hello Revenue when he joined AIS+. He didn’t need more AI hype. He needed other serious builders who could challenge how he was thinking. Through live calls and conversations inside the community, he found the kind of human input AI couldn’t give him - different perspectives, context, and people willing to push back. That helped him break through technical roadblocks and improve the system he was building. Today, Hello Revenue is producing results across multiple industries and bringing in new clients. His biggest takeaway? AI is powerful. But if you’re serious about building, you still need great people around you. 🎥 Watch Dennis’s story 👇 ✨ Sometimes the breakthrough isn’t another model, prompt, or tool. It’s one conversation that helps you see the problem differently.

https://website-builder-orcin-nine.vercel.app/ Happy with this build. Didn't feel the need to change much. The interactive piece on the hero background it built on its own the first time. I kept it as is. For brand assets I had my logo but didn't have brand guidelines so went into plan mode with Claude to put that together which I thought was really cool. I liked the minimalist design, easy to read, added a few more calls to action and spent a bit of time making a few changes which helped me actually think about the message I'm sending and how its positioned but really like how this has come out.