Skills: reusable procedures

A skill describes how Era or an agent should do a job. Unlike a one-off request, it can be reused. Web: Skills. Desktop Agents & tools → Skills handles business skills; Settings → AI → Skills handles local engine skills.

Creation routes

Write it yourself supplies a name and steps. Create with AI drafts from your description. Upload a file extracts a procedure from a document. Filter template playbooks by category. Types Instruction / Code / Enrich cover written procedures, executable operations and adding information to data.

Open a skill to inspect name, description, scope, status and connections. Choose Personal / Workspace / Organization with suitable access. Scope does not grant unrestricted tools; app connections are separate requirements.

Lifecycle

Save, create a version, evaluate it with test cases and promote the right version. Versions are Draft / Live / Retired; promoting an older version rolls back. Details show run history and errors. Manage Pause / Resume, publication and Skill permissions. Put necessary secrets in secret fields, not instructions. Confirm deletion to remove a skill.

After a successful multi-step job, Era can propose a procedure with skill_save. A card contains name, short use description, working steps and evidence. Say “Save this method as a skill” and review the card. “Stop using this old method” can stop remembered use; it is distinct from version management.

Permissions and limits

AI/skill management and scope access are required; target records retain their own permissions during execution. Skills are not event triggers: attach one to an agent or call it from a workflow for automation. Local file skills need not be identical to shared workspace skill records.

Try “Prepare a quote-checking procedure: tax, delivery date, then customer address.” See agents, memory and approvals.

Practical start