Basinfy/Basinfy-SaaS-Studio / .agents/skills/saas-seo
saas-seo
UnverifiedSaaS SEO, GEO & Agentic Readiness hub — technical, schema, AI search, llms.txt, and drift.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.2 KB |
| references/backlink-quality.md | markdown | 3.4 KB |
| references/cwv-thresholds.md | markdown | 7.5 KB |
| references/eeat-framework.md | markdown | 7.2 KB |
| references/eeat-scoring-guide.md | markdown | 1.5 KB |
| references/free-backlink-sources.md | markdown | 6.2 KB |
| references/local-schema-multilocation.md | markdown | 1.4 KB |
| references/local-schema-types.md | markdown | 8.0 KB |
| references/local-search-behavior.md | markdown | 2.8 KB |
| references/local-seo-signals.md | markdown | 7.7 KB |
| references/maps-api-endpoints.md | markdown | 6.1 KB |
| references/maps-free-apis.md | markdown | 6.0 KB |
| references/maps-gbp-checklist.md | markdown | 6.0 KB |
| references/maps-geo-grid.md | markdown | 4.3 KB |
| references/quality-gates.md | markdown | 5.9 KB |
| references/schema-types.md | markdown | 9.2 KB |
| references/thinking-framework-validate-act.md | markdown | 3.1 KB |
| references/thinking-framework.md | markdown | 6.6 KB |
references/thinking-framework-validate-act.md
View on GitHub# Audit Synthesis Framework: VALIDATE and ACT
> Phases 3 and 4 of the 10-principle framework in `thinking-framework.md`. Read that file first for the phase overview, PERCEIVE and ANALYZE.
## VALIDATE
### 7. FEEL: emotional intelligence + intuition
Pure-logic recommendations break on contact with the actual reader /
business / stakeholder. Pressure-test against:
- **User experience.** Would the recommendation make the page worse for
a human reader? (Common failure: stuffing FAQ schema for a site Google
doesn't even show rich results for.)
- **Brand voice.** Would the recommendation conflict with the site's
existing tone? (Common failure: recommending "answer-first" rewrites
on a luxury brand that uses suspense as a UX device.)
- **Operator capacity.** Is this realistic for the team that has to ship
it? (Common failure: recommending 30 new location pages to a 2-person
agency.)
- **Hard-earned intuition.** When the data is ambiguous, trust pattern
recognition from past sites in the same vertical.
**Discipline:** if you can't articulate the human cost of a
recommendation, you haven't fully validated it.
### 8. ACCEPT: intellectual humility
Each recommendation should carry the falsifiability that comes with
honesty:
- If the hypothesis behind the recommendation is wrong, what would
prove it? (Set a measurable check.)
- If the user has tried this and it didn't work before, surface that.
Don't re-recommend the same thing.
- If a constraint cannot be removed (legal, brand, technical), the
recommendation has to pivot, not double down.
- If a v1 recommendation is now stale because Google's guidance shifted,
retract it explicitly.
**Discipline:** every recommendation gets a "how would we know this
failed?" line. No invisible bets.
---
## ACT
### 9. CREATE: generative output
Stop strategizing. Produce the artifact:
- A markdown report with prioritized actions, dependencies, and
measurable outcomes.
- Generated schema JSON-LD ready to paste into the site.
- A content brief with target keywords, outline, and internal links.
- A PDF through the current client's export tools, when available and requested. Otherwise provide the Markdown report and mark PDF export as unavailable.
- The smallest implementation of the highest-leverage recommendation,
not the full plan.
**Discipline:** ship the artifact. Analysis paralysis is the enemy.
### 10. GROW: iterative loop
The audit is a snapshot, not a verdict. Build the feedback loop:
- Capture a baseline via `/seo drift baseline <url>` so subsequent
audits can prove what changed.
- Define one or two leading indicators the user should monitor (CrUX
trend, GSC impressions for a target cluster, brand-mention growth on
Reddit / YouTube).
- Schedule a re-audit cadence appropriate to the site's velocity
(weekly for a high-churn ecommerce; quarterly for a B2B SaaS).
- Surface what claude-seo itself **could not measure** (offline
conversion, brand lift, customer interviews) so the human closes
those loops.
**Discipline:** the last paragraph of every audit names what the next
audit should look for.
---
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |