Elizabeth-Stief

Who They Are

Elizabeth Stief is a highly technically sophisticated AIMM member who consistently operates at the frontier of practical AI implementation — and surprises the group by doing so quietly. Lou noted explicitly that she “consistently surprises with her depth of technical understanding,” a remark made after a session where she diagnosed and resolved a skill-slop problem that would have stumped most practitioners. Her contributions tend to arrive as operational discoveries rather than theoretical frameworks: a monitoring workflow she had already been running for weeks, a skill-building technique she had already stress-tested, a question about an edge case that unlocks a broader principle for everyone in the room.

She is one of the most frequent contributors of external resources to the group — tools, workflows, and links she has already evaluated before sharing — and one of the few members who has contributed a named technique that generated genuine excitement from Lou (the context-carryover protocol, described as “I need that yesterday”).

Sessions

2026-02-26_Mastermind — Subject of Lou’s live onboarding demo; raised a thoughtful edge case about whether pure-HTML pages (generated directly into GoHighLevel code blocks) would work with GEARS schema. Lou confirmed: the schema script goes in the header, not the page, so construction method is irrelevant.
2026-02-19_Mastermind — Offered to share her context-carryover protocol with the group — a system for reliably transferring context between AI conversation threads. Lou’s “I need that yesterday” reaction signalled this as a high-value contribution; the protocol surfaced genuine excitement across the group.
2026-02-05_Mastermind — Diagnosed and fixed her own skill-slop problem, demonstrating AI engineering depth that stood out even in a technically strong group. Lou later commented on her consistent capacity to surprise.
2026-01-29_Mastermind — Raised the framework evolution question that produced Lou’s temporal authority reframe: her hesitation about whether an evolving, not-yet-proven framework was appropriate to submit to GEARS prompted the insight that releasing a framework before it’s finished is itself an authority signal.
2026-01-22_Mastermind — Introduced E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) to the group — Google’s quality signal framework, directly relevant to AI engine evaluation criteria.
2026-01-15_Mastermind — Shared a rapid skill-building workflow: dump a set of documents into Claude, prompt it to use the skill-creator skill, and it encodes the documents as a reusable skill automatically. Significantly faster than writing skills manually; works especially well for existing SOPs. Also shared the Amy Yamada “How AI Recommends Experts” webinar replay link.
2026-01-08_Mastermind — Shared the session’s most operationally original contribution: an automated daily monitoring system (Perplexity queries, structured to test whether AI was citing her content on specific topics). Turned the vague aspiration of “getting cited by AI” into a measurable, repeatable feedback loop.
2025-12-12_Mastermind — Reported real-time workflow traction: Claude and Perplexity both pre-populated her ICH intake from memory, confirming AI memory as a meaningful workflow accelerator for returning users.
2025-12-05_Mastermind — Brought the session’s most technically rich case study: her family medical data project, which created a diagnostic discussion about matching AI architecture to data type (vector database vs. SQL vs. RAG). Lou’s conclusion: if queries are primarily numerical trends and time-series patterns, SQL is the right architecture — not a vector database.
2025-11-27_Mastermind — Discovery: Perplexity artifacts can be saved directly to Google Drive — a small but practically valuable workflow shortcut shared with the group.
2025-11-13_Mastermind — Shared the Qdrant file loading tutorial and n8n workflow templates library; both resources were relevant to current member projects.
2025-09-25_Mastermind — Shared Cluely (ambient AI assistant that reads your screen in real time as a live consultant).
2025-09-18_Mastermind — Referenced Comet browser (AI-native browser; sent invite to Ri Ca via Telegram); recommended Adobe Firefly as an alternative to other tools for image editing.
2025-09-04_Mastermind — Shared Coolify (open-source self-hosted deployment UI for Docker/app management).

Characteristic Contributions

GEO citation monitoring system — automated daily Perplexity queries structured to test whether AI was citing her content on specific topics. Built before anyone else in the group had operationalized GEO testing; turned a vague goal into a measurable feedback loop.
Document-to-skill workflow — dump existing documents (SOPs, reference materials) into Claude, invoke the skill-creator skill, receive a reusable skill encoding those documents automatically. Much faster than writing skills manually; generalizable to any knowledge base.
Context-carryover protocol — a system for reliably transferring conversation context between AI thread sessions. Lou’s immediate reaction (“I need that yesterday”) signals this as a widely-applicable operational technique. The protocol was offered but not yet fully surfaced in session; follow up for extraction.
Skill-slop diagnosis — identified and fixed her own case of unconstrained skill invocation producing unintended outputs; demonstrated a level of AI system-debugging sophistication that Lou explicitly noted as surprising.
E-E-A-T introduction — brought Google’s quality signal framework (Experience, Expertise, Authoritativeness, Trustworthiness) into the group’s GEO vocabulary; it became part of the shared authority-building vocabulary from that session forward.
Framework timing question — her hesitation about submitting an evolving framework to GEARS generated Lou’s insight about temporal activity as an authority signal: releasing a framework before it is finished is itself an act of authority, because it establishes the timestamp of your thinking.
Tool curation — consistent sharer of evaluated tools and resources: Coolify, Cluely, Adobe Firefly, n8n workflow templates, Qdrant tutorials, Amy Yamada’s webinar replay.

Insights They Are Quoted or Referenced In

Signature Quotes

“I need to see a URL — where did it get this information? If it cannot provide that — ditch it.” (referenced via Kasimir, January 15, 2026 — Elizabeth’s citation-demand heuristic, adapted and shared by Kasimir in multi-model synthesis discussion)

(On context-carryover protocol, February 19, 2026 — offered to share with the group; Lou’s reaction: “I need that yesterday.”)

PowerUp Coaching — Living Knowledge Base

Explorer