Skills
Create and edit reusable procedures, scope them to channels and attach them to routines.
Procedures OpenTag can reuse
A skill describes how to do a kind of work. “Sam owns billing” is a fact; “check the CRM before drafting a customer email” is a procedure.
OpenTag includes skills for common work and integrations. Your team can create its own skills and edit them in Skills at app.tryopentag.com.
Create or edit a skill
Describe the repeatable steps and the output:
@OpenTag make a skill for our weekly pipeline report: show totals first, compare with last week, then list deals missing a next step. Include links to the deal records.
Review the saved instructions and correct anything that should not apply every time. The Skills page lets you create and edit the skill directly and inspect required connections or credentials.
A useful skill says what to do with an exception. “If the account owner is missing, flag the record instead of assigning someone” is more useful than “be careful”.
Choose where it applies
Skills can be tied to the channels where they belong. Use channel bindings for team-specific procedures instead of assuming every skill should apply to every conversation.
You can also attach relevant skills to a routine. When a job uses an unexpected format, check its routine instructions and applicable skills before rewriting the request.
Review improvements
OpenTag can propose changes to user skills from work outcomes. Review the proposed edit before accepting it. A suggestion is not evidence that the skill has already changed.
Permissions still apply
A skill does not grant access to a disconnected app or remove a connection's read-only restriction. Skill scripts that explicitly declare human approval require it.
A sentence in ordinary instructions is not a replacement for tool permissions. For a firm limit on changes, choose Read only on the connection. See Approvals.