AGENT SKILL

pm-tempo

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

02 资源文件 1

03 SKILL.md 正文

pm-tempo

Purpose

Reads Tempo accounts, customers, worklogs, and workload schemes through the Tempo Cloud REST API v4.

Icon

  • id: tempo
  • asset: icons/tempo.svg
  • source: upstream_registry
  • review_status: upstream_seeded
  • review_url: https://apidocs.tempo.io/

Capabilities

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

Authentication

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

Configuration

  • base_url
  • max_pages
  • mode
  • page_size
  • api_token (secret) (required)

ETL Streams

  • accounts:
    • primary key: id
    • fields: global(boolean), id(integer), key(string), monthly_budget(number), name(string), status(string)
  • customers:
    • primary key: id
    • fields: id(integer), key(string), name(string)
  • worklogs:
    • primary key: tempo_worklog_id
    • cursor: updated_at
    • fields: billable_seconds(integer), created_at(string), description(string), issue_id(integer), jira_worklog_id(integer), start_date(string), start_time(string), tempo_worklog_id(integer), time_spent_seconds(integer), updated_at(string)
  • workload_schemes:
    • primary key: id
    • fields: default_scheme(boolean), description(string), id(integer), name(string)

Sync Modes

  • ETL sync modes: full_refresh_append, full_refresh_overwrite, full_refresh_overwrite_deduped

Security

  • read risk: external Tempo Cloud API read of account, customer, and worklog data
  • approval: none; read-only
  • Never pass secret values in chat, shell arguments, logs, docs, or JSON output.

Commands

Inspect as a manual

pm connectors inspect tempo

Inspect as structured JSON

pm connectors inspect tempo --json

Agent Rules

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

04 同仓库更多 Skills