> open agents/devops/raspberry-pi/SOUL.md
> cat identity rules capabilities
Pihole SOUL.md
Pihole is a devops SOUL.md template built for infrastructure health, incidents, logs, deployment safety, and operational monitoring..
# Agent: Raspberry Pi Agent
CATEGORY
DevOps
ROLE_FOCUS
DevOps SOUL.md Template
FILE_PATH
agents/devops/raspberry-pi/SOUL.md
SOURCE_TYPE
awesome-openclaw-agents catalog
What This Template Type Covers
This page is a dedicated landing URL for the Pihole SOUL.md pattern. It gives users and search engines one stable page for this specific template type instead of hiding everything behind a single filter UI.
Best when incident handling, observability, and escalation boundaries must stay explicit.
Authorship Note
This page is an indexed preview, not an original authored template by this site. Template authorship remains with the original source, and this page exists to organize discovery, show a partial preview, and link back to the source file.
SOUL.md Preview
Open raw sourceIdentity
Responsibilities
Skills
Hardware Profile
Typical Use Cases
Start a pihole agent with a clearer identity and operating boundary.
Benchmark this devops template against other roles before customizing your own SOUL.md.
Use it when you need stronger defaults for devops work.
What To Look For In This SOUL.md
Best For
People searching for a named SOUL.md type, a shareable prompt starter, or a category-specific agent configuration page.
Likely Sections
Identity, philosophy, rules, skills, constraints, escalation rules, and response formatting tuned for pihole workflows.
FAQ
What is the Pihole SOUL.md template used for?
Pihole is a devops SOUL.md template used to define identity, operating rules, and expected behavior for that specific agent role.
Does this page show the real Pihole SOUL.md content?
Yes. This page renders parsed preview sections from the original SOUL.md source file and links back to the source file for the full document.
How should I customize the Pihole SOUL.md template?
Keep the role identity and core operating rules that match your use case, then adapt tone, boundaries, tools, and escalation rules to your own workflow.