AwesomeWebpageMetaSkill
Build a local multimedia webpage project from a user topic, audience, language, style, and media preferences by framing requirements, researching, planning, acquiring media, generating files, packaging, validating, repairing, and delivering usage guidance.
Profile →npx skills add opensquilla/opensquilla --skill AwesomeWebpageMetaSkill --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Guides the agent to build a local multimedia webpage project from user inputs (topic, audience, language, style, media preferences). It frames requirements, conducts research, plans, acquires media, generates files, packages, validates, repairs, and delivers usage guidance as a packaged output.
How it works
- Requirement framing stage: analyzes user inputs and resolves a framed requirement set including topic, target_audience, output_language, visual_style, media_preferences, configured_output_dir, and constraints/risks.
- Project slug: produces a single filesystem-safe slug derived from the topic.
- Media confirmation: a sequence of user_input steps asking whether to include images, audio, video, and visual style, with default YES for images, audio, and video.
- Deep research: invokes the agent skill awesome-webpage-research to produce a short cited brief (3-5 page anchors) about the topic, based on the framed requirements and confirmed media choices.
- Page outline: creates a structural outline and media intent list (not final assets), detailing sections, narrative arc, visual style summary, and a list of media intents with slot_id, modality, placement, subject, prompt_hint, search_keywords, and load_bearing flags.
- The process uses the configured OpenRouter-based pipeline for page, image, audio, and video generation, with specific models and output_dir defined in the config.
When to use it
Triggers include phrases like "create awesome webpage" and "build multimedia webpage project" to initiate the meta-skill workflow.
What it can touch
- Filesystem: writes to output_dir (configured as {{ inputs.workspace_dir }}/awesome-webpage-output by default).
- Network: performs web search via web_search (via clawhub) and OpenRouter-based media generation for page, image, audio, and video.
- Commands/tools: uses the declared tool set (claude-code) and references skills like awesome-webpage-research and filesystem.
Caveats
- Risk level is high per metadata; dependencies on API keys and hosted models are required (OpenRouter models and API key).
- Licensing is Apache-2.0; includes components that may rely on external services with external costs and terms.
- Output relies on configured media strategy (search_first, modalities, and placeholders) and may require user confirmation at several stages.
# AwesomeWebpageMetaSkill Build a local multimedia webpage project from a topic, audience, language, style, and media preference request. Pipeline: 1. Requirement Framing 2. Deep Research 3. Page Outline (section structure + media intents; no filenames) 4. Media Acquisition (search / AIGC; producers emit `*_READY:` lines) 5. Media Assets Collect (deterministic path + existence check) 6. Webpage Source Generation 7. Deterministic Webpage Write 8. Deterministic Media Bind + Validation 9. Local Validation 10. Publish Complete Webpage Bundle 11. Delivery Guide Provider, OpenRouter model, API key, output directory, and media strategy are configuration-owned. The meta-skill may pass the config contract through the DAG, but individual steps must not invent those values.
What does the AwesomeWebpageMetaSkill skill do?
Build a local multimedia webpage project from a user topic, audience, language, style, and media preferences by framing requirements, researching, planning, acquiring media, generating files, packaging, validating, repairing, and delivering usage guidance.
How do I install it?
Run `npx skills add opensquilla/opensquilla --skill AwesomeWebpageMetaSkill --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From opensquilla/opensquilla, a repository with 6,515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.