Real Skill packageSource verifiedClawHub registry

tempo-api-mcp

Access Tempo time-tracking data via MCP. Use when the user asks about Tempo worklogs, plans, teams, accounts, or wants to log time, check resource allocations, or manage timesheet approvals. Triggers on phrases like "log my time in Tempo", "how many hours did I log this week", "check my team's worklogs", "what's the resource plan for this sprint", or any request involving Jira/Tempo time tracking. Requires tempo-api-mcp installed and the tempo server registered (see Setup below).

Identity and source

Publisher attributionchrischallregistry owner unverified by skillvetai
Functional categoryData, Spreadsheets & Analyticsautomatically inferred · 54% rule confidence
Package forminstruction bundle2 recorded files
Canonical sourceClawHub registryclawhub:chrischall:tempo-api-mcp
Open canonical source ↗

Platform declarations

These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.

OpenClawnative officialProvenance: registry distribution

Independent structural checks

These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.

Claude Codepasses structure
Checker 0.1.0 · agent-skills-2026-08-13+claude-code-docs-2026-08-13 · 9/2/2026.claude/skills/tempo-api-mcp

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenAI Codexpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+codex-docs-2026-08-13 · 9/2/2026.agents/skills/tempo-api-mcp

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenClawpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+openclaw-docs-2026-08-13 · 9/2/2026skills/tempo-api-mcp

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

Installation and inspection

This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.

clawhub install @chrischall/tempo-api-mcp
clawhub inspect @chrischall/tempo-api-mcp --version 2.4.0

Security evidence

SkillVetAI static result: no findings detected

This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.

Status
completed
Coverage
full text content
Files
2 / 2 inspected as text
Checked
9/2/2026, 4:32:29 AM
Scanner
0.1.3
Policy
1.0.3
2 inferred permission indicators
  • network access — automatically inferred
  • filesystem write — automatically inferred
4 dependency and API indicators
  • api: clawhub.ai
  • api: github.com
  • api: www.npmjs.com
  • api: www.tempo.io
External clawhub result: suspicious

This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.

Evidence checked
9/2/2026, 12:29:42 AM
Release binding
Matches this record
  • skillspector: suspicious
  • llm: suspicious

Recorded files

The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.

Package content hashsha256:1d1b758b7707ac40e224e682688010a22f6870e7e9810fd5b86b685f67ef9690
Show up to 2 recorded paths
  • skill-card.md
  • SKILL.md

Source changelog

- Added a new `tempo_healthcheck()` tool for checking connector health, credential validity, and diagnosing authentication issues. - Removed the redundant `skill-card.md` file. - No changes to other tools or workflows; all existing functionality is unchanged.

Release security diff

mediumCompared fixed releases 2.3.2 and 2.4.0; 0 finding and 1 permission indicators were added.

Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.

Permission escalation detected
Change reasons and limitations
  • permission surface changed
  • content hash changed

Observed release history

These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.

2.3.28/28/2026sha256:94fb8e0edb2b5921534a4304c08424dc90586165e2f86c3d323d39e54377b35a