agentsclimarketplace

Masheev automations

Skill masheev/skills/skills/masheev-automations

Official Agent Skills for integrating Masheev into your applications

Install
npx -y skills add masheev/skills --skill masheev-automations

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when building automation rules and workflows in Masheev. Covers triggers (conversation.created, message.created, SLA breach, time-based), conditions (equals, contains, greater_than), and actions (set status, assign, add labels, send responses, trigger AI, webhook calls, notifications). Also covers the workflow builder with AI invoke steps, action steps, conditional steps, and delay steps. Use this skill when someone asks to "automate conversations", "set up rules", "auto-assign", "auto-resolve", "trigger AI", or "build a workflow" in Masheev.

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.8 KB, as published. Nobody here has run it

Masheev Automations

Automations run server-side rules that react to events in Masheev. They consist of triggers, conditions, and actions.

Quick Start

import { apiClient } from "@masheev/client/server";

await apiClient.automations.create.mutate({
  name: "Auto-assign VIP contacts",
  trigger: "conversation.created",
  conditions: [
    { field: "contact.customAttributes.plan", operator: "equals", value: "enterprise" },
  ],
  actions: [
    { type: "set_priority", value: "high" },
    { type: "assign_to", assigneeType: "agent", assigneeId: "agt_..." },
    { type: "add_label", labelId: "label_vip" },
  ],
});

Triggers

TriggerWhen
conversation.createdNew conversation starts
conversation.updatedConversation status/priority/assignment changes
conversation.assignedConversation assigned to agent/AI
message.createdNew message in any conversation
sla.warningSLA warning threshold reached
sla.breachSLA breached
time.scheduleCron-based scheduled trigger

Conditions

OperatorDescriptionExample
equalsExact matchchannel equals "whatsapp"
not_equalsNot equalstatus not_equals "resolved"
containsString containscontent contains "urgent"
matchesRegex matchemail matches "@enterprise.com$"
greater_thanNumeric comparisonmessageCount greater_than 10
less_thanNumeric comparisonpriority less_than "high"
is_setField has a valueassigneeId is_set

Actions

ActionDescription
set_statusChange conversation status (open, pending, resolved)
set_prioritySet priority (low, medium, high, urgent)
assign_toAssign to agent, AI, or unassign
add_label / remove_labelTag management
send_canned_responseSend a pre-written message
send_templateSend a channel template (WhatsApp, email)
add_noteAdd internal note
snoozeSnooze conversation for a duration
trigger_aiHand to AI agent
stop_aiTake back from AI
webhookCall external URL (GET/POST with headers/payload)
notifySend notification (email, Slack, in-app)

Managing Automations

// List
const rules = await apiClient.automations.list.query({});

// Activate/deactivate
await apiClient.automations.activate.mutate({ id: "rule_...", active: false });

// View execution history
const runs = await apiClient.automations.listRuns.query({ automationId: "rule_..." });

// Pre-built templates
const templates = await apiClient.automations.listTemplates.query();

Workflow Builder

For complex multi-step automations, use the workflow builder (see masheev-workflows skill for client-side workflows). Server-side workflows support:

  • AI invoke steps — Generate text/objects with tools
  • Action steps — Execute platform skills
  • Conditional steps — Branch based on conversation state
  • Delay steps — Wait before next action

See references/templates.md for pre-built automation templates.

Gives 0 of the 12 instructions most automation workflows skills give

Counted across 745 of the 1,008 authors here whose files we hold, read 2026-08-06

  • write conventional commit messagesin 36 of 745, across 35 files
  • delete branches after mergein 30 of 745, across 21 files
  • make atomic commitsin 25 of 745, across 15 files
  • write minimal code to pass testsin 22 of 745, across 10 files
  • run tests before committingin 21 of 745, across 13 files
  • re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
  • use try-catch for error handlingin 20 of 745, across 6 files
  • write tests before implementationin 20 of 745, across 8 files
  • configure branch protection rulesin 19 of 745, across 5 files
  • explain the why in commit messagesin 19 of 745, across 9 files
  • refactor code while tests remain greenin 19 of 745, across 6 files
  • Interact with elements using refsin 19 of 745, across 11 files

Said here and by no other author read

  • create automations using triggers conditions and actions
  • activate or deactivate automations
  • query execution history
  • use pre-built templates
  • use the workflow builder for complex multi-step automations

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.