AKA SEO Wireframe
v1.1.1Generate 200+ page authority site content using the Authority-Knowledge-Answer (AKA) framework. Produces structured content, internal linking maps, and SEO m...
⭐ 0· 86·0 current·0 all-time
byRabih Rizk@lebtiga
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill is an AKA-framework content generator and linking/orchestration system that uses Anthropic (claude-opus-4) for generation and optionally deploys to WordPress. Requesting an ANTHROPIC_API_KEY and optional WordPress REST credentials (WP_URL, WP_USER, WP_PASS) is proportional to the described capabilities. Note: registry metadata at the top reported 'Required env vars: none' while SKILL.md lists ANTHROPIC_API_KEY as required — that discrepancy should be resolved before trusting automated runs.
Instruction Scope
SKILL.md explicitly instructs the agent to write config and generated content to local paths (.factory/config/aka-wireframe/, generated-content/) and to run the five-step workflow including an optional auto-deploy to WordPress. All file reads/writes and the optional WP REST API deployment are within the claimed scope. This does grant the skill access to local project files and, if you provide them, WordPress credentials — so inspect outputs and use dry-run/staging first. There are no instructions to read unrelated system files or exfiltrate data to unknown endpoints.
Install Mechanism
This is an instruction-only skill with no install spec and no downloads. No packages or external installers are pulled — lowest-risk install posture.
Credentials
The only required credential is ANTHROPIC_API_KEY (used for the claimed model). WordPress credentials (URL, username, application password) are optional and clearly documented as only needed for the deploy step. This is proportionate. However, the registry metadata contradicts SKILL.md (metadata said no required env vars). Also, WP_PASS is sensitive — the skill suggests using an Application Password and revoking it after use (good guidance).
Persistence & Privilege
The skill does not request always:true and does not modify other skills. It writes project state and progress to local files (progress-tracker.json, .factory/*), which is consistent with orchestrator behavior. One consideration: autonomous invocation is enabled by default (disable-model-invocation: false). Combined with provided WP credentials and the skill's 'auto' mode, the agent could autonomously deploy to your site if invoked — use dry-run/staging or restrict autonomous execution if you want to avoid automatic deployments.
Assessment
This skill appears to do what it says: generate large volumes of SEO content (using your Anthropic key) and optionally deploy to WordPress. Before installing/using it: 1) Ensure you have and control an Anthropic API key (the SKILL.md requires ANTHROPIC_API_KEY even though registry metadata said none). 2) If you intend to use the WordPress deploy step, create a dedicated WordPress account with the least privileges needed (Editor role if feasible) and use an Application Password; revoke it after the deploy. 3) Always run the WordPress deploy in --dry-run mode and test on a staging site first — the skill can generate hundreds of pages and perform bulk changes. 4) Inspect generated files in generated-content/ and .factory/config/ before publishing; these may contain PII or marketing claims that require human review. 5) If you do not want the agent to automatically run the full pipeline (generate → link → deploy), avoid giving it WP credentials or disable autonomous invocation on your agent. 6) Resolve the metadata discrepancy (skill.json vs SKILL.md) with the publisher before trusting automated runs.Like a lobster shell, security has layers — review code before you run it.
latestvk978ghze569ey31khewqxwj7kh83sc85
License
MIT-0
Free to use, modify, and redistribute. No attribution required.