> For the complete documentation index, see [llms.txt](https://help.jurisphere.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.jurisphere.ai/jurisphere-word-add-in/core-features/ask-juris/skills-in-the-word-add-in.md). # Skills in the Word Add-In How to use the pre-built skill available in the Word Add-In ## Overview A Skill is a pre-built, one click legal workflow, written and approved by expert lawyers for a specific, repeatable task. You can run it against your open document with a single selection, instead of writing out an instruction yourself. #### What a Skill actually is Think of a Skill as the difference between writing your own search query from scratch every time, versus clicking a saved filter that an expert lawyer built once and got right. Every Skill: * Runs against your currently open document. Either the [**Whole Document**](#set-your-scope) or whatever you've highlighted ([**Selection Only**](#set-your-scope)), exactly like a typed instruction. * Requires **no prompt of your own**. You ccan select it from a list rather than describing what you want. * Returns a **structured response in the panel**, the same conversational surface you'd see for any other query, so you review its findings the same way you'd review an answer or a suggested edit. * Was **built and approved by expert lawyers** for a specific, repeatable task, rather than generated freehand for your one off situation. {% hint style="success" %} Skills exist on the Jurisphere web platform too, in greater number. You can find more information about [available skills](/ask-juris/skills.md) and how to [create your own custom skill](/workflows/creating-custom-skills.md) here. {% endhint %} *** ### Skills available The most popular Skill is Proofreading and Finalization Check. If you only try one Skill this week, this is the one worth starting with. **What the proofreading and finalization skill checks for:** * Grammar, spelling and punctuation issues. * Inconsistent formatting, such as mismatched fonts, spacing, numbering styles or capitalization of defined terms. * Placeholder text left behind (`[INSERT]`, `[TBD]`, `[●]`, or similar) that shouldn't make it into a final version. * General finalization readiness. The kind of pass a senior associate does before a document goes out the door. **Try selecting it when:** > You've finished negotiating a document and want a last check before sending it out, filing it or sharing it with a client. The same instinct as a final read through, but faster and more consistent. **What comes back:** A structured list of flagged issues in the panel, each with a short description of the problem and an inline citation back to its exact location in your document, so you can jump straight to it, the same way you would with any other Ask Juris response. *** ### Running a Skill {% stepper %} {% step %} ### Set your scope Choose **Whole Document** for a full document sweep or highlight the specific section you want checked and choose **Selection Only**. For example, running **Cross-Reference Checker** on just the schedule you've been editing, rather than the whole agreement. {% endstep %} {% step %} ### Select a Skill from the list Skills appear below the text field in the panel, each with a short description and one or more tags (for example, "Drafting" or "Review agreements") indicating what kind of task it's built for. Click one directly, there's no need to type anything into the text field first. {% endstep %} {% step %} ### Review the output The Skill runs against your document and returns its findings in the panel, in the same conversational format as any other Ask Juris response, with inline citations included. Click a citation to jump straight to that spot in your document and verify it, exactly as you would with a review answer or a suggested edit. {% endstep %} {% endstepper %} *** ### Following up on a Skill's output A Skill's findings land in the same conversation thread as everything else in the Add-In, so you can build on them exactly the way you would build on an answer or a suggested edit, no need to start over. **Try asking, after running Proofreading and Finalization Check:** > "Group these by severity. Which of these are just typographical errors versus something that actually changes the meaning of a clause?" **Try asking, after running Defined Term Checker:** > "Draft a definition for every term this flagged as used but undefined, using standard market language." **Try asking, after running Cross-Reference Checker:** > "Fix the three broken cross-references you just found, updating each to point to the correct current section number." *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.jurisphere.ai/jurisphere-word-add-in/core-features/ask-juris/skills-in-the-word-add-in.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.