Pricing Page
boraoztunc/skills
A skill your agent uses when designing or rewriting a high-converting SaaS pricing page (structure, plan design, copywriting, SEO/AEO, FAQs, layout patterns, experiments).
Edits, updates, rewrites, or adds content on the ComfyUI template site pages.
Install Editing Site Content
$ npx skills add Comfy-Org/workflow_templates --skill editing-site-content -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Comfy-Org/workflow_templates editing-site-content --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/Comfy-Org/workflow_templates.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/editing-site-content .claude/skills/editing-site-content && 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 "editing-site-content" agent skill from https://github.com/Comfy-Org/workflow_templates/tree/main/.claude/skills/editing-site-content into .claude/skills/editing-site-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "editing-site-content", 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/Comfy-Org/workflow_templates/tree/main/.claude/skills/editing-site-contentType 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 Comfy-Org/workflow_templates --skill editing-site-content -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Comfy-Org/workflow_templates editing-site-content --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Comfy-Org/workflow_templates.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/editing-site-content .agents/skills/editing-site-content && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "editing-site-content" agent skill from https://github.com/Comfy-Org/workflow_templates/tree/main/.claude/skills/editing-site-content into .agents/skills/editing-site-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "editing-site-content", 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 Comfy-Org/workflow_templates --skill editing-site-content -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Comfy-Org/workflow_templates editing-site-content --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Comfy-Org/workflow_templates.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/editing-site-content .cursor/skills/editing-site-content && 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 "editing-site-content" agent skill from https://github.com/Comfy-Org/workflow_templates/tree/main/.claude/skills/editing-site-content into .cursor/skills/editing-site-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "editing-site-content", 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/Comfy-Org/workflow_templates.git --path .claude/skills/editing-site-content--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 Comfy-Org/workflow_templates --skill editing-site-content -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Comfy-Org/workflow_templates editing-site-content --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Comfy-Org/workflow_templates.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/editing-site-content .gemini/skills/editing-site-content && 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 "editing-site-content" agent skill from https://github.com/Comfy-Org/workflow_templates/tree/main/.claude/skills/editing-site-content into .gemini/skills/editing-site-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "editing-site-content", 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 Comfy-Org/workflow_templates editing-site-contentInstalls 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 Comfy-Org/workflow_templates --skill editing-site-content -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Comfy-Org/workflow_templates.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/editing-site-content .github/skills/editing-site-content && 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 "editing-site-content" agent skill from https://github.com/Comfy-Org/workflow_templates/tree/main/.claude/skills/editing-site-content into .github/skills/editing-site-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "editing-site-content", 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 Comfy-Org/workflow_templates --skill editing-site-content -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Comfy-Org/workflow_templates editing-site-content --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Comfy-Org/workflow_templates.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/editing-site-content .opencode/skills/editing-site-content && 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 "editing-site-content" agent skill from https://github.com/Comfy-Org/workflow_templates/tree/main/.claude/skills/editing-site-content into .opencode/skills/editing-site-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "editing-site-content", 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
editing-site-content- GitHub stars
- 1.3k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 805 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
Edits, updates, rewrites, or adds content on the ComfyUI template site pages.
- Works in 4 steps: Identify the Template → Check for Existing Override → Make the Changes → …
- Asked to: change text
- SKILL.md covers How It Works, Step 1: Identify the Template, Step 2: Check for Existing… and Step 3: Make the Changes, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Editing Site Content is an agent skill from Comfy-Org/workflow_templates. Edits, updates, rewrites, or adds content on the ComfyUI template site pages. Creates override JSON files so changes survive AI regeneration. Use when asked to: change text, update descriptions, fix wording, rewrite content, edit a template page, update SEO, add FAQ, change steps, modify use cases, update copy, fix typos, add sections, customize a page, write marketing copy, improve messaging, tweak headlines, adjust tone, replace placeholder text, personalize content, or manage any template page content…
Its SKILL.md is about 1.8k 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 Sales & Support, covering Programmatic SEO, Diffusion and image models and Copywriting. It works with ComfyUI. The repository describes itself as: ComfyUI template workflows. The licence is MIT.
When your agent uses it
- Asked to: change text
- Update descriptions
- Rewrite content
- Edit a template page
Example prompts
- “/editing-site-content”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 8be1f8c. 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 (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Editing Site Content loads about 1.8k tokens when it runs. Until then it costs about 190 tokens; SKILL.md has 805 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 Comfy-Org/workflow_templates at commit 8be1f8c, republished under its MIT licence (© Comfy-Org). 805 words, ~1,763 tokens.
Download SKILL.mdSave it as
.claude/skills/editing-site-content/SKILL.md (or your agent's skills folder).- name
- editing-site-content
- description
- Edits, updates, rewrites, or adds content on the ComfyUI template site pages. Creates override JSON files so changes survive AI regeneration. Use when asked to: change text, update descriptions, fix wording, rewrite content, edit a template page, update SEO, add FAQ, change steps, modify use cases, update copy, fix typos, add sections, customize a page, write marketing copy, improve messaging, tweak headlines, adjust tone, replace placeholder text, personalize content, or manage any template page content. Triggers on: edit content, change description, update page, fix text, rewrite, add FAQ, update steps, site content, template text, page copy, SEO description, marketing copy, content manager, update wording, customize template.
Editing Site Content
You are helping a content manager or creative edit template pages on the ComfyUI workflow template site. They should never need to understand JSON, code, or the build pipeline — you handle all of that.
How It Works
Template pages on the site have AI-generated content. To override that content with human-written copy, you create a JSON file in site/overrides/templates/{template-name}.json. The build pipeline merges these overrides on top of AI output, preserving human edits across regenerations.
Step 1: Identify the Template
The user may refer to a template by its display name, a partial name, a description of what it does, or a URL slug.
To find the right template:
- Search
templates/index.jsonfor the template. It contains all templates grouped into bundles withname,title, anddescriptionfields. - The
namefield (e.g.,templates-sprite_sheet) is the filename key used for the override file. - If the user's request is ambiguous, show them matching candidates with their titles and descriptions and ask them to confirm.
Example: User says "the sprite sheet one"
→ Search index.json → find templates-sprite_sheet with title "Sprite Sheet Generator"
→ Confirm with user: "I found Sprite Sheet Generator — is that the one you mean?"
Step 2: Check for Existing Override
Read site/overrides/templates/{template-name}.json if it exists. If it does, you'll be editing the existing override. If not, you're creating a new one.
Also read the current generated output at site/src/content/templates/{template-name}.json (if it exists) to see what the current live content looks like. Show the user what's currently there before making changes.
Step 3: Make the Changes
Overridable Fields
These are the fields you can set in an override file:
| Field | Type | What It Is |
|---|---|---|
extendedDescription | string | The main long-form description shown on the template detail page. Supports plain text. |
metaDescription | string | SEO meta description shown in search results. Keep to 150-160 characters. |
howToUse | string[] | Step-by-step instructions. Each array item is one step. |
suggestedUseCases | string[] | List of use cases or scenarios where this template shines. |
faqItems | Array<{question, answer}> | FAQ section. Each item has a question string and an answer string. |
humanEdited | boolean | Set to true to fully replace AI content and prevent regeneration. |
Writing the Override File
Create or update site/overrides/templates/{template-name}.json:
- Only include fields the user wants to change. Omitted fields fall back to AI-generated content.
- Always set
"humanEdited": truewhen the user is providing complete custom content for one or more fields. This prevents the AI from overwriting their work. - Partial tweaks (e.g., fixing a typo in one field) can omit
humanEditedif the user wants AI to continue generating the other fields. But if in doubt, set it totrue— it's safer.
Override File Format
{
"extendedDescription": "Your custom description here...",
"metaDescription": "Short SEO-friendly description under 160 chars",
"howToUse": [
"Step 1: Do this first",
"Step 2: Then do this",
"Step 3: Finally do this"
],
"suggestedUseCases": [
"Game development sprite animation",
"Social media character assets"
],
"faqItems": [
{
"question": "What image formats are supported?",
"answer": "PNG and WebP are supported as input formats."
}
],
"humanEdited": true
}Step 4: Confirm with the User
After writing the file, show the user a readable summary of what changed:
- Which template was updated
- Which fields were changed
- A preview of the new content in plain English (not raw JSON)
Show full SKILL.md (328 more words)Show less
Guidelines for Content Quality
When helping the user write content:
- extendedDescription: Write in a clear, engaging tone. Explain what the template does, what makes it special, and what output to expect. 2-4 paragraphs.
- metaDescription: Must be 150-160 characters. Include the primary keyword/template purpose. Write as a compelling search result snippet.
- howToUse: Write actionable steps. Start each step with a verb. Be specific about what the user does and what happens. 4-8 steps is ideal.
- suggestedUseCases: Be specific and practical. Think about the end user's actual projects. 3-6 use cases.
- faqItems: Answer real questions a user would have. Address common concerns about requirements, compatibility, or output quality. 3-5 items.
Common User Requests — How to Handle Them
| User Says | What to Do |
|---|---|
| "Change the description to say X" | Update extendedDescription |
| "Fix the SEO / meta description" | Update metaDescription (keep under 160 chars) |
| "Update the steps" / "Change how-to" | Update howToUse array |
| "Add a FAQ" / "Add a question" | Add to or create faqItems array |
| "Add a use case" | Add to suggestedUseCases array |
| "Rewrite everything for this template" | Update all fields, set humanEdited: true |
| "Make it sound more professional / casual / fun" | Rewrite relevant fields with the requested tone |
| "What does this page currently say?" | Read the generated output file and show them |
| "List all templates" / "What templates are there?" | Search templates/index.json and list them with titles |
| "Undo my changes" / "Go back to AI content" | Delete the override file from site/overrides/templates/ |
| "Remove just my FAQ override" | Remove only the faqItems key from the override JSON |
Important Rules
- Never edit files in
site/src/content/templates/— those are generated and git-ignored. Only edit files insite/overrides/templates/. - Never modify the build scripts, content schema, or pipeline code for a content change.
- Always use the template's
namefield (e.g.,templates-sprite_sheet) as the override filename, not the display title. - Preserve existing override fields when adding new ones — read the file first, merge your changes.
- The override directory is
site/overrides/templates/— it is checked into git and survives rebuilds.
© Comfy-Org, 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 .claude/skills/editing-site-content of Comfy-Org/workflow_templates.
Open the folder on GitHubat commit 8be1f8c
Compare with similar skills
Editing Site Content 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 |
|---|---|---|---|---|---|---|
| Editing Site Content this skillComfy-Org/workflow_templates | 1.3k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Pricing Pageboraoztunc/skills | 397 | 2 repos | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Iibzanllp/infinite-image-browsing | 1.4k | — | ~3.3k | Automated safety check: Pass | MIT | |
| 9Router Image Generationdecolua/9router | 30k | — | ~830 | Automated safety check: Pass | MIT | |
| Comfyui Skill OpenclawHuangYuChuh/ComfyUI_Skills_OpenClaw | 413 | — | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| Character Refseternityspring/shuohao-skills | 4.3k | — | ~1.7k | Automated safety check: Warn | Apache-2.0 |
Similar skills
Iib
zanllp/infinite-image-browsing
Interact with IIB (Infinite Image Browsing) service for searching, browsing, tagging, and organizing AI-generated images.
9Router Image Generation
decolua/9router
Generates images through a 9Router gateway's image endpoint, with model discovery, the request fields and per-provider quirks for OpenAI, Gemini, MiniMax and others.
Comfyui Skill Openclaw
HuangYuChuh/ComfyUI_Skills_OpenClaw
Run registered ComfyUI workflows through the fast comfyui-skill CLI, and use the official local Comfy MCP for live template, node, model, validation, and orchestration capabilities.
Character Refs
eternityspring/shuohao-skills
给任何故事里的角色真出参考图（小说改编、自己原创的故事、单独设计一个角色都行，不需要小说原文）： 一段话描述角色，拆成分层字段、补全后确认， 先出一张正面全身锚点，其余视图（大头照、90° 侧面、背面、细节、45° 大头照）都只参考这张锚点， 按需分档出图。每张图带标识、可单独重出，重出后自动标出哪些图过期。
ComfyUI Custom Node Builder
ConstantineB6/comfy-pilot
Helps an agent write ComfyUI custom nodes in Python, including wrapping an existing script, mapping data types and handling image batches.
More from Comfy-Org/workflow_templates
All 10 skills in this repoImporting Subgraphs
Comfy-Org/workflow_templates
Imports and registers subgraph blueprints into the ComfyUI workflowtemplates repository.
Managing Bundles
Comfy-Org/workflow_templates
Manages template bundles, categories, and ordering in the ComfyUI template repository.
Managing MCP Index
Comfy-Org/workflow_templates
Builds and maintains templates/index.mcp.json for Comfy Cloud MCP tools.
Managing Releases
Comfy-Org/workflow_templates
Manages releases for this repository: how version bumps, PyPI publishing, and GitHub releases work.
Managing Templates
Comfy-Org/workflow_templates
Manages ComfyUI workflow templates end-to-end: add new templates and rename existing ones (files, index metadata, bundles, i18n, package sync).
Managing Thumbnails
Comfy-Org/workflow_templates
Manages thumbnail and preview images for ComfyUI workflow templates.
Related
Works with
Questions about Editing Site Content
What does Editing Site Content do?
Edits, updates, rewrites, or adds content on the ComfyUI template site pages. Editing Site Content is an agent skill from Comfy-Org/workflow_templates. Edits, updates, rewrites, or adds content on the ComfyUI template site pages.
When should I use Editing Site Content?
Editing Site Content fits situations like: asked to: change text; update descriptions; rewrite content; edit a template page.
How do I install Editing Site Content in Claude Code?
Run `npx skills add Comfy-Org/workflow_templates --skill editing-site-content -a claude-code`. Or copy the skill folder (.claude/skills/editing-site-content in Comfy-Org/workflow_templates) into .claude/skills/editing-site-content in your project. Claude Code loads it when a task matches its description.
How do I install Editing Site Content in Codex?
Run `npx skills add Comfy-Org/workflow_templates --skill editing-site-content -a codex`. Or copy the skill folder (.claude/skills/editing-site-content in Comfy-Org/workflow_templates) into .agents/skills/editing-site-content in your project. Codex loads it when a task matches its description.
Can I use Editing Site Content 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 Comfy-Org/workflow_templates --skill editing-site-content -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/editing-site-content, .gemini/skills/editing-site-content, .github/skills/editing-site-content and .opencode/skills/editing-site-content in your project.
What does Editing Site Content need to run?
SKILL.md names no scripts, command-line tools or credentials: Editing Site Content is instructions for the agent only.
Does Editing Site Content access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Editing Site Content 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 Editing Site Content use?
Editing Site Content 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 Editing Site Content use?
About 1.8k tokens (SKILL.md is roughly 7.1k 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 Editing Site Content?
Skills that share tags, products or a category with Editing Site Content: Pricing Page (boraoztunc/skills, 397 stars), Iib (zanllp/infinite-image-browsing, 1.4k stars), 9Router Image Generation (decolua/9router, 30k stars) and Comfyui Skill Openclaw (HuangYuChuh/ComfyUI_Skills_OpenClaw, 413 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Editing Site Content?
Comfy-Org (a GitHub organization) maintains it in Comfy-Org/workflow_templates, which has 1,270 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 9, 2026.
Source: Comfy-Org/workflow_templates on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.