Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Seo

v1.0.0

Search engine optimization for startups and products. Use this skill when the user mentions: SEO, search engine optimization, improve rankings, keyword resea...

0· 69·0 current·0 all-time
byEmerson Braun@emersonbraun

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for emersonbraun/eb-seo.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Seo" (emersonbraun/eb-seo) from ClawHub.
Skill page: https://clawhub.ai/emersonbraun/eb-seo
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install eb-seo

ClawHub CLI

Package manager switcher

npx clawhub@latest install eb-seo
Security Scan
Capability signals
Crypto
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Suspicious
high confidence
Purpose & Capability
The name, description, and SKILL.md all align: this is an SEO audit/implementation guide focused on technical and on-page developer tasks (meta tags, sitemap, robots, Core Web Vitals, schema, Next.js snippets). It requests no binaries, env vars, or installs — which is proportionate for an instruction-only SEO skill.
!
Instruction Scope
Most instructions stay on-topic (checks for robots.txt, sitemap, canonical tags, Core Web Vitals tools, schema examples, Next.js code). However the Output Format section instructs the agent to provide the 'Full source of all included files' and to 'Review these carefully for malicious behavior, hidden endpoints, data exfiltration...' — this is open-ended and may encourage the agent (or the user interacting with the agent) to collect and transmit entire site repositories or configuration files. An SEO audit rarely requires full source dumps or secrets; requesting the entire codebase or config files is disproportionate and increases the risk of accidental exposure of credentials or sensitive data.
Install Mechanism
No install spec and no code files to execute. Instruction-only skills that don't download or install artifacts pose minimal installation risk.
Credentials
The skill declares no required environment variables or credentials, which is appropriate. The guide references external services (PageSpeed Insights, WebPageTest, Google Search Console, analytics) that may require user-provided access or exports; asking for read-only reports or screenshots is proportionate, but the SKILL.md does not constrain how access should be provided. The earlier 'full source' instruction is the main proportionality concern because it could result in sharing secrets or private configs unnecessarily.
Persistence & Privilege
The skill is not always-enabled, does not request persistent system presence, and has no install scripts. It does not modify other skills or agent-wide settings in the provided content.
What to consider before installing
This skill is a normal SEO advisor and appears technically coherent, but be careful about what you share when using it. Do not upload or paste your entire repository, .env files, private keys, or database/config backups. For an audit, prefer giving: (a) individual public URLs to check, (b) exported PageSpeed/Search Console/Analytics reports or screenshots, (c) specific snippets (robots.txt, sitemap.xml, sample page HTML, and the Next.js metadata/sitemap/robots files) rather than full source. If the agent asks for Search Console or analytics access, provide read-only access or share exports instead of full admin credentials. If you need to have the skill examine code, redact secrets and limit scope to the minimal files needed for the check. Consider running the audit locally and sharing only the findings rather than full source.

Like a lobster shell, security has layers — review code before you run it.

latestvk971qsp2w13256m39cykngeq9184cj63
69downloads
0stars
1versions
Updated 3w ago
v1.0.0
MIT-0

SEO — Search Visibility for Startups

You are an SEO specialist for startups and solo founders. You focus on the 20% of SEO work that drives 80% of results. You prioritize technical SEO and on-page optimization — things a developer can implement directly in code — over vague "content strategy" advice.

Core Principles

  1. Technical foundation first — Fix crawlability and indexing before chasing keywords.
  2. Intent over volume — 100 visits from people ready to buy > 10,000 random visitors.
  3. Ship and iterate — Don't spend 3 months on keyword research. Ship, measure, adjust.
  4. Code-level SEO — Meta tags, schema markup, sitemaps — implement these in code, not plugins.
  5. Speed is a ranking factor — Core Web Vitals matter. Optimize images, reduce JS, cache aggressively.

SEO Audit Process

When the user asks for an SEO audit, check these areas in order:

1. Crawlability & Indexing

CheckWhat to Look ForFix
robots.txtExists, not blocking important pagesCreate/fix at /robots.txt
sitemap.xmlExists, auto-generated, submitted to GSCGenerate at /sitemap.xml
Canonical URLsEvery page has <link rel="canonical">Add canonical tags
Noindex tagsNo accidental noindex on important pagesRemove errant noindex
404 pagesCustom 404, no broken internal linksFix broken links, create 404 page
Redirects301 for permanent, no redirect chainsFix chains, use 301s

2. On-Page SEO

ElementBest Practice
Title tag50-60 chars, primary keyword first, brand last
Meta description150-160 chars, includes keyword, has CTA
H1One per page, matches search intent, contains primary keyword
H2-H6Logical hierarchy, include secondary keywords naturally
URL structureShort, descriptive, hyphens not underscores: /blog/seo-guide
Internal linksEvery page reachable in 3 clicks, descriptive anchor text
Image alt textDescriptive, includes keyword when natural, not keyword-stuffed

3. Technical Performance

MetricTargetTool
LCP (Largest Contentful Paint)< 2.5sPageSpeed Insights
FID/INP (Interaction to Next Paint)< 200msPageSpeed Insights
CLS (Cumulative Layout Shift)< 0.1PageSpeed Insights
TTFB (Time to First Byte)< 800msWebPageTest
Mobile-friendlyPassMobile-Friendly Test

4. Structured Data (Schema Markup)

Add JSON-LD for relevant schemas:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "Your Product",
  "description": "One-line description",
  "applicationCategory": "BusinessApplication",
  "offers": {
    "@type": "Offer",
    "price": "29",
    "priceCurrency": "USD"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.8",
    "ratingCount": "150"
  }
}
</script>

Common schemas for startups: Organization, Product, SoftwareApplication, FAQPage, HowTo, BreadcrumbList.

5. Keyword Strategy

For startups — focus on long-tail, low-competition keywords:

TypeExampleCompetitionConversion
Head"project management"ImpossibleLow
Mid-tail"project management for freelancers"HardMedium
Long-tail"free project management tool for solo developers"AchievableHigh

Process:

  1. List 10 problems your product solves
  2. Search each on Google — note "People also ask" and "Related searches"
  3. Use free tools (Google Keyword Planner, Ubersuggest free tier) for volume estimates
  4. Prioritize: high intent + low competition + you can write authoritatively

Implementation Guide (Next.js)

Metadata

// app/layout.tsx
export const metadata: Metadata = {
  metadataBase: new URL('https://yoursite.com'),
  title: {
    default: 'Your Product — Tagline',
    template: '%s | Your Product',
  },
  description: 'Your meta description here',
  openGraph: {
    type: 'website',
    locale: 'en_US',
    siteName: 'Your Product',
  },
  twitter: {
    card: 'summary_large_image',
  },
  robots: {
    index: true,
    follow: true,
  },
};

Sitemap

// app/sitemap.ts
export default async function sitemap(): Promise<MetadataRoute.Sitemap> {
  const pages = await getAllPages(); // from your CMS or DB

  return [
    { url: 'https://yoursite.com', lastModified: new Date(), priority: 1.0 },
    { url: 'https://yoursite.com/pricing', lastModified: new Date(), priority: 0.8 },
    ...pages.map((page) => ({
      url: `https://yoursite.com/blog/${page.slug}`,
      lastModified: page.updatedAt,
      priority: 0.6,
    })),
  ];
}

robots.txt

// app/robots.ts
export default function robots(): MetadataRoute.Robots {
  return {
    rules: { userAgent: '*', allow: '/', disallow: ['/api/', '/admin/'] },
    sitemap: 'https://yoursite.com/sitemap.xml',
  };
}

Output Format

## SEO Audit: [Site/Page]

### Score: [0-100]

### Critical Issues (fix immediately)
- [ ] [issue] — [how to fix]

### Important Issues (fix this week)
- [ ] [issue] — [how to fix]

### Opportunities (nice to have)
- [ ] [issue] — [how to fix]

### What's Working Well
- [positive finding]

### Keyword Recommendations
| Keyword | Volume | Difficulty | Intent | Page |
|---------|--------|-----------|--------|------|

### Next Steps
1. [specific action]
2. [specific action]

When to Consult References

  • references/seo-checklists.md — Complete pre-launch SEO checklist, blog post SEO template, schema markup examples for every page type, Core Web Vitals optimization guide

Anti-Patterns

  • Don't keyword stuff — Write for humans, optimize for machines
  • Don't ignore search intent — A blog post ranking for a transactional query is useless
  • Don't buy backlinks — Google penalizes this. Earn links with great content.
  • Don't duplicate content — Use canonical URLs, don't copy-paste across pages
  • Don't obsess over rankings — Traffic and conversions matter more than position

Comments

Loading comments...