Public reading view · SmartAItomation

LinkedIn posting schedule

47 posts in the queue. The posting plan has one slot every day at 11:30 Europe/Chisinau. Only posts you schedule receive dates; the other version of a scheduled hook is an Alternative.

This is a manual publishing queue. Copying or marking done does not publish to LinkedIn.

View-only on this device. Scheduling, Done and improvements need the private editing link opened on this phone. Unlock editing

6/47marked done

Editorial score estimates draft readiness from length, example, verification step, team lesson and question. Edit it after review. “Improved” means the draft text was revised.

Hook 6

The agent called the right tool with the wrong customer ID.

Hook details

Hook 6 · Version A · Problem-Example-Solution (labeled example)

The agent called the right tool with the wrong customer ID.

Score 95/100Scheduled
Show postHide post
The agent called the right tool with the wrong customer ID. Tool selection is only one part of a safe agent action. The arguments and the authority to use them matter just as much. Hypothetical example: Request: “Show me the latest invoice for my account.” Tool: get_invoice — the correct function. Argument: customer_id = a different account copied from earlier context. Result: The tool returns an invoice the requester should not see. Failure: The agent supplied a plausible but unauthorized identifier. Solution: Bind the account identifier to the authenticated session on the server. Do not let the model choose it from conversational text. Check authorization before the tool runs, and record the rejected call for review. An evaluation should inspect the proposed tool, its arguments, the authorization decision and the final answer separately. A correct-looking response cannot make an invalid call acceptable. The skill is not teaching an agent every tool name. It is teaching the team where to put deterministic controls and how to test them. Server-side authorization stops an invalid call; evals are the most important way to keep checking that boundary. Engineers need training to write adversarial cases, inspect tool arguments and count a safe rejection as success. Those skills transfer to every later agent with account-scoped actions. Comment “ACCESS” if you want the short guide to testing agent tool authorization. P.S. We'll start sending it once at least 10 people ask for it here. P.P.S. Connect with me so I can send it by DM after that.
Unlock to schedule Unlock to mark done

Copy post includes bold formatting when the destination supports it. Copy with bold letters uses special Unicode characters; they may be less accessible to screen readers.

Hook 40

We helped a UK startup team improve its reported RAG accuracy from 65% to 96% after a two-day workshop.

Hook details

Hook 40 · Version A · Problem-Example-Solution (scoped client story)

We helped a UK startup team improve its reported RAG accuracy from 65% to 96% after a two-day workshop.

Score 90/100Scheduled
Show postHide post
We helped a UK startup team improve its reported RAG accuracy from 65% to 96% after a two-day workshop. The startup had spent a year developing an email-answering system for an oilfield production company. This is one owner-supplied engagement result, not a typical outcome or a guarantee. The available case notes do not define the metric or establish which technical change caused the improvement. The transferable lesson is a check your team can run before its next RAG change: Input: A representative question and the source material needed to answer it. Failure: The answer is wrong or unsupported. Diagnosis: Did retrieval find the right source? Did the answer use it faithfully? Did it cover the user's full request? Verification: Compare a focused change against the same labeled cases and inspect regressions. Keep retrieval coverage separate from answer quality. When an LLM judge is involved, test its decisions against expert-reviewed failures before using its score as evidence. The aim of coaching is a method your engineers can repeat across projects, not a promise to reproduce one client's number. For production RAG, evals are the most important transferable capability. Coaching engineers to define cases, inspect retrieval and test the judge gives them a method for the next product. One reported client improvement is useful context, not a guarantee that another team will reach it. Comment “RAG” if you want the short guide to separating retrieval from answer quality. P.S. We'll start sending it once at least 10 people ask for it here. P.P.S. Connect with me so I can send it by DM after that.
Unlock to schedule Unlock to mark done

Copy post includes bold formatting when the destination supports it. Copy with bold letters uses special Unicode characters; they may be less accessible to screen readers.