AGENT SKILL

pm-tinyemail

TinyEmail connector knowledge and safe action guide.

License 许可
AGPL-3.0
所属仓库
polymetrics-ai/cli
最近更新
2026-09-21
Stars
★ 7
Forks
0

01 前言 Front Matter

name
pm-tinyemail
description
TinyEmail connector knowledge and safe action guide.

03 SKILL.md 正文

pm-tinyemail

Purpose

Reads subscribers, lists, and campaigns, and writes subscriber create/upsert actions, through the tinyEmail API.

Icon

Capabilities

  • check=true catalog=true read=true write=true query=false
  • Integration type: api

Authentication

  • Use pm credentials add with --from-env or --value-stdin for secret fields.

Configuration

  • base_url
  • api_key (secret) (required)

ETL Streams

  • subscribers:
    • primary key: id
    • fields: created_at(string), email(string), first_name(string), id(string), last_name(string), status(string)
  • lists:
    • primary key: id
    • fields: created_at(string), id(string), name(string), subscriber_count(string)
  • campaigns:
    • primary key: id
    • fields: created_at(string), id(string), name(string), status(string), subject(string)

Sync Modes

  • ETL sync modes: full_refresh_append, full_refresh_overwrite

Reverse ETL Actions

  • create_subscriber:
    • endpoint: POST /segment/customer
    • required fields: email
    • risk: creates or upserts a subscriber (customer) into the caller's tinyEmail account, optionally into a named audience segment; low-risk external mutation, no approval required

Security

  • read risk: external tinyEmail API read of subscriber, list, and campaign data
  • write risk: external tinyEmail API mutation: creates or upserts a subscriber (customer) record, optionally assigning it to a named audience segment
  • approval: reverse ETL plan approval required before writes
  • Never pass secret values in chat, shell arguments, logs, docs, or JSON output.

Commands

Inspect as a manual

pm connectors inspect tinyemail

Inspect as structured JSON

pm connectors inspect tinyemail --json

Agent Rules

  • Run pm connectors inspect tinyemail before creating credentials or plans.
  • Use --json only when the caller needs structured output; use the manual for human-readable guidance.
  • Never ask the user to paste secret values into chat.
  • For reverse ETL writes, create a plan, show the preview, wait for explicit approval, then run with the approval token.

04 同仓库更多 Skills