What are skills?
Skills allow digital workers to use the systems your business already relies on. PAIR can connect to software through APIs, approved tools and controlled workflows, so digital workers can complete real tasks rather than just provide advice.
Skill
Paperclip Organization helps PAIR agents classify attachments, organize files, check supporting documents, summarize PDFs, and connect documents to Odoo, CRM, finance, project, or service records.
View
Best for ERP, documents, and multi-system relationships.
Pattern
A matrix breaks dense content into readable capability blocks.
PAIR + Attachment classification
The visual shows documents flowing from intake to classification, review, and handover-ready output.
document intake board
Skill control
PAIR turns loose files into structured work that a team can trust.
Source 1
PDFs, attachments, folders
PAIR layer
PAIR document organizer
Source 3
Review packs and missing-item checks
Attachments, PDFs, contracts, photos, estimates, and handover folders are collected.
PAIR classifies files, summarizes folders, flags missing documents, and prepares review packs.
Sensitive documents and external sharing remain governed by review rules.
Final files can be linked to projects, customers, roles, and handover memory.
Attachment classification
A lot of business work gets stuck because supporting documents are missing, misnamed, attached to the wrong email, or stored in the wrong place. The Paperclip Organization skill helps PAIR agents manage the messy document layer around real operations. This skill is about invoices, contracts, photos, estimates, PDFs, receipts, signed documents, onboarding files, and handover packs.
File organization
PAIR can identify attachments in emails or workflow records, classify files by customer, project, supplier, invoice, or job, check whether required supporting documents are present, prepare folder structures for review, summarize attached PDFs or documents, and connect attachments to Odoo, CRM, finance, project, or service records.
PDF summaries
A finance user can ask whether all supporting documents are present for a set of invoices. A project manager can ask PAIR to organize client handover files and report what is missing. A service team can ask the agent to find photos, signed forms, and PDFs attached to a job.
Document handoff
PAIR can organize, classify, and prepare files, but deletion, sharing, or final record updates should require permission. Document access should follow role and department rules. The implementation can define who can read attachments, who can move files, and which folders or records require explicit review.
Example scenario
Read
Approved records, files, messages, documents, or system context.
Prepare
A summary, draft, task, script, update, recommendation, or exception note.
Route
External messages, sensitive records, financial changes, and risky actions move through review.
Remember
The completed outcome can become part of department knowledge and handover memory.
CONTROLLED BY DESIGN
PAIR can be configured so each skill has a defined level of access. Your team can see what the digital worker can read, what it can prepare, what needs review, and what can only run after approval.
Search approved systems and summarize useful context.
Draft messages, updates, notes, reports, and next steps.
Route sensitive communication or record changes to people.
Run only the workflows the company explicitly approves.
