skills.rest
FreeshardBase
FreeshardBaseOFFICIAL
Explore all skills by this author →
GitHub

freeshard-debugging-playbook

Diagnose Freeshard shard_core failures by mapping symptoms to remediation steps.

47|2|Updated Feb 11, 2025
Search Tags:#debugging#troubleshooting#docker#incident-response#traefik#freeshard
One-click install
npx skills add https://github.com/FreeshardBase/freeshard --skill freeshard-debugging-playbook
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: freeshard-debugging-playbook
Source: https://github.com/FreeshardBase/freeshard/tree/main/.claude/skills/freeshard-debugging-playbook
Command: npx skills add https://github.com/FreeshardBase/freeshard --skill freeshard-debugging-playbook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, symptom-based diagnostic framework for resolving common failure modes in the Freeshard shard_core stack, reducing downtime by mapping observed errors to verified root causes and fixes.

Core Features & Use Cases

  • Symptom-to-Triage Index: Quickly identify the cause of issues like Traefik file descriptor exhaustion, proxy 422 errors, or app installation stalls.
  • Operational Diagnostics: Provides specific, safe commands to inspect container health, disk usage, and log patterns for live shards.
  • Use Case: When a user reports that their shard is unreachable despite containers appearing healthy, use this skill to verify if Traefik is hitting file descriptor limits and apply the documented resolution.

Quick Start

Use the freeshard-debugging-playbook to diagnose why the shard is unreachable by checking the Traefik file descriptor limits and logs.

Frequently Asked Questions about freeshard-debugging-playbook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot a Freeshard shard_core container that is unreachable despite appearing healthy?▼

To troubleshoot an unreachable shard_core container, verify if Traefik is hitting file descriptor limits by inspecting container health, disk usage, and Traefik logs using provided diagnostic commands.

What is the best way to resolve Traefik file descriptor exhaustion in a Docker production environment?▼

The best way to resolve Traefik file descriptor exhaustion is to map the observed symptom to specific discriminating experiments and apply the documented remediation steps for the shard_core stack.

Why does my shard_core app installation stall during containerized deployment?▼

Shard_core app installation stalls can be diagnosed by mapping the symptom to verified root causes within the operational diagnostics framework, inspecting container runtime logs and resource constraints.

Do I need direct Docker environment access to diagnose shard_core production incidents?▼

Yes, diagnosing shard_core production incidents requires direct access to the Docker environment and the ability to execute diagnostic commands against the stack to inspect container health and logs.

How to fix Traefik proxy 422 errors in the Freeshard stack?▼

To fix Traefik proxy 422 errors, use the symptom-to-triage index to identify the specific failure mode and execute the corresponding safe diagnostic commands to determine the root cause and apply fixes.

Related Skills

Explore More Software Engineering Skills→
alannreyesalannreyes

Docker Health & Build Validation

Validate docker-compose configuration, build images, and verify service health.

Community
Advanced
dSchulenburgdSchulenburg
3

docker-management

Manage Docker containers on a remote Hetzner server via SSH.

Community
Advanced
htlin222htlin222
77

vm-docker

Deploy Docker services on a local VM with Traefik and Homepage.

Community
Advanced
NagyViktNagyVikt
2

docker-debug-containers

Diagnose Docker container failures by analyzing state, logs, and resource utilization.

Community
Intermediate