Web Scraping
platonai/Browser4
Extracts data from web pages using browser automation and CSS/JavaScript selectors.
When the user wants to choose or optimize rendering strategy for SEO.
Install Rendering Strategies
$ npx skills add kostja94/marketing-skills --skill rendering-strategies -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install kostja94/marketing-skills rendering-strategies --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/seo/technical/rendering-strategies .claude/skills/rendering-strategies && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "rendering-strategies" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/seo/technical/rendering-strategies into .claude/skills/rendering-strategies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rendering-strategies", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/kostja94/marketing-skills/tree/main/skills/seo/technical/rendering-strategiesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add kostja94/marketing-skills --skill rendering-strategies -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install kostja94/marketing-skills rendering-strategies --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/seo/technical/rendering-strategies .agents/skills/rendering-strategies && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "rendering-strategies" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/seo/technical/rendering-strategies into .agents/skills/rendering-strategies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rendering-strategies", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add kostja94/marketing-skills --skill rendering-strategies -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install kostja94/marketing-skills rendering-strategies --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/seo/technical/rendering-strategies .cursor/skills/rendering-strategies && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "rendering-strategies" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/seo/technical/rendering-strategies into .cursor/skills/rendering-strategies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rendering-strategies", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/kostja94/marketing-skills.git --path skills/seo/technical/rendering-strategies--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add kostja94/marketing-skills --skill rendering-strategies -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install kostja94/marketing-skills rendering-strategies --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/seo/technical/rendering-strategies .gemini/skills/rendering-strategies && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "rendering-strategies" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/seo/technical/rendering-strategies into .gemini/skills/rendering-strategies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rendering-strategies", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install kostja94/marketing-skills rendering-strategiesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add kostja94/marketing-skills --skill rendering-strategies -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/seo/technical/rendering-strategies .github/skills/rendering-strategies && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "rendering-strategies" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/seo/technical/rendering-strategies into .github/skills/rendering-strategies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rendering-strategies", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add kostja94/marketing-skills --skill rendering-strategies -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install kostja94/marketing-skills rendering-strategies --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/seo/technical/rendering-strategies .opencode/skills/rendering-strategies && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "rendering-strategies" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/seo/technical/rendering-strategies into .opencode/skills/rendering-strategies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rendering-strategies", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
rendering-strategies- GitHub stars
- 1k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 693 words
- Files
- 1
- Skills in repo
- 102
- Repo updated
- First seen
- Licence
- MIT
At a glance
When the user wants to choose or optimize rendering strategy for SEO.
- Wants to choose
- SKILL.md covers Scope (Technical SEO), Rendering Methods, Crawler Behavior and Component-Level: Content in…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Optimize rendering strategy for SEO
What it does
Rendering Strategies is an agent skill from kostja94/marketing-skills. When the user wants to choose or optimize rendering strategy for SEO. Also use when the user mentions "SSR," "SSG," "CSR," "ISR," "static rendering," "dynamic rendering," "server-side rendering," "client-side rendering," "JavaScript rendering," "pre-rendering," "prerender," "content in initial HTML," or "crawler visibility." For crawl issues, use site-crawlability.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Data & Analytics, covering Web scraping, Technical SEO and Backend development. It works with JavaScript. The repository describes itself as: Agent Skills for Marketing — SEO, Social, Influencer & More. 160+ open-source skills for SEO, content, 40+ page types, paid ads, channels, and strategies. Add project context… The licence is MIT.
When your agent uses it
- Wants to choose
- Optimize rendering strategy for SEO
- The user mentions SSR
- Static rendering
Example prompts
- “static rendering,”
- “dynamic rendering,”
- “server-side rendering,”
- “/rendering-strategies”
What it can do on your machine
Read from SKILL.md and the folder at commit 8dd89c5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
nextjs.orgvercel.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Rendering Strategies loads about 1.6k tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 693 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from kostja94/marketing-skills at commit 8dd89c5, republished under its MIT licence (© kostja94). 693 words, ~1,575 tokens.
Download SKILL.mdSave it as
.claude/skills/rendering-strategies/SKILL.md (or your agent's skills folder).- name
- rendering-strategies
- description
- When the user wants to choose or optimize rendering strategy for SEO. Also use when the user mentions "SSR," "SSG," "CSR," "ISR," "static rendering," "dynamic rendering," "server-side rendering," "client-side rendering," "JavaScript rendering," "pre-rendering," "prerender," "content in initial HTML," or "crawler visibility." For crawl issues, use site-crawlability.
- metadata.version
- 1.0.2
SEO Technical: Rendering Strategies
Guides rendering strategy selection and optimization for search engine and AI crawler visibility. Golden rule: Page data and metadata must be available on page load without JavaScript execution for optimal SEO.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Scope (Technical SEO)
- Static vs dynamic: SSG, SSR, ISR, CSR; when to use each
- Crawler behavior: Googlebot renders JS (with delays); AI crawlers do not
- Component-level: Content in initial HTML; tabs, carousels, nav
- Dynamic rendering: Prerender for bots when full SSR/SSG is not feasible
Rendering Methods
| Method | When HTML generated | SEO | Best for |
|---|---|---|---|
| SSG (Static Site Generation) | Build time | ✅ Best | Blog, docs, marketing pages; content rarely changes |
| SSR (Server-Side Rendering) | Request time | ✅ Good | News, product pages; dynamic, personalized content |
| ISR (Incremental Static Regeneration) | Build + revalidate | ✅ Good | Large sites; static with periodic updates |
| CSR (Client-Side Rendering) | Browser (after JS) | ❌ Poor | Dashboards, account pages; no SEO needed |
| Dynamic rendering | On-demand for bots | ✅ Fallback | SPAs; prerender for crawlers, SPA for users |
SSG (Static Site Generation)
HTML generated at build time; same HTML for every request. Best for SEO: crawlers receive full HTML immediately; optimal performance.
- Use when: Blog, docs, marketing pages, content that doesn't change frequently
- Framework: Next.js
getStaticProps, Astro, Gatsby
SSR (Server-Side Rendering)
HTML generated on each request. Good for SEO: crawlers receive complete HTML; supports dynamic, personalized content.
- Use when: News, product pages, user-specific content
- Tradeoff: Higher server load; slower TTFB than SSG
- Framework: Next.js
getServerSideProps, Remix
ISR (Incremental Static Regeneration)
Static at build; pages can revalidate after a period. Good for SEO: combines static performance with freshness.
- Use when: Large sites (millions of pages); content updates periodically
- Framework: Next.js
revalidateingetStaticProps
CSR (Client-Side Rendering)
Server sends minimal HTML shell; content renders in browser after JS loads. Not for SEO: crawlers may see empty content; indexing delays or failures.
- Use when: Dashboards, account pages, internal tools—no search visibility needed
- Avoid for: Public content, marketing pages, blog
Dynamic Rendering
Serve prerendered HTML to crawlers; serve SPA to users. Fallback when full SSR/SSG is not feasible (e.g. legacy SPA migration).
- How: Detect crawler user-agent; route to prerender service (e.g. Prerender.io) or headless render
- When: JavaScript-heavy sites; migration period; product/docs with CSR
- Note: Google permits this; prerendered content should match user experience
Show full SKILL.md (288 more words)Show less
Crawler Behavior
| Crawler | JavaScript | Content in initial HTML |
|---|---|---|
| Googlebot | Renders JS (Chrome); may have multi-day queue | Full weight; SSR/SSG preferred |
| AI crawlers (GPTBot, ClaudeBot, PerplexityBot) | Do not execute JS | Required—CSR content invisible |
| Bingbot | Renders JS | Same as Googlebot |
AI crawlers: ~28% of Googlebot's crawl volume. Critical content (articles, meta, nav) must be in initial HTML. See site-crawlability for AI crawler optimization; generative-engine-optimization for GEO.
Component-Level: Content in Initial HTML
Google does not simulate user clicks (tabs, carousels, "Load more"). Content loaded via AJAX or on interaction is not discoverable.
| Component | Requirement | Implementation |
|---|---|---|
| Tabs / Accordion | All tab content in DOM at load | Server-render; use <details>/<summary> or CSS show/hide |
| Carousel | All slides in initial HTML | Server-render; CSS/JS for show/hide only |
| Hero | Headline, CTA, LCP image in HTML | No JS-only rendering |
| Navigation | All nav links in first paint | No JS-injected menus for critical links |
Recommendation: Server-render (SSR/SSG) all critical content; use JS only for interaction (show/hide, animation). Content loaded on click = not indexed.
Decision Guide
| Content type | Rendering | Reason |
|---|---|---|
| Blog, docs, marketing | SSG or ISR | Best SEO; fast; static |
| Product, news, dynamic | SSR | Fresh content; crawler-ready |
| Dashboard, account | CSR | No SEO; auth required |
| Legacy SPA | Dynamic rendering | Bridge until SSR/SSG migration |
Output Format
- Current setup: SSG, SSR, CSR, or hybrid
- Recommendation: By page type
- Component checks: Tabs, carousel, nav—content in initial HTML?
- References: Next.js Rendering, Vercel SSR vs SSG
Related Skills
- site-crawlability: AI crawler optimization; SSR for critical content; URL management
- generative-engine-optimization: GEO; AI crawlers don't execute JS
- core-web-vitals: LCP; SSR/SSG for above-fold; client-side hurts LCP
- mobile-friendly: Mobile-first indexing; content parity
- tab-accordion: Content in DOM at load; server-render tabs
- carousel: Content in initial HTML; server-render slides
- hero-generator: Hero in initial HTML; avoid JS-only
- navigation-menu-generator: Nav in first paint; no JS-only menus
© kostja94, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/seo/technical/rendering-strategies of kostja94/marketing-skills.
Open the folder on GitHubat commit 8dd89c5
Compare with similar skills
Rendering Strategies next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Rendering Strategies this skillkostja94/marketing-skills | 1k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Web Scrapingplatonai/Browser4 | 1.2k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Selenium Opinion Crawler123321kk/opinion-agent-ultimate | 107 | — | ~631 | Automated safety check: Pass | None | |
| Chrome Devtoolseinverne/dotfiles | 121 | 1 repos | ~1.6k | Automated safety check: Notes | Apache-2.0 | |
| Docs Managementxiaoyuge886/aigc | 198 | — | ~7.8k | Automated safety check: Notes | MIT | |
| Meowhub Browserzhaojiaqi/MeowHub | 111 | — | ~1.6k | Automated safety check: Pass | GPL-3.0 |
Similar skills
Selenium Opinion Crawler
123321kk/opinion-agent-ultimate
browser-based page capture and text extraction for public-opinion research.
Chrome Devtools
einverne/dotfiles
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts.
Docs Management
xiaoyuge886/aigc
Single source of truth and librarian for ALL Claude official documentation.
Meowhub Browser
zhaojiaqi/MeowHub
Browse the web using Browserless.io cloud browser service. An agent skill from zhaojiaqi/MeowHub.
Add Parser
aropan/clist
Add, fix, or debug a Django standings parser in src/ranking/management/modules/, including Statistic.getstandings, leaderboard scraping, and offline regression fixtures.
More from kostja94/marketing-skills
All 102 skills in this repoGrokipedia Recommendations
kostja94/marketing-skills
When the user wants to add recommendations, links, or content to Grokipedia.
AI Traffic Tracking
kostja94/marketing-skills
When the user wants to track AI search traffic in GA4 or GSC.
Analytics Tracking
kostja94/marketing-skills
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions).
Brand Visual Generator
kostja94/marketing-skills
When the user wants to define, audit, or apply visual identity (typography, colors, spacing, design tokens, frontend aesthetics).
Canonical Tag
kostja94/marketing-skills
When the user wants to configure canonical URLs, fix duplicate content, or consolidate URL signals.
Content Strategy
kostja94/marketing-skills
When the user wants to plan content for SEO, create content calendar, or build topic clusters.
Related
Works with
Categories
Questions about Rendering Strategies
What does Rendering Strategies do?
When the user wants to choose or optimize rendering strategy for SEO. Rendering Strategies is an agent skill from kostja94/marketing-skills. When the user wants to choose or optimize rendering strategy for SEO.
When should I use Rendering Strategies?
Rendering Strategies fits situations like: wants to choose; optimize rendering strategy for SEO; the user mentions SSR; static rendering.
How do I install Rendering Strategies in Claude Code?
Run `npx skills add kostja94/marketing-skills --skill rendering-strategies -a claude-code`. Or copy the skill folder (skills/seo/technical/rendering-strategies in kostja94/marketing-skills) into .claude/skills/rendering-strategies in your project. Claude Code loads it when a task matches its description.
How do I install Rendering Strategies in Codex?
Run `npx skills add kostja94/marketing-skills --skill rendering-strategies -a codex`. Or copy the skill folder (skills/seo/technical/rendering-strategies in kostja94/marketing-skills) into .agents/skills/rendering-strategies in your project. Codex loads it when a task matches its description.
Can I use Rendering Strategies in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add kostja94/marketing-skills --skill rendering-strategies -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rendering-strategies, .gemini/skills/rendering-strategies, .github/skills/rendering-strategies and .opencode/skills/rendering-strategies in your project.
What does Rendering Strategies need to run?
SKILL.md names no scripts, command-line tools or credentials: Rendering Strategies is instructions for the agent only.
Does Rendering Strategies access the network?
SKILL.md names 2 domains. As links in the text: nextjs.org and vercel.com. This is read from the text; nothing was executed.
Is Rendering Strategies safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Rendering Strategies use?
Rendering Strategies is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Rendering Strategies use?
About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Rendering Strategies?
Skills that share tags, products or a category with Rendering Strategies: Web Scraping (platonai/Browser4, 1.2k stars), Selenium Opinion Crawler (123321kk/opinion-agent-ultimate, 107 stars), Chrome Devtools (einverne/dotfiles, 121 stars) and Docs Management (xiaoyuge886/aigc, 198 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Rendering Strategies?
kostja94 (a GitHub user) maintains it in kostja94/marketing-skills, which has 1,025 GitHub stars. The repository holds 102 skills in this directory. The repository was last updated on October 6, 2026.
Source: kostja94/marketing-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.