Pikud HaOref alert workflow — agent, skill, and SessionStart hook bundled. Fetches Israeli Home Front Command alerts and produces bilingual Markdown reports under reports/.
This file is **not** loaded by Claude Code as an agent (filename does not
Fetches Pikud HaOref (Israeli Home Front Command) alert data from oref.org.il and produces a Markdown alert report. Use when the user asks about current rocket/siren alerts, recent alert activity in Israel, or wants a daily/hourly Pikud HaOref alert report. Always writes the report under the project's reports/ directory. **Before invoking this agent, the calling Claude MUST fetch the current Israel local time (e.g. `TZ=Asia/Jerusalem date "+%Y-%m-%d %H:%M %Z"` on Unix, or `Get-Date -Format "yyyy-MM-dd HH:mm" ; [System.TimeZoneInfo]::Local.Id` adjusted for Asia/Jerusalem on Windows/PowerShell) and pass it verbatim in the agent prompt as a line like `current time is YYYY-MM-DD HH:MM IDT`. The agent has no clock of its own and depends on this for an exact last_n_hours window and the HHmm filename suffix.
This plugin requires configuration values that are prompted when the plugin is enabled. Sensitive values are stored in your system keychain.
Executes bash commands
Hook triggers when Bash tool is used
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
default_regionHebrew substring applied to area names when /alert-report is called with no region argument. Leave empty to mean 'no filter — show all areas'. Example: מנרה (matches קיבוץ מנרה), חוף (matches any beach area).
${user_config.default_region}A spec-driven, hands-on lab for learning how to build, install, and orchestrate agents and skills in Claude Code. Each lesson follows the same structure the lab itself teaches: Spec → Plan → Tasks → Verification.
Phase 1 theme — Pikud HaOref (Israeli Home Front Command) alerts. Real public data, no API keys, immediately recognizable for Israeli learners. The same lab will be re-skinned for enterprise DevOps audiences in Phase 2.
Most "agent tutorials" jump to frameworks. They skip the foundational question: what work belongs in an agent vs. inline in the conversation vs. a skill the user invokes? Picking the wrong shape makes agents that are too chatty, too broad, or impossible to reuse. This lab builds the intuition first, on a small real domain, then scales it to enterprise patterns.
By the end of the four lessons you will be able to:
ai-agents/
├── README.md ← you are here
├── .claude/
│ ├── agents/
│ │ ├── pikud-alerts.md ← Lesson 1: custom agent
│ │ └── code-reviewer.md ← Lesson 3: third-party agent (later)
│ └── skills/
│ └── alert-report/SKILL.md ← Lesson 2: custom skill (later)
├── lessons/
│ ├── 01-custom-agent.md ← start here
│ ├── 02-skills.md ← after Lesson 1
│ ├── 03-third-party-agents.md
│ └── 04-orchestration.md
├── references/
│ └── agent-discovery.md ← the 5 scopes, precedence, diagnostics
└── reports/ ← agent outputs land here
📖 Reference docs (factual material you can lift into slides):
references/agent-discovery.md— the 5 scopes Claude Code scans, precedence order, when discovery happens, and a diagnostic checklist for missing agents.
The single .claude/ directory at the repo root is intentional: Claude Code
auto-discovers agents and skills from the project root. Splitting them per
lesson would break discovery.
| Thing | Lives in | Triggered by | Best for |
|---|---|---|---|
| Agent | .claude/agents/<name>.md | Main Claude delegating via the Agent tool | Isolated context, parallel work, focused expertise (review, research, audit) |
| Skill | .claude/skills/<name>/SKILL.md | User typing /<name> (or model autoload) | Procedures the user invokes; reasoning stays in the main conversation |
| Inline | The current conversation | Whatever the user typed | One-off work, exploratory questions, things needing the full conversation |
Memorable rule of thumb:
lessons/01-custom-agent.md and follow the Tasks section.Once Phase 1 is complete, the same four lessons will be re-skinned for an enterprise DevOps audience. The agent will monitor a Kubernetes events stream or a CI/CD pipeline instead of oref alerts; the skill will produce an SRE incident summary instead of an alert report. The mechanics stay identical — only the domain changes — which is exactly the point of the lab structure.
npx claudepluginhub baruchihalamish20/ai-agents --plugin pikud-alerts-suiteTzevaAdom community alert workflow — agent, skill, and SessionStart hook bundled. Fetches Israeli rocket/siren alerts from api.tzevaadom.co.il and produces bilingual Markdown reports under reports/tzevaadom/.
Word-to-PDF batch converter — skill that converts .doc/.docx files under to-convert-word-files/ to PDFs under converted-pdf-files/ via LibreOffice headless (with pandoc fallback).
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Superpowers Plus core skills library for Claude Code: planning, execution routing, TDD, debugging, and collaboration workflows
Claude harness - A harness for solo developers (Vibecoders) to handle full-cycle contract development.
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
v9.44.1 — Patch release for Gemini environment/version detection and qwen auth gating. Run /octo:setup.
AI-powered development tools for code review, research, design, and workflow automation.