Skills

A skill saves the instructions and format for work your team repeats: a review checklist, a testing log, or a coordination report. Run it in a conversation with the project documents you want to use. Custom skills can be available across your organization or limited to selected projects.

Running a skill

1. Open a conversation in the project you want to work on.
2. Type / and select a skill by name. The picker includes Specset's built-in skills and your team's available custom skills.
3. Add the scope for this run, such as the mechanical spec sections or a particular drawing set, then send your message. The agent follows the saved instructions and asks for any missing inputs.

Use source references to point to the exact documents, sheets, or records you mean. Creating a skill and running it are separate steps; saving instructions does not start a review.

Choose what the skill produces

The editor's Artifact → Type setting determines the result you review.

For a Checklist, define the categories, checks, and any custom columns. Enable issue creation lets the agent file issues from review findings and link them in an Issue column. Use this when you want a checklist and tracked follow-up; use Issues when filing issues is the main result.

Create a testing and inspection log

Managers and admins can create and edit skills within their permitted organization or projects. Open Org Settings → Skills or Project Settings → Skills, then choose New skill.

Create with AI opens the Skill Creator. Describe the sources, the result you need, and how to handle missing information. For example:

Create a Testing and inspection log skill. Scan the spec sections I select and create one row per testing or inspection requirement, with source citations. Include the requirement, responsible party, timing, and required record. Write “Not stated” where the specification doesn't provide a detail. Ask which sections to review before starting.

You can also start from Create a new skill in the chat skill picker. Review the resulting draft in the editor before publishing.

To build the same skill yourself, choose Create manually:

1. Enter Testing and inspection log as the Name, plus a short Description so teammates know when to use it. Put the directions above in Instructions, including the inputs to request and the rules for missing information.
2. Under Artifact, select Table. Set Scan coverage to Spec sections.
3. Use Add column for Responsible party, Timing, and Required record, using text columns for this example. The table already provides Field, Finding, and References for the requirement, its details, and supporting sources.
4. Select the Projects where the skill should appear, or use Enable for all projects if you have organization-level permission. Leave Published off and click Create to save a draft.

Pick the right sources

For Table and Issues skills, Scan coverage chooses the kind of material to review: Documents, Spec sections, Drawing sheets, or RFIs. You select the particular sources in the conversation when you run it. Agent planned lets the agent propose a work plan for your approval instead.

For Documents, Scan depth also controls how the agent reads each file. Targeted uses its outline and search to find relevant material; Every page reads throughout the selected documents and takes more work. Use it when a complete register needs a page-by-page pass.

Test before publishing

Managers and admins who can manage a draft can also select it in the skill picker. Start with a small, familiar sample so you can check both the coverage and the result.

1. Open a new project conversation, type /, and select Testing and inspection log.
2. Ask it to review one spec section, for example: “Run this on Section 03 30 00 only.” Confirm the source selection before expanding the scope.
3. Review the table alongside the conversation. Open its source citations and compare several rows with the specification. Check that distinct requirements have separate rows and missing details are marked clearly.
4. If the instructions need work, edit the skill, click Save, and test again in a new conversation. Correcting a result table does not change the skill's saved instructions.

Table and checklist results are saved as artifacts. Use the Artifacts library to return to a run, review its conversation, or export the table.

Publish and maintain a skill

Once the trial is ready, save your edits and turn on Published. The skill becomes available to members in its selected projects. Drafts remain visible only to people who can manage them; publishing does not grant access to additional project documents.

Refine the instructions as your process changes. New runs use the updated skill; existing results are not automatically rewritten. To make a separate version for another use, choose Clone from the skill card's menu. The copy starts as a draft.

Template document drafting

Attach a template to a skill so each run follows your team's format, or use Fill a Template for a one-off document or workbook.

• Word templates. The agent maps the document's structure and fills each section with cited project content, flagging anything that needs your input rather than inventing it.
• PDF templates. The template is converted to Word for filling. Check the resulting layout before sharing it, since pagination can change.
• Excel templates. Form fields and table rows are filled while your formulas, styles, dropdowns, and images stay exactly as you built them.
• Review and export. Filled document templates open in a read-only preview with Word/PDF downloads. Request revisions in the draft's own chat. Workbook templates export as Excel files.

See Generate documents from templates for preparation, drafting, review, and reuse.

Help when you want it

Most teams set up their first skills with us during onboarding, and we're happy to do the same for a new workflow any time. If a workflow needs more than a skill can express, we can build it fully custom.