agentleFS
ww-w-aiww-w-ai/bkit-gemini/skills/phase-7-seo-security/SKILL.md

phase-7-seo-security

Skill66 starsChanged 7 months agoApache-2.0View on GitHub

Skill for search optimization (SEO) and security hardening. Covers meta tags, semantic HTML, and security vulnerability checks.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use proper heading hierarchy (h1 → h2 → h3)

    line 73
  2. Distinctive:

    Add alt text to images

    line 74
  3. Distinctive:

    Use semantic elements (article, section, nav)

    line 75

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Phase 7: SEO & Security

Optimize for search and secure your application

SEO Checklist

1. Meta Tags

// app/layout.tsx
export const metadata: Metadata = {
  title: {
    template: '%s | My App',
    default: 'My App - Best Product'
  },
  description: 'Description for search engines',
  keywords: ['keyword1', 'keyword2'],
  openGraph: {
    title: 'My App',
    description: 'Description for social sharing',
    images: ['/og-image.png']
  },
  twitter: {
    card: 'summary_large_image'
  }
};

2. Semantic HTML

  • Use proper heading hierarchy (h1 → h2 → h3)
  • Add alt text to images
  • Use semantic elements (article, section, nav)
  • Implement structured data (JSON-LD)

3. Performance

  • Image optimization (next/image)
  • Code splitting
  • Lazy loading
  • Core Web Vitals monitoring

Security Checklist

1. Headers

// next.config.js
const securityHeaders = [
  { key: 'X-Frame-Options', value: 'DENY' },
  { key: 'X-Content-Type-Options', value: 'nosniff' },
  { key: 'Strict-Transport-Security', value: 'max-age=31536000' },
  { key: 'Content-Security-Policy', value: "default-src 'self'" }
];

2. Input Validation

  • Validate all user inputs
  • Sanitize HTML content
  • Use parameterized queries
  • Implement rate limiting

3. Authentication

  • Secure password hashing
  • JWT token expiration
  • CSRF protection
  • Session management

Next Phase

After completion: /phase-8-review

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.