debian-linux-triage
Triage and resolve Debian Linux issues with apt, systemd, and AppArmor-aware guidance.
Best use case
debian-linux-triage is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Triage and resolve Debian Linux issues with apt, systemd, and AppArmor-aware guidance.
Teams using debian-linux-triage should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/debian-linux-triage/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How debian-linux-triage Compares
| Feature / Agent | debian-linux-triage | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Triage and resolve Debian Linux issues with apt, systemd, and AppArmor-aware guidance.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Debian Linux Triage
You are a Debian Linux expert. Diagnose and resolve the user’s issue with Debian-appropriate tooling and practices.
## Inputs
- `${input:DebianRelease}` (optional)
- `${input:ProblemSummary}`
- `${input:Constraints}` (optional)
## Instructions
1. Confirm Debian release and environment assumptions; ask concise follow-ups if required.
2. Provide a step-by-step triage plan using `systemctl`, `journalctl`, `apt`, and `dpkg`.
3. Offer remediation steps with copy-paste-ready commands.
4. Include verification commands after each major change.
5. Note AppArmor or firewall considerations if relevant.
6. Provide rollback or cleanup steps.
## Output Format
- **Summary**
- **Triage Steps** (numbered)
- **Remediation Commands** (code blocks)
- **Validation** (code blocks)
- **Rollback/Cleanup**Related Skills
linux-troubleshooting
Linux system troubleshooting workflow for diagnosing and resolving system issues, performance problems, and service failures.
linux-shell-scripting
This skill should be used when the user asks to "create bash scripts", "automate Linux tasks", "monitor system resources", "backup files", "manage users", or "write production she...
fedora-linux-triage
Triage and resolve Fedora issues with dnf, systemd, and SELinux-aware guidance.
centos-linux-triage
Triage and resolve CentOS issues using RHEL-compatible tooling, SELinux-aware practices, and firewalld.
bash-linux
Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.
arch-linux-triage
Triage and resolve Arch Linux issues with pacman, systemd, and rolling-release best practices.
context7-auto-research
Automatically fetch latest library/framework documentation for Claude Code via Context7 API
context-optimization
Apply compaction, masking, and caching strategies
context-driven-development
Use this skill when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md, and...
content-research-writer
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
content-marketer
Elite content marketing strategist specializing in AI-powered content creation, omnichannel distribution, SEO optimization, and data-driven performance marketing.
conductor-validator
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.