MikroCLAW: Skill for Claude Code

.claude/skills/mikrotik-troubleshoot/SKILL.md

mikrotik-troubleshoot is a skill for Claude Code from Syamsuddin/MikroCLAW. It costs 93 tokens per session (954 once invoked), scanned A, original, Apache-2.0.

A read-only troubleshooting workflow for MikroTik connectivity problems. It checks the network in layers, from physical interface status and the internet connection through routing, DNS, and firewall rules.

In plain words
What is it for?
Use it when the internet is down, browsing fails, DNS does not work, or a particular client cannot connect.
Why use it?
It narrows down where a connection fails instead of treating every internet problem as the same issue. This helps distinguish local hardware, ISP, routing, name-resolution, and firewall problems.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is Syamsuddin/MikroCLAW's own configuration. It tells Claude Code how to work on MikroCLAW itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything MikroCLAW configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Syamsuddin/MikroCLAW. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Syamsuddin/MikroCLAW/main/.claude/skills/mikrotik-troubleshoot/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Syamsuddin/MikroCLAW

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for mikrotik-troubleshoot

README.md
[![agentmods](https://agentmods.dev/badge/skills/syamsuddin/mikroclaw/mikrotik-troubleshoot/github.svg)](https://agentmods.dev/skills/syamsuddin/mikroclaw/mikrotik-troubleshoot)
Your own site
<a href="https://agentmods.dev/skills/syamsuddin/mikroclaw/mikrotik-troubleshoot"><img src="https://agentmods.dev/badge/skills/syamsuddin/mikroclaw/mikrotik-troubleshoot/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for mikrotik-troubleshoot

Your own site · 80×15
<a href="https://agentmods.dev/skills/syamsuddin/mikroclaw/mikrotik-troubleshoot"><img src="https://agentmods.dev/badge/skills/syamsuddin/mikroclaw/mikrotik-troubleshoot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 954 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00093 $0.00954
Opus 5 $0.00046 $0.00477
Sonnet 5 $0.00019 $0.00191
Haiku 4.5 $0.00009 $0.00095

Measured 10d ago against content hash c7e151fd5d6e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

mikrotik-troubleshoot scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/mikrotik-troubleshoot/SKILL.md · 62 lines

How it starts

The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MikroTik Troubleshooting

Orkestrasi tool MikroCLAW (MCP server mikroclaw) untuk mendiagnosis gangguan konektivitas secara berlapis dan menyimpulkan akar masalah. Read-only.

Jika user menyebut gejala/target spesifik (mis. "tidak bisa buka youtube", "klien 192.168.88.50 tak dapat internet"), fokuskan diagnosa ke sana.

Tool yang dipakai

  • mcp__mikroclaw__list_interfaces — status fisik/up-down
  • mcp__mikroclaw__dhcp_client + mcp__mikroclaw__ip_cloud — WAN/IP publik
  • mcp__mikroclaw__list_ip_addresses + mcp__mikroclaw__routing_table — IP & default route
  • mcp__mikroclaw__ping + mcp__mikroclaw__traceroute — uji jangkauan & jalur
  • mcp__mikroclaw__dns_settings + mcp__mikroclaw__dns_cache — resolusi nama
  • mcp__mikroclaw__firewall_connections + mcp__mikroclaw__firewall_filter_rules — blokir?
  • mcp__mikroclaw__interface_traffic_live — apakah ada trafik mengalir
  • mcp__mikroclaw__recent_logs — petunjuk (link down, DHCP gagal, dst.)

Alur diagnosa (berhenti di lapisan yang gagal)

  1. L1/L2 — interface. list_interfaces: interface WAN & LAN running? Jika WAN down → masalah fisik/ISP; cek recent_logs untuk "link down".
  2. L3 — alamat WAN. dhcp_client/ip_cloud: dapat IP dari ISP? Tidak dapat IP → masalah WAN/PPPoE/DHCP ke ISP.
  3. L3 — default route. routing_table: ada default route 0.0.0.0/0 & gateway reachable? ping ke gateway. Gagal → masalah uplink.
  4. Internet mentah. ping 8.8.8.8 (IP, bukan nama). Sukses tapi nama gagal → lompat ke DNS. Gagal → traceroute 8.8.8.8 untuk lihat di hop mana putus.
  5. DNS. dns_settings (server terisi & valid?), lalu ping nama domain (mis. google.com). Domain gagal padahal IP sukses = masalah DNS. Cek juga allow-remote-requests & dns_cache.
  6. Firewall. Bila trafik tertentu terblokir, firewall_filter_rules & firewall_connections: cari aturan drop/reject yang relevan dengan target/klien.
  7. Trafik. interface_traffic_live pada interface terkait untuk konfirmasi ada/tidaknya aliran data.

Read the full file on GitHub · 62 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 62 lines · 93 tokens per session scan A c7e151fd5d6e

Subscribe to this mod's changes

mikrotik-troubleshoot is a skill published in the GitHub repository Syamsuddin/MikroCLAW (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 93 tokens to every session and 954 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens