Skill: Huginn Browser Automation

Capability Domain: Automation
Technology Stack: Huginn, Browser Automation
Linked Activities: Configure Huginn for Automated Reporting

Recipe

1. Check ../huginn for an existing Agent/Scenario close to what's needed before creating one from scratch — most refresh-on-a-schedule needs already have a near-identical precedent there.
2. Configure through the Huginn web UI: create/update the Agent, set its schedule, wire it into the target Scenario. Record the Agent's name and purpose in this playbook's own notes, not just in Huginn — there's no IaC diff to review later.
3. Trigger the Agent's dry-run/"run now" action once before trusting its schedule — Huginn Agents fail silently on a schedule if a dependency (an API token, an upstream Agent) breaks.

Pitfalls

• This whole activity is a flagged stopgap: don't let a manually-configured Agent quietly become permanent infrastructure — note it as a future-MCP-connector candidate every time it's touched.