> For the complete documentation index, see [llms.txt](https://support.vlex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.vlex.com/vincent-by-vlex/vincent/skills/tips-for-writing-effective-skills.md).

# Tips for Writing Effective Skills

#### Summary

The difference between a Skill that Vincent uses reliably and one that misfires or produces uneven output comes down to how the Skill is written. This guide covers the four principles behind effective Skills, specificity, examples, explicit constraints, and iterative refinement plus ready-to-use prompts for litigation and transactional practice areas.

#### Why This is Important

You can create a Skill in five minutes, but a Skill that actually works well takes a little more thought. The good news: the principles are simple, and the practical difference between a basic Skill and a great one is often just a few extra sentences of precision. Once you internalize these patterns, every Skill you build will be sharper, and firm-wide submissions will get approved faster.

Great Skills also compound over time. As you refine a Skill and it produces reliable output, that reliability becomes part of your firm's institutional knowledge. Poor Skills produce inconsistent output that lawyers stop trusting, which defeats the whole purpose. Investing in Skill quality upfront pays back every time the Skill runs.

#### The Four Principles of Effective Skills

**1. Be Specific**

Vague instructions produce vague output. The single biggest lever for Skill quality is specificity, telling Vincent exactly what you want, not roughly what you want.

Compare these two versions of the same Skill:

* **Weak:** *"Draft professional emails."*
* **Strong:** *"Draft emails in plain language, use the client's first name, keep responses under 200 words, and always close with a clear next step and a proposed timeline."*

The strong version tells Vincent what "professional" actually means for your firm. The weak version leaves Vincent guessing, and Vincent guessing is where uneven output comes from.

Apply specificity to every dimension that matters: structure, tone, length, terminology, jurisdictional context, output format, and expected audience.

**2. Use Examples**

Nothing communicates what "good" looks like faster than an actual example. When Vincent has produced an output you like, capture that framework directly by saying:

> *"Remember this as a skill."*

Vincent will save the working framework as a Skill you can then refine in the editor. This is often the fastest path to a high-quality Skill, you're teaching Vincent from a real success, not from a hypothetical description.

You can also include examples inside a Skill's instructions. For example, in a demand letter Skill:

> *"Structure the letter as follows: (1) Opening paragraph naming parties and incident date; (2) Liability theory with supporting facts; (3) Damages summary with specific figures where available; (4) Settlement demand with a response deadline. Example opening: 'This firm represents \[client name] regarding injuries sustained on \[date] at \[location].'"*

The example inside the instruction removes ambiguity about tone and format in a way that description alone cannot.

**3. Include What to Avoid**

Great Skills often specify what *not* to do as clearly as what to do. Explicit prohibitions prevent common failure modes that description alone won't catch.

Examples:

* *"Do not include legal citations in client-facing summaries."*
* *"Avoid passive voice in demand letters."*
* *"Do not speculate about damages amounts without instruction from the user."*
* *"Never draft in first person plural ('we') when writing on behalf of an individual client."*
* *"Do not reference specific opposing parties by name in draft documents; use 'Opposing Counsel' as a placeholder."*

Explicit prohibitions are especially valuable when you've noticed a specific mistake Vincent makes repeatedly. Every recurring correction is a "do not" waiting to be added to the Skill.

**4. Start Simple, Refine Over Time**

Don't try to write a perfect Skill on the first pass. The most effective Skills are usually built iteratively:

1. **Write a rough first version** with the core instructions and one or two conditions.
2. **Run it on three or four realistic prompts** and see what Vincent produces.
3. **Note what needs adjustment,** output too long, missing a section, wrong tone, over-cautious.
4. **Refine the Skill** in the editor, adding specificity, examples, or prohibitions to address each issue.
5. **Test again.**

You can update a Skill at any time in the panel, or just tell Vincent mid-conversation what to change, see Editing and Managing Your Skills. Iterative refinement is faster than trying to anticipate every edge case upfront.

#### Ready-to-Use Prompts by Practice Area

If you want to try building a Skill but don't know where to start, copy any of these prompts into Vincent to trigger the guided setup. Each is designed to produce a working, useful Skill on first pass.

**Litigation**

| Task                              | Example Prompt                                                                                                                                            |
| --------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Build an Argument**             | *"Help me build a skill for building arguments in \[employment discrimination / personal injury / commercial litigation] cases under \[your state] law."* |
| **Draft a client update**         | *"Help me build a skill for drafting a client update after a motion ruling, in plain language, covering what happened, what it means, and what's next."*  |
| **Review a discovery production** | *"Help me build a skill for reviewing medical records in PI matters, extracting date of treatment, provider, diagnosis, treatment, and billed amount."*   |

**Transactional**

| Task                      | Example Prompt                                                                                                                                                             |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Summarize documents**   | *"Help me build a skill for reviewing \[commercial lease / vendor / SaaS] agreements against our standard clause checklist."*                                              |
| **Diligence extraction**  | *"Help me build a skill for diligence review that pulls parties, effective date, term, renewal, assignment and change-of-control, and governing law from each agreement."* |
| **Drafting in Legal Pad** | *"Help me build a skill for drafting NDAs following our firm's standard form and signature block."*                                                                        |

Adapt any prompt to your practice, swap in your actual jurisdictions, document types, or firm-specific terminology. The more concretely you frame the opening request, the fewer follow-up questions Vincent will ask.

For the full guided-setup walkthrough, see [Creating a Custom Skill.](/vincent-by-vlex/vincent/skills/creating-a-custom-skill.md)

#### Common Pitfalls to Avoid

A few patterns consistently produce Skills that underperform:

* **Scope creep.** A Skill that tries to handle every variant of a task ("all litigation drafting") ends up doing none of them well. Narrow the scope to a specific, well-defined task.
* **Overly abstract instructions.** *"Write clearly"* is not an instruction, Vincent has no way to convert it into behavior. Replace abstractions with concrete rules: sentence length, banned words, required sections.
* **Missing jurisdictional grounding.** A Skill that doesn't specify the applicable jurisdiction defaults to whatever Vincent guesses. Always name the jurisdiction (or explicitly say "the user will specify jurisdiction at runtime").
* **Contradictions inside instructions.** Two instructions that pull in opposite directions ("keep it under 200 words" and "cover all material terms in detail") force Vincent to compromise unpredictably. Reconcile contradictions before saving.
* **No test cycle.** Skills you never test drift silently. Run every Skill on realistic prompts before relying on it for real work.

#### Best Practices & Pro Tips

* **Turn every correction into a Skill improvement.** When you find yourself telling Vincent the same correction more than twice in different conversations, "shorter," "no citations in emails to clients," "always include a subject line" that's the signal. Open the relevant Skill and encode the correction directly. The goal is to stop repeating yourself.
* **Write Skills as if for a smart new associate.** The mental model that produces the best Skills is this: imagine you're briefing a bright associate who just joined the firm. They're capable, but they don't yet know your house style, your preferred structure, or the things you've learned not to do. Everything you'd tell them belongs in the Skill.

#### Related Articles

* [Creating a Custom Skill](/vincent-by-vlex/vincent/skills/creating-a-custom-skill.md)
* [Editing and Managing Your Skills](/vincent-by-vlex/vincent/skills/editing-and-managing-your-skills.md)
* [Submitting a Skill for Organization-Wide Use](/vincent-by-vlex/vincent/skills/submitting-a-skill-for-organization-wide-use.md)
* [What are Skills in Vincent?](/vincent-by-vlex/vincent/skills/what-are-skills-in-vincent.md)

**What's Your Next Step?**

| **New to Vincent?**                                                                                                                                                                                        | **Already a Vincent Customer?**                                                                                                                            |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [See how Vincent can transform your practice. **Request a personalized demo**.](https://vlex.com/book-a-demo?utm_source=website\&utm_medium=organic\&utm_campaign=web_trial_homepage\&campaign_id=4270741) | [If you still have questions or need help with a specific feature, our team is here to assist. **Contact our Support team**.](https://vlex.com/contact-us) |