seo-geo
|
pinned to #d72eb64updated 3 weeks ago
Ask your AI client: “install skills/seo-geo”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/seo-geometahub onboarded this repo on the author's behalf.
If you own github.com/ReScienceLab/opc-skills on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
1,137
Last commit
3 weeks ago
Latest release
published
- #agent-skills
- #ai-tools
- #claude-code
- #geo
- #llm-tools
- #opc
- #seo
About this skill
Pulled from SKILL.md at publish time.
Comprehensive SEO and GEO (Generative Engine Optimization) for websites. Optimize for both traditional search engines (Google, Bing) and AI search engines (ChatGPT, Perplexity, Gemini, Copilot, Claude).
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.d72eb64· 3 weeks ago
Documentation
121Description qualityfail
Only 1 words · 1 chars — minimum 15 words
A skill's description doubles as its trigger. Describe what it does, when to use it, what file types it handles.
README is present and substantialwarn
README present but its contents couldn't be read this scan
Transient fetch issue — re-run the eval to grade the README's substance.
Tags / topics declaredwarn
No manifest tags and no GitHub repo topics
Add tags to the manifest (or GitHub topics on the repo) so the registry's search and category filters surface this artifact.
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
Release history
1- releasecurrentd72eb64warn3 weeks ago
Contents
Archive Skill
Capture, index, and reuse project knowledge across sessions.
When to Archive
- After completing a significant task (deploy, migration, major feature)
- After resolving a tricky debugging session
- When the user says "archive this"
- After any multi-step process with learnings worth preserving
When to Consult Archives
- Before debugging infrastructure, deploy, or CI issues
- Before repeating a process done in a past session
- When encountering an error that may have been solved before
Search: grep -ri "keyword" .archive/
Index: .archive/MEMORY.md
Archive Workflow
- Read
.archive/MEMORY.md— check for related existing archives - Create
.archive/YYYY-MM-DD/directory if needed - Write markdown file with YAML frontmatter (see
references/TEMPLATE.md) - Update
.archive/MEMORY.md: add one-line entry under the right category - If related archives exist, add
relatedfield in frontmatter
Lookup Workflow
- Read
.archive/MEMORY.mdto find relevant entries - Read the specific archive file for detailed context
- Apply learnings to current task
Categories
- infrastructure — AWS, ECS, IAM, networking, secrets, CloudWatch
- release — TestFlight, versioning, Git Flow, CHANGELOG
- debugging — Bug fixes, error resolution, gotchas
- feature — Feature design, implementation notes
- design — UI/UX, icons, visual design
Rules
.archive/must be in.gitignore— local-only notes- Keep entries concise but reproducible
- Focus on problems, fixes, and exact commands
- Always update MEMORY.md after creating an archive
- Use descriptive filenames (e.g.,
cloudwatch-logging.mdnotsession.md) - Include YAML frontmatter with
tags,category, and optionalrelated
Reviews
No reviews yet. Be the first.
Related
Planning With Files
Claude Code skill implementing Manus-style persistent markdown planning — the workflow pattern behind the $2B acquisition.
Browser Use
🌐 Make websites accessible for AI agents. Automate tasks online with ease.
Frontend Slides
Create beautiful slides on the web using Claude's frontend skills
mh install skills/seo-geo