Overview

Automate a local SEO maintenance workflow for the two specific sites boll-koll.se and hyresbyte.se by running a predefined script, then returning the created PR link plus a short summary of key SEO findings.

Key Advantages

1.Very targeted and simple: one command abstracts a full SEO update workflow for boll-koll.se and hyresbyte.se.

2.Built-in safety guardrails via a strict allowlist (only boll-koll.se and hyresbyte.se) and a constrained command (`scripts/run.sh <site>`).

3.Automatically surfaces the resulting PR URL from script output, making it easy for humans to review and merge changes.

4.Optionally summarizes top SEO findings from `SEO_REPORT.md`, reducing the need to open and read the report manually.

5.Default-site behavior (boll-koll.se) and message parsing make it easy to trigger from natural chat (e.g., WhatsApp).

Use Cases

Routine SEO upkeep for boll-koll.se via chat, producing a PR and brief summary of changes.
On-demand SEO optimization runs for hyresbyte.se with a quick overview of top issues from the generated report.
Non-technical stakeholders triggering SEO maintenance through a chat interface and handing the PR off to developers/SEO specialists for review.
Automated weekly or monthly SEO runs wired into a conversational agent that reminds a team and posts PR links in a channel.

Evaluation Scores

7.5

/ 10

Reliability

7.0

Functionality

7.6

Usability

8.0

Safety

8.6

Performance

7.0

Compatibility

5.5

Based on 1 evaluation · Latest: 3/19/2026

Download Trend

Loading...

Evaluation History (1)

7.5/103/19/2026linux-x64

▼

OS: linux-x64LLM: z-ai/glm-5

**Quick judgement** A narrowly focused but well-scoped skill for running an SEO automation pipeline specifically for **boll-koll.se** and **hyresbyte.se**, then returning a PR URL and up to three key findings from `SEO_REPORT.md`. It is a good fit if you own or manage these sites and already trust the underlying `scripts/run.sh` workflow. **What it does well** - Restricts actions to a single command pattern (`scripts/run.sh <site>`) and an allowlist of two domains, which is a strong, simple safety model. - Handles natural-language messages by parsing which of the two sites is requested (defaulting to boll-koll.se when ambiguous). - Extracts the PR link from stdout and optionally summarizes the top SEO findings, saving time when reviewing results. **Key risks and limitations** - **Extremely domain-specific**: it is only useful for boll-koll.se and hyresbyte.se; any other domain should be refused by design. - **Opaque script behavior**: all real work is delegated to `scripts/run.sh`. If that script is slow, brittle, or has side-effects (e.g., heavy network usage, large diffs, or unexpected repository changes), the skill inherits those issues. - **Parsing fragility**: relies on the script printing a line starting with `"PR:"` and on a reasonably structured `SEO_REPORT.md`; changes in format can break PR extraction or the summary. - Potential **resource usage** or rate-limiting issues if the SEO pipeline performs intensive crawling, API calls, or frequent PR creation. **Recommended scenarios** - Teams responsible for **boll-koll.se** or **hyresbyte.se** who want a chat-triggered, standardized SEO update process that culminates in a PR. - Workflows where a human will always review and merge the generated PR, providing oversight over SEO changes and catching any oddities from the automation. - Environments where the underlying repo and `scripts/run.sh` are maintained and version-controlled, ensuring the automation remains aligned with current SEO strategies and doesn’t silently degrade. In summary, this is a specialized, relatively safe automation layer over an existing SEO script, best used by the site owners or their team, with human review of the resulting PRs as a standard practice.

Seo Autopilot