Run any Skill in Manus with one click

adguard

Stars1

Forks0

UpdatedJune 4, 2026 at 05:43

This skill should be used when the user asks about AdGuard Home status, DNS filtering, or blocked domains. Triggers include: "is adguard running", "how many queries did it block today", "show me recent DNS queries", "search the DNS log for a domain", "is example.com blocked", "AdGuard stats", or any question about DNS-level ad blocking or network filtering.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

jmagar

jmagar/lab

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

SKILL.md

readonly

name	adguard
description	This skill should be used when the user asks about AdGuard Home status, DNS filtering, or blocked domains. Triggers include: "is adguard running", "how many queries did it block today", "show me recent DNS queries", "search the DNS log for a domain", "is example.com blocked", "AdGuard stats", or any question about DNS-level ad blocking or network filtering.

AdGuard

DNS-level ad blocking and network filtering. Talk to it directly over the AdGuard Home control API (served under /control, HTTP Basic auth).

How to call it

Read the base URL and credentials from ~/.lab/.env:

ADGUARD_URL=$(grep -E '^ADGUARD_URL='      ~/.lab/.env | cut -d= -f2- | tr -d '"')
ADGUARD_USERNAME=$(grep -E '^ADGUARD_USERNAME=' ~/.lab/.env | cut -d= -f2- | tr -d '"')
ADGUARD_PASSWORD=$(grep -E '^ADGUARD_PASSWORD=' ~/.lab/.env | cut -d= -f2- | tr -d '"')
AUTH=(-u "$ADGUARD_USERNAME:$ADGUARD_PASSWORD")

Auth is HTTP Basic (-u user:pass). Never echo the password.

ADGUARD_* may be unset in ~/.lab/.env — populate them before use.

Common operations

Intent	Request
Server status + version + running state	`curl -sS "${AUTH[@]}" "$ADGUARD_URL/control/status"`
DNS query statistics	`curl -sS "${AUTH[@]}" "$ADGUARD_URL/control/stats"`
Search the query log	`curl -sS "${AUTH[@]}" "$ADGUARD_URL/control/querylog?search=<term>&limit=50"`
Filtering status / rule lists	`curl -sS "${AUTH[@]}" "$ADGUARD_URL/control/filtering/status"`
Check whether a host is blocked	`curl -sS "${AUTH[@]}" "$ADGUARD_URL/control/filtering/check_host?name=<host>"`

The version string and running state are fields inside GET /control/status (there is no separate version endpoint). Full API reference: https://github.com/AdguardTeam/AdGuardHome/blob/master/openapi/openapi.yaml.

Configuration

ADGUARD_URL, ADGUARD_USERNAME, and ADGUARD_PASSWORD live in ~/.lab/.env. Verify connectivity:

curl -sS -o /dev/null -w 'HTTP %{http_code}\n' "${AUTH[@]}" "$ADGUARD_URL/control/status"

When NOT to use this skill

The user is asking about a different homelab service — load that service's skill instead.
The user wants to change filtering rules or protection settings — those are mutating POST /control/* endpoints; confirm intent first and consult the OpenAPI reference for the exact body.

More from this repository

same repository

creating-snippets

jmagar/lab

Use when creating, editing, validating, testing, running, explaining, or removing Labby Code Mode snippets; when a user wants a reusable workflow made from gateway MCP tools; or when building schema-backed snippets from upstream tool ids, JSON schemas, params, inputs, defaults, artifacts, and MCP/CLI snippet actions.

This skill should be used when the user wants to automate an iOS Simulator, drive an Android device or emulator via MCP tools, test on multiple devices simultaneously, run a visual regression baseline on mobile, audit accessibility on a real device, release an app to the Play Store, or use the claude-in-mobile CLI or MCP server. Does not apply for structured end-to-end test reports (use android-app-testing or desktop-app-testing for those).

2026-06-151

mcpjam-inspector

jmagar/lab

Interpret and use `mcpjam` probe, doctor, OAuth, apps conformance, tools, resources, and prompts output conservatively against MCP 2025-11-25. Use when interacting with MCP servers, executing tools, triaging findings, performing security reviews, deciding whether a CLI finding is real or overstated, or turning inspection output into an engineer-facing report with severity and confidence.

2026-06-131

repo-status

jmagar/lab

Audit the current Git checkout, open worktrees, local branches, stale or merged cleanup candidates, merge readiness, conflicts, PR/CI/test state, blockers, and safest merge order. Use when the user asks for repo status, branch/worktree cleanup candidates, stale branch review, conflict investigation, merge readiness, or what must be done before open branches can merge.

2026-06-131

using-labby

jmagar/lab

This skill should be used when the user mentions labby, the labby CLI, the Lab gateway, or any Lab operator surface. Triggers include: "run labby doctor", "check labby health", "start the labby MCP server", "configure ~/.lab/.env", "search upstream MCP tools with Code Mode", "use labby gateway to import servers", "manage the Labby marketplace", "reload the gateway", or any request to run labby CLI commands, inspect gateway upstreams, or dispatch an action against a Lab service.

2026-06-131

name	adguard
description	This skill should be used when the user asks about AdGuard Home status, DNS filtering, or blocked domains. Triggers include: "is adguard running", "how many queries did it block today", "show me recent DNS queries", "search the DNS log for a domain", "is example.com blocked", "AdGuard stats", or any question about DNS-level ad blocking or network filtering.

AdGuard

DNS-level ad blocking and network filtering. Talk to it directly over the AdGuard Home control API (served under /control, HTTP Basic auth).

How to call it

Read the base URL and credentials from ~/.lab/.env:

ADGUARD_URL=$(grep -E '^ADGUARD_URL='      ~/.lab/.env | cut -d= -f2- | tr -d '"')
ADGUARD_USERNAME=$(grep -E '^ADGUARD_USERNAME=' ~/.lab/.env | cut -d= -f2- | tr -d '"')
ADGUARD_PASSWORD=$(grep -E '^ADGUARD_PASSWORD=' ~/.lab/.env | cut -d= -f2- | tr -d '"')
AUTH=(-u "$ADGUARD_USERNAME:$ADGUARD_PASSWORD")

Auth is HTTP Basic (-u user:pass). Never echo the password.

ADGUARD_* may be unset in ~/.lab/.env — populate them before use.

Common operations

Intent	Request
Server status + version + running state	`curl -sS "${AUTH[@]}" "$ADGUARD_URL/control/status"`
DNS query statistics	`curl -sS "${AUTH[@]}" "$ADGUARD_URL/control/stats"`
Search the query log	`curl -sS "${AUTH[@]}" "$ADGUARD_URL/control/querylog?search=<term>&limit=50"`
Filtering status / rule lists	`curl -sS "${AUTH[@]}" "$ADGUARD_URL/control/filtering/status"`
Check whether a host is blocked	`curl -sS "${AUTH[@]}" "$ADGUARD_URL/control/filtering/check_host?name=<host>"`

Configuration

ADGUARD_URL, ADGUARD_USERNAME, and ADGUARD_PASSWORD live in ~/.lab/.env. Verify connectivity:

curl -sS -o /dev/null -w 'HTTP %{http_code}\n' "${AUTH[@]}" "$ADGUARD_URL/control/status"

When NOT to use this skill

The user is asking about a different homelab service — load that service's skill instead.
The user wants to change filtering rules or protection settings — those are mutating POST /control/* endpoints; confirm intent first and consult the OpenAPI reference for the exact body.