Relewise/relewise-agent-plugins / plugins/relewise/skills/relewise-administration
relewise-administration
VerifiedInspect Relewise Dataset Jobs and execution history. Use when a user wants to understand configured jobs, recent runs, failures, execution messages, or job settings. These operations are read-only; they do not run or change Jobs.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.9 KB |
| operations.json | config | 149 B |
SKILL.md
View on GitHub---
name: relewise-administration
metadata:
relewise-execution-skill: relewise-agent-gateway
description: Inspect Relewise Dataset Jobs and execution history. Use when a user wants to understand configured jobs, recent runs, failures, execution messages, or job settings. These operations are read-only; they do not run or change Jobs.
---
# Relewise Administration
Before any Agent Gateway call, activate and follow the installed `relewise-agent-gateway` skill from this plugin. Pass it the selected REST operation ID and/or MCP tool plus validated parameters; do not resolve the CLI, choose a transport, or handle authentication in this domain skill. Confirm the intended Dataset before making an Administration call and ensure its Agent Gateway Administration area is enabled.
## Inspect Jobs
1. Call `list_jobs` to discover the Dataset's Jobs and their stable Job IDs. Do not guess a Job ID.
2. Use `get_job` with a Job ID returned by `list_jobs` to inspect its schedule, type, state, and safe custom configuration.
3. Treat the returned execution summary as the latest available summary; it does not provide the full execution history.
4. Explain that these operations cannot create, start, stop, or modify Jobs.
## Inspect execution history
1. Use `list_job_logs` with an inclusive UTC date range. Filter by Job ID when the user asks about one Job; omit it to inspect all Jobs.
2. Use the returned cursors for pagination. Do not combine `beforeLogId` and `afterLogId`.
3. Use `get_job_log` with a Job ID and Log ID returned by `list_job_logs` to inspect the complete execution messages.
4. Distinguish `completed`, `completedWithWarnings`, and `faulted`. Do not infer a run outcome from a missing or nullable message.
State the Dataset, Job name/type/ID, execution dates, result, and relevant messages. Separate observed Job configuration and execution records from conclusions about data freshness or integration health.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |