Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

loggifly

Étoiles0

Forks0

Mis à jour23 mai 2026 à 06:59

Lab's Loggifly integration — Docker container log alerting via keyword/regex patterns. Use when the user wants to manage their Loggifly instance, or invokes `lab loggifly` / `mcp__lab__loggifly`. Calls the MCP tool first, falls back to the CLI if MCP is unavailable.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

jmagar

jmagar/.agents

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

6 fichiers

SKILL.md

readonly

name	loggifly
description	Lab's Loggifly integration — Docker container log alerting via keyword/regex patterns. Use when the user wants to manage their Loggifly instance, or invokes `lab loggifly` / `mcp__lab__loggifly`. Calls the MCP tool first, falls back to the CLI if MCP is unavailable.

Loggifly

Docker container log alerting via keyword/regex patterns. Exposes 3 actions via the lab homelab control plane.

How to call it

Prefer the MCP tool. Fall back to the CLI only when MCP is unavailable.

MCP (preferred)

One tool: mcp__lab__loggifly. Dispatch shape: { "action": "<name>", "params": {...} }.

Discover actions live:

{ "action": "help" }
{ "action": "schema", "params": { "action": "<name>" } }

Full action catalog: references/mcp.md.

CLI fallback

lab loggifly --help
lab loggifly <action> --help
labby --json loggifly <action> ...

CLI mirrors MCP actions; dots become dashes (server.health → server-health). Full CLI surface: references/cli.md.

Highlights

contract.status — Get LoggiFly contract/API status
health.status — Check LoggiFly health
config.summary — Get active configuration summary

Configuration

Credentials and base URLs live in ~/.lab/.env. Onboard / re-extract with labby extract scan and labby extract apply. Verify connectivity:

labby doctor service loggifly

When NOT to use this skill

The user is asking about a different lab service — load that service's skill instead.
The user is asking about lab itself (CLI internals, install, gateway, doctor across all services) — that's operator-tier, not loggifly-specific.

Plus depuis ce dépôt

même dépôt

android-app-testing

jmagar/.agents

Use when the user wants to live-test an Android APK end-to-end on an emulator/device and get a works/doesn't-work + UI/UX report — driving the real app, not writing test code. Triggers: "test my Android app", "QA this APK", "run the app on the emulator and tell me what breaks", "click through every screen", "review the app's UX", "does my APK work", "test the built APK". Installs/launches the APK, enumerates screens from the accessibility tree, exercises each feature via adb (tap/type/swipe/launch), watches logcat for crashes/ANRs, captures screenshots + UI dumps, and emits a structured report. Primary path is direct local adb; optional richer path via claude-in-mobile. Sibling of web-app-testing and desktop-app-testing (shared report format). Does NOT fire for: building/coding an Android app (use claude-android-ninja / jetpack-compose-expert), iOS, or unit tests.

2026-05-300

desktop-app-testing

jmagar/.agents

Use when the user wants to live-test a built Windows desktop application (.exe) end-to-end inside the agent-os Windows 11 VM and get a works/doesn't-work + UI/UX report — launching the real binary and driving it, not writing test code. Triggers: "test my Windows app", "QA this .exe", "run my desktop build on agent-os and tell me what breaks", "click through the app", "review the desktop app's UX", "does my exe work", "test the built binary in the Windows VM". Gets the .exe into the VM, launches it, enumerates controls from the UI Automation tree, drives every feature (click/type by element), watches for crashes/hangs/error dialogs, captures screenshots + control-tree dumps, and emits a structured report. Drives the agent-os VM via the Windows-MCP gateway. Sibling of web-app-testing and android-app-testing (shared report format). Does NOT fire for: building/coding a desktop app, the user's personal Windows on steamy (use nircmd), or general agent-os VM driving (use agent-os).

2026-05-300

web-app-testing

jmagar/.agents

Use when the user wants to live-test a WEB app/site end-to-end in a real browser and get a works/doesn't-work + UI/UX report — not just write Playwright code. Triggers: "test my web app", "QA this site", "run E2E on the web app", "click through every feature and tell me what breaks", "review the UX of this web app", "does my web app work", "test the deployed site". Drives a real Chrome via Playwright over CDP (default http://127.0.0.1:9222), enumerates features from the DOM/ARIA tree, exercises each, captures screenshots + console/page/network errors, and emits a structured report. Sibling of android-app-testing and desktop-app-testing (shared report format). Does NOT fire for: writing a one-off Playwright script (use webwright), pure web design/build with no testing, or backend/API-only testing.

2026-05-300

broadcastr

jmagar/.agents

Read or interact with the broadcastr activity feed across concurrent Claude sessions. Use when the user says "what are other agents doing", "show recent activity", "mute plan-exec notifications", "what's on the bus", "broadcastr status", "tail broadcastr", "emit a manual broadcastr event", or asks why a notification appeared. Also use to disable broadcastr in the current session (BROADCASTR_DISABLED=1) or check the global feed. Does NOT fire on generic "show me activity" or "what's happening" unless broadcastr is explicitly named.

2026-05-270

work-it

jmagar/.agents

Use when the user asks to "work it", execute a superpowers executing-plans document in a worktree, create a PR as soon as the implemented plan is green, or run a complete review-and-fix loop over all touched files.

2026-05-260

yt-dlp

jmagar/.agents

Use when the user asks to download, archive, search, inspect, or organize media with yt-dlp, MeTube, YouTube, playlists, channels, supported video sites, audio extraction, metadata, thumbnails, subtitles, Plex yt-dlp libraries, or NAS media downloads.

2026-05-260

name	loggifly
description	Lab's Loggifly integration — Docker container log alerting via keyword/regex patterns. Use when the user wants to manage their Loggifly instance, or invokes `lab loggifly` / `mcp__lab__loggifly`. Calls the MCP tool first, falls back to the CLI if MCP is unavailable.

Loggifly

Docker container log alerting via keyword/regex patterns. Exposes 3 actions via the lab homelab control plane.

How to call it

Prefer the MCP tool. Fall back to the CLI only when MCP is unavailable.

MCP (preferred)

One tool: mcp__lab__loggifly. Dispatch shape: { "action": "<name>", "params": {...} }.

Discover actions live:

{ "action": "help" }
{ "action": "schema", "params": { "action": "<name>" } }

Full action catalog: references/mcp.md.

CLI fallback

lab loggifly --help
lab loggifly <action> --help
labby --json loggifly <action> ...

CLI mirrors MCP actions; dots become dashes (server.health → server-health). Full CLI surface: references/cli.md.

Highlights

contract.status — Get LoggiFly contract/API status
health.status — Check LoggiFly health
config.summary — Get active configuration summary

Configuration

Credentials and base URLs live in ~/.lab/.env. Onboard / re-extract with labby extract scan and labby extract apply. Verify connectivity:

labby doctor service loggifly

When NOT to use this skill

The user is asking about a different lab service — load that service's skill instead.
The user is asking about lab itself (CLI internals, install, gateway, doctor across all services) — that's operator-tier, not loggifly-specific.