Use Client Examples Without Exposing the Client

When a skill needs an example, start with the decision it should teach. Build a new fictional case that contains the necessary constraints, choices, and unknowns. Label it as fictional. If you want to use actual client material instead, establish permission and review the disclosure risk before putting it into the skill or an AI service.

Changing a name to “Client A” is not a reliable anonymity test. A combination of dates, places, roles, unusual events, and distinctive numbers can still make a person or organization recognizable. The ICO’s guidance explicitly warns against focusing only on obvious identifiers. ICO guidance on effective anonymisation.

This resource offers a fictional demonstration and a review checklist. It does not determine whether a real client disclosure complies with a contract or law, and the checklist cannot certify anonymity.

An established author may have years of useful experience but little material they can freely publish. That is a real constraint, not a reason to invent a successful client engagement.

In a consulting discussion, u/Ok-Pear2215 described the difficulty:

“I have experience in them, but I can’t show it.”

The writer said relevant work was covered by confidentiality agreements and asked whether toy examples would help. Their experience supports the need for an alternative demonstration; the replies do not establish what any particular agreement permits. Original consulting discussion.

A fictional case can show how your method handles a realistic problem. It cannot demonstrate that a client achieved a result. Keep those two purposes separate in the skill, sales page, and supporting examples.

Write down the reasoning you need to demonstrate before inventing the setting. If the lesson is about resolving competing constraints, the example needs constraints that actually conflict. If the lesson is about uncertainty, leave something important unknown. Do not create a case where every detail makes the answer obvious.

Then choose fresh details that do not trace a particular client. Avoid starting with a confidential document and asking an unapproved AI tool to anonymize it: that would disclose the material before the proposed protection occurs.

For an author who teaches service design, the necessary lesson might be distinguishing a customer preference from an operational requirement. The example needs both kinds of input and a choice between them. It does not need a real customer’s name, internal revenue, or a screenshot of their system.

The following case is invented for instruction. It is not a disguised client, a composite of interviews, or a reported result.

Situation: The fictional Alder Repair Library lends household repair tools. Its coordinator wants to improve collection instructions. Visitors say they want a quicker handover. Volunteers need the correct item and reservation reference before releasing a tool. Some visitors arrive without their reference; the existing message puts that requirement after several paragraphs about the organization.

Constraints: The team can revise its confirmation message this week. It cannot change the booking software. Volunteers should not be asked to improvise a new identity-checking process. The author’s method in this example is to separate the desired outcome, the operational requirement, and the change within the team’s control.

The example ends with a proposed check. It does not claim the change reduced delays, increased satisfaction, or passed a real test. An illustrative output might be a revised message outline: what to bring, where and when to collect, what to do if a reference is missing, then background information.

That is enough to demonstrate the method’s sequence without fabricated business results. If your skill invents a percentage improvement, the example has become misleading rather than more persuasive.

When reviewing material for a demonstration, use this checklist to identify questions for the appropriate owner or reviewer. It applies to supporting files and screenshots as well as the main text.

These checks flag risk; they do not produce a legal clearance. If the example depends on real restricted material, involve the person responsible for approving its use.

“Fictional” should mean you invented the case. “Composite” means you combined elements from more than one source and may still need to review what those elements reveal. “Anonymized” makes a stronger claim than “names changed.” Use the term your process can justify.

The ICO distinguishes anonymisation from pseudonymisation and explains that retaining a way to identify people matters. Its guidance is UK-specific and currently marked as under review; it should not be treated as a blanket conclusion about your example. ICO introduction to anonymisation.

Before publishing, ask another reviewer what the case teaches, whether the fictional status is unmistakable, and whether any unnecessary real-world clues remain. That is an editorial check, not a claim that a re-identification test has been completed.

Use how to write an agent skill to connect the example to the method’s actual instructions. To discuss an author skill with a clear, usable demonstration, visit Skillfully and choose Book onboarding. Bring the fictional case and the specific decision it is designed to teach.