AGENT SKILL

pm-bitly

Bitly 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-bitly
description
Bitly connector knowledge and safe action guide.

03 SKILL.md 正文

pm-bitly

Purpose

Reads Bitly organizations, groups, campaigns, channels, bitlinks, branded short domains, webhooks, QR codes, and group tags, and writes bitlink/campaign/group/channel/webhook/custom-bitlink/QR-code mutations, through the Bitly v4 REST API.

Icon

  • id: simple-icons-bitly
  • asset: icons/simple-icons/bitly.svg
  • title: Bitly
  • simple_icon_slug: bitly
  • simple_icon_hex: EE6123
  • source: simple-icons
  • license: CC0-1.0
  • review_status: cc0_with_trademark_caveat
  • review_url: https://simpleicons.org/?q=Bitly
  • match: exact-name-or-slug
  • matched_by: bitly

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
  • group_guid
  • api_key (secret) (required)

ETL Streams

  • organizations:
    • primary key: guid
    • fields: created(string), guid(string), is_active(boolean), modified(string), name(string), role(string), tier(string), tier_display_name(string), tier_family(string)
  • groups:
    • primary key: guid
    • fields: bsds(array), created(string), guid(string), is_active(boolean), modified(string), name(string), organization_guid(string), role(string)
  • campaigns:
    • primary key: guid
    • fields: channel_guids(array), created(string), description(string), group_guid(string), guid(string), modified(string), name(string)
  • channels:
    • primary key: guid
    • fields: bitlinks(array), campaign_guid(string), created(string), group_guid(string), guid(string), modified(string), name(string)
  • bsds:
    • primary key: account
    • fields: account(string), bsds(array)
  • webhooks:
    • primary key: guid
    • fields: campaign_guid(string), client_id(string), created(string), event(string), group_guid(string), guid(string), is_active(boolean), modified(string), updated_by(string), url(string)
  • qr_codes:
    • primary key: qrcode_id
    • fields: archived(boolean), bitlink_id(string), created(string), created_by(string), destination(object), expiration_at(string), group_guid(string), is_customized(boolean), modified(string), qr_code_type(string), qrcode_id(string), tags(array), title(string)
  • group_tags:
    • primary key: group_guid
    • fields: group_guid(string), tags(array)
  • bitlinks:
    • primary key: id
    • fields: archived(boolean), created_at(string), deeplinks(array), id(string), link(string), long_url(string), references(object), tags(array), title(string)

Sync Modes

  • ETL sync modes: full_refresh_append, full_refresh_overwrite

Reverse ETL Actions

  • create_bitlink:
    • endpoint: POST /bitlinks
    • required fields: long_url
    • risk: creates a new publicly-resolvable short link; low-risk external mutation, no approval required
  • update_bitlink:
    • endpoint: PATCH /bitlinks/{{ record.id }}
    • required fields: id
    • risk: mutates an existing bitlink's metadata or redirect destination; changing long_url redirects all future traffic on that short link and consumes an encode-limit unit
  • delete_bitlink:
    • endpoint: DELETE /bitlinks/{{ record.id }}
    • required fields: id
    • risk: permanently removes a bitlink; any traffic still hitting the short URL starts failing to resolve
  • update_bitlink_tags:
    • endpoint: PATCH /bitlinks/{{ record.id }}/tags
    • required fields: id, tags
    • risk: replaces the full tag set on a bitlink; overwrites any tags not included in the submitted list
  • delete_bitlink_tags:
    • endpoint: DELETE /bitlinks/{{ record.id }}/tags
    • required fields: id, tags
    • risk: removes the named tags from a bitlink; irreversible without re-adding them via update_bitlink_tags
  • create_campaign:
    • endpoint: POST /campaigns
    • required fields: group_guid
    • risk: creates a new campaign container in the target group; low-risk external mutation, no approval required
  • update_campaign:
    • endpoint: PATCH /campaigns/{{ record.guid }}
    • required fields: guid
    • risk: mutates an existing campaign's name, description, or associated channels
  • update_group:
    • endpoint: PATCH /groups/{{ record.guid }}
    • required fields: guid
    • risk: renames or re-parents an existing group; a visible change for every member of that group
  • update_group_preferences:
    • endpoint: PATCH /groups/{{ record.group_guid }}/preferences
    • required fields: group_guid, domain_preference
    • risk: changes the default branded short domain new bitlinks in this group are created with
  • create_channel:
    • endpoint: POST /channels
    • risk: creates a new channel container; low-risk external mutation, no approval required
  • update_channel:
    • endpoint: PATCH /channels/{{ record.guid }}
    • required fields: guid
    • risk: mutates an existing channel's name or campaign association
  • create_webhook:
    • endpoint: POST /webhooks
    • required fields: group_guid, event, url
    • risk: registers a new outbound webhook that will POST live event data (clicks/scans) to an external URL of the caller's choosing; verify the target endpoint before enabling
  • update_webhook:
    • endpoint: PATCH /webhooks/{{ record.guid }}
    • required fields: guid
    • risk: mutates an existing webhook's target URL, event type, or active state; a changed url redirects future event deliveries to a different endpoint
  • delete_webhook:
    • endpoint: DELETE /webhooks/{{ record.guid }}
    • required fields: guid
    • risk: permanently removes a webhook subscription; event delivery to its target URL stops immediately
  • create_custom_bitlink:
    • endpoint: POST /custom_bitlinks
    • required fields: custom_bitlink, bitlink_id
    • risk: claims a custom keyword/back-half on a branded short domain and points it at a bitlink; consumes a finite custom-bitlink allocation on the domain
  • update_custom_bitlink:
    • endpoint: PATCH /custom_bitlinks/{{ record.custom_bitlink }}
    • required fields: custom_bitlink, bitlink_id
    • risk: re-points an existing custom keyword at a different bitlink; redirects all future traffic hitting that custom URL to the new destination
  • create_qr_code:
    • endpoint: POST /qr-codes
    • required fields: group_guid, destination
    • risk: creates a new QR code resource pointed at a bitlink or long_url; low-risk external mutation, no approval required
  • update_qr_code:
    • endpoint: PATCH /qr-codes/{{ record.qrcode_id }}
    • required fields: qrcode_id
    • risk: mutates an existing QR code's title or destination; changing destination redirects anyone scanning an already-printed/distributed code
  • delete_qr_code:
    • endpoint: DELETE /qr-codes/{{ record.qrcode_id }}
    • required fields: qrcode_id
    • risk: permanently removes a QR code resource; any already-printed/distributed copy of the code stops resolving

Security

  • read risk: external Bitly API read of organization, group, campaign, channel, bitlink, branded-short-domain, webhook, QR code, and tag data
  • write risk: external mutation of bitlinks, campaigns, groups, channels, webhooks, custom bitlinks, and QR codes; create_webhook/update_webhook register or repoint an outbound event delivery URL of the caller's choosing and warrant review before use, every write ships with an explicit per-action risk string
  • approval: required for destructive actions (delete_bitlink, delete_webhook, delete_qr_code, delete_bitlink_tags) and for webhook URL mutations; creates/updates of bitlinks, campaigns, channels, and QR codes are low-risk
  • Never pass secret values in chat, shell arguments, logs, docs, or JSON output.

Commands

Inspect as a manual

pm connectors inspect bitly

Inspect as structured JSON

pm connectors inspect bitly --json

Agent Rules

  • Run pm connectors inspect bitly 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