> 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/reviewing-and-publishing-skills-for-your-organization.md). # Reviewing and Publishing Skills for Your Organization #### Summary When Builders submit Skills for firm-wide use, those Skills appear in your Publisher panel under Pending Review. This guide walks you through the review workflow and explains what to check before approving a Skill for the whole organization. #### Why This is Important Every Skill you approve becomes part of your firm's institutional toolkit. Once published, any User in your organization can trigger it, in filings, in client-facing documents. That makes the Publisher's review the quality gate for firm-wide AI-assisted work. A thoughtful review process protects three things: **consistency** (approved Skills reflect the firm's actual standards), **quality** (only tested, well-written Skills reach production), and **trust** (users can rely on any Skill in the library without second-guessing it). Skipping this step, or rubber-stamping submissions, undermines all three. #### Who Can Review Skills Only **Publishers** can review and approve submitted Skills. Builders who submit a Skill can see its pending status but cannot approve their own submissions. If your firm doesn't have an active Publisher, submitted Skills will accumulate in the review queue with no one to action them, assign at least one Publisher before rolling out Skills to your team. #### Step-by-Step Guide **Step 1: Open the Pending Review Queue** 1. On the Vincent home page, click **Customize** in the top right. 2. Select the **Skills** tab. 3. Locate the **Pending Review** section. Any Skill submitted by a Builder appears here with the submitter's name, submission date, and the Skill's description. **Step 2: Open the Skill You Want to Review** Click into the Skill to see its full contents, description, activation conditions, instructions, sub-skills, and any attached assets. Take the time to read everything the Builder submitted. The description tells Vincent when to trigger the Skill, so an inaccurate description means the Skill will activate in the wrong situations even if the instructions themselves are excellent. **Step 3: Test the Skill Before Approving (Recommended)** Before publishing to the whole firm, test the Skill in your own conversation to confirm it behaves as expected. You can do this by opening the Skill and selecting **Try in conversation**, or by starting a new chat and triggering the Skill with a prompt that matches its conditions. This step is optional but strongly recommended for any Skill that will be used on client-facing work. **Step 4: Approve or Reject** Once you've reviewed and (ideally) tested the Skill: * **Approve** to publish the Skill to every User in your organization. It becomes immediately available in all users' Skills libraries. * **Reject with a note to the Builder** if the Skill needs changes. Write a specific, constructive note explaining what needs to change so the Builder can revise and resubmit. #### What to Check When Reviewing a Skill Use this checklist to review submissions consistently: * **Description accuracy:** Does the description correctly capture what the Skill does? Vincent uses this text to decide when to trigger the Skill, so vague or misleading descriptions cause misfires. * **Activation conditions:** Are the conditions specific enough that the Skill activates on the right prompts, and only on those prompts? Overly broad conditions cause the Skill to fire when it shouldn't. * **Instruction quality:** Are the instructions specific, unambiguous, and free of contradictions? Do they explicitly state what to do *and* what to avoid? * **Jurisdictional and factual accuracy:** Does the Skill reference the correct jurisdiction, applicable law, and firm standards? Flag anything that would produce output inconsistent with how your firm actually practices. * **Confidentiality and privilege:** Does the Skill avoid inappropriate handling of client information? Does it comply with your firm's ethics and confidentiality policies? * **Firm-wide relevance:** Is this Skill useful across the firm, or does it capture one lawyer's idiosyncratic workflow? Highly personal Skills are better kept as personal (Published · Just me) rather than firm-wide. * **Overlap with existing Skills:** Does an approved Skill already cover this task? If so, consider whether to merge, replace, or reject. {% hint style="info" %} **Set a regular review cadence.** Submitted Skills lose momentum if they sit in the queue for weeks. A short, standing slot on the Publisher's calendar — 30 minutes on Monday mornings, for example, clears the backlog and keeps Builders motivated to submit high-quality work. {% endhint %} #### Approving vs. Rejecting: Guidance * **Approve** when the Skill is accurate, specific, tested, and adds value across the firm. Minor stylistic preferences can be edited after approval, you have full editing rights over any Skill in the library. * **Reject** when the Skill has substantive issues: incorrect law, poorly scoped conditions, overlap with existing Skills, or content that's too personal to be firm-wide. Reject with a clear note so the Builder understands what to fix. * **Edit and approve** when the Skill is fundamentally sound but needs polish. Publishers can edit any Skill, so small refinements don't require a rejection round trip, approve and refine in place. #### Best Practices & Pro Tips * **Give constructive rejection notes.** "This isn't quite right" tells the Builder nothing. "The activation condition is too broad, it fires on any contract question, not just NDA drafts. Narrow it to prompts explicitly requesting an NDA and resubmit" tells them exactly what to do. Specific rejections lead to better resubmissions and stronger Skills over time. #### Related Articles * [Submitting a Skill for Organization-Wide Use](/vincent-by-vlex/vincent/skills/submitting-a-skill-for-organization-wide-use.md) * [Skills Roles and Permissions](/vincent-by-vlex/vincent/skills/skills-roles-and-permissions.md) * [Tips for Writing Effective Skills](/vincent-by-vlex/vincent/skills/tips-for-writing-effective-skills.md) * [Editing and Managing Your Skills](/vincent-by-vlex/vincent/skills/editing-and-managing-your-skills.md) ### Relevant Video Content {% embed url="" %} **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) |