adynato-seo
Handles SEO requirements for all web content including blogs, landing pages, and documentation. Covers LD+JSON schema.org structured data, internal backlinks strategy, further reading sections, meta tags, and Open Graph. Use when creating or editing any public-facing web content, blog posts, or pages that need search visibility.
Best use case
adynato-seo is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Handles SEO requirements for all web content including blogs, landing pages, and documentation. Covers LD+JSON schema.org structured data, internal backlinks strategy, further reading sections, meta tags, and Open Graph. Use when creating or editing any public-facing web content, blog posts, or pages that need search visibility.
Teams using adynato-seo should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/adynato-seo/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How adynato-seo Compares
| Feature / Agent | adynato-seo | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Handles SEO requirements for all web content including blogs, landing pages, and documentation. Covers LD+JSON schema.org structured data, internal backlinks strategy, further reading sections, meta tags, and Open Graph. Use when creating or editing any public-facing web content, blog posts, or pages that need search visibility.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# SEO Skill
Use this skill when creating or modifying any public-facing web content for Adynato projects.
## Requirements Checklist
Every public page MUST include:
1. **LD+JSON Structured Data** - schema.org markup in `<script type="application/ld+json">`
2. **Internal Backlinks** - Links to related Adynato projects/pages
3. **Further Reading Section** - At the end of content, link to related resources
4. **Meta Tags** - title, description, keywords
5. **Open Graph Tags** - og:title, og:description, og:image, og:url
## LD+JSON Schema.org
Always include structured data. See [references/SCHEMAS.md](references/SCHEMAS.md) for templates.
### Required Schemas by Content Type
| Content Type | Required Schemas |
|--------------|------------------|
| Blog Post | Article, BreadcrumbList, Organization |
| Landing Page | WebPage, Organization, optional Product/Service |
| Documentation | TechArticle, BreadcrumbList |
| Product Page | Product, BreadcrumbList, Organization |
### Implementation
Place LD+JSON in the `<head>` or before closing `</body>`:
```html
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
...
}
</script>
```
For multiple schemas, use `@graph`:
```html
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@graph": [
{ "@type": "Article", ... },
{ "@type": "BreadcrumbList", ... },
{ "@type": "Organization", ... }
]
}
</script>
```
## Internal Backlinks
Every piece of content must link to related Adynato projects and pages.
### Rules
1. **Minimum 2-3 internal links** per page/post
2. **Link naturally** within content, not just in footer sections
3. **Use descriptive anchor text** - not "click here" or "read more"
4. **Cross-link related projects** - if mentioning image optimization, link to img4web
### Example
```markdown
When optimizing images for your project, use [img4web](https://github.com/adynato/img4web)
to automatically compress and convert assets to modern formats like WebP and AVIF.
```
## Further Reading Section
Every blog post and documentation page must end with a "Further Reading" section.
### Format
```markdown
## Further Reading
- [Related Post Title](/blog/related-post) - Brief description of what reader will learn
- [Another Project](https://github.com/adynato/project) - How it relates to current topic
- [External Resource](https://example.com) - Why this external link is valuable
```
### Rules
1. **Minimum 3 links** in Further Reading
2. **At least 1 internal link** to Adynato content
3. **Include brief descriptions** explaining relevance
4. **Mix of internal and external** resources when appropriate
## Meta Tags
### Required Meta Tags
```html
<meta name="title" content="Page Title - Adynato">
<meta name="description" content="Concise description under 160 characters">
<meta name="keywords" content="relevant, keywords, comma, separated">
<meta name="author" content="Adynato">
```
### Open Graph (Required)
```html
<meta property="og:type" content="article">
<meta property="og:url" content="https://adynato.com/blog/post-slug">
<meta property="og:title" content="Post Title">
<meta property="og:description" content="Description for social sharing">
<meta property="og:image" content="https://adynato.com/images/og/post-slug.png">
<meta property="og:site_name" content="Adynato">
```
### Twitter Cards
```html
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Post Title">
<meta name="twitter:description" content="Description for Twitter">
<meta name="twitter:image" content="https://adynato.com/images/og/post-slug.png">
```
## Blog Post Frontmatter
For MDX/Markdown blogs, include this frontmatter:
```yaml
---
title: "Post Title"
description: "Meta description under 160 characters"
date: "2026-01-17"
author: "Author Name"
tags: ["tag1", "tag2"]
image: "/images/blog/post-slug/cover.png"
ogImage: "/images/og/post-slug.png"
schema:
type: "Article"
datePublished: "2026-01-17"
dateModified: "2026-01-17"
---
```
## Validation
Before publishing, verify:
- [ ] LD+JSON validates at https://validator.schema.org/
- [ ] Meta description is under 160 characters
- [ ] OG image exists and is correct dimensions (1200x630)
- [ ] At least 2 internal backlinks present
- [ ] Further Reading section has 3+ links
- [ ] All links are working (no 404s)Related Skills
adynato-aimake
Integrate with aimake's AI-powered delivery pipeline via MCP. Covers connecting to aimake, using code/docs/kanban tools, understanding the card-based system, and leveraging AI capabilities. Use when building integrations with aimake or using its MCP tools.
adynato-github
GitHub workflow conventions for Adynato projects. Covers creating PRs with gh CLI, writing thorough descriptions, and using stacked PRs for large deliverables. Use when creating pull requests, managing branches, or breaking down large features.
adynato-web-api
Web API development conventions for Adynato projects. Covers API routes, middleware, authentication, error handling, validation, and response formats for Next.js and Node.js backends. Use when building or modifying API endpoints, server actions, or backend logic.
adynato-mobile-api
API integration patterns for Adynato mobile apps. Covers data fetching with TanStack Query, authentication flows, offline support, error handling, and optimistic updates in React Native/Expo apps. Use when integrating APIs into mobile applications.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
obsidian-daily
Manage Obsidian Daily Notes via obsidian-cli. Create and open daily notes, append entries (journals, logs, tasks, links), read past notes by date, and search vault content. Handles relative dates like "yesterday", "last Friday", "3 days ago".
obsidian-additions
Create supplementary materials attached to existing notes: experiments, meetings, reports, logs, conspectuses, practice sessions, annotations, AI outputs, links collections. Two-step process: (1) create aggregator space, (2) create concrete addition in base/additions/. INVOKE when user wants to attach any supplementary material to an existing note. Triggers: "addition", "create addition", "experiment", "meeting notes", "report", "conspectus", "log", "practice", "annotations", "links", "link collection", "аддишн", "конспект", "встреча", "отчёт", "эксперимент", "практика", "аннотации", "ссылки", "добавь к заметке".
observe
Query and manage Observe using the Observe CLI. Use when the user wants to run OPAL queries, list datasets, manage objects, or interact with their Observe tenant from the command line.
observability-review
AI agent that analyzes operational signals (metrics, logs, traces, alerts, SLO/SLI reports) from observability platforms (Prometheus, Datadog, New Relic, CloudWatch, Grafana, Elastic) and produces practical, risk-aware triage and recommendations. Use when reviewing system health, investigating performance issues, analyzing monitoring data, evaluating service reliability, or providing SRE analysis of operational metrics. Distinguishes between critical issues requiring action, items needing investigation, and informational observations requiring no action.
nvidia-nim
NVIDIA NIM inference microservices for deploying AI models with OpenAI-compatible APIs, self-hosted or cloud
numpy-string-ops
Vectorized string manipulation using the char module and modern string alternatives, including cleaning and search operations. Triggers: string operations, numpy.char, text cleaning, substring search.
nova-act-usability
AI-orchestrated usability testing using Amazon Nova Act. The agent generates personas, runs tests to collect raw data, interprets responses to determine goal achievement, and generates HTML reports. Tests real user workflows (booking, checkout, posting) with safety guardrails. Use when asked to "test website usability", "run usability test", "generate usability report", "evaluate user experience", "test checkout flow", "test booking process", or "analyze website UX".