Create evidence-aware, interactive visual explainers as self-contained offline HTML. Use when a user asks to explain a concept, repository module, engineering tradeoff, or incident with a diagram, walkthrough, ELI5 treatment, data/request trace, failure view, or teach-back. Do not use for a plain short answer, ordinary prose rewrite, generic website implementation, or unsupported claims presented as facts.
yizhiyanhua-ai/fireworks-open-eli5
Score58
How is this score calculated?
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Diagnostic and advisory skill for email deliverability problems. Use when a developer asks why emails are going to spam, not reaching the inbox, getting blocked, bouncing, or how to improve sender reputation — with or without a specified platform. Covers SendGrid-specific tooling: SPF, DKIM, DMARC, BIMI, IP warmup, list hygiene, bounce/spam rate thresholds, and Engagement Quality Score (SEQ). Do NOT use for Twilio Email (comms.twilio.com / Account SID + Auth Token) — use twilio-email-deliverability-advisor instead. Do NOT use for general email sending questions — use twilio-sendgrid-email-send (SendGrid) or twilio-email-deliverability-advisor instead.
Create a new scrap from a source (prompt, URL, or arbitrary markdown), update cross-links in related scraps, and run a sanity check. Use this when the user wants to add a scrap, summarize an article, save synthesized content to the wiki, or file back a Q&A result.
Guides users through discovering their database requirements, recommends a Google Cloud database based on a recommendation matrix, and assists in database creation. Use when a user asks 'What database service should I use?', 'Help me pick a database', or when a user wants to create a new database on Google Cloud. Don't use for general Google Cloud maintenance, managing existing databases, or database migrations.
Audit and rewrite an Instagram profile end-to-end for 2026: profile photo, searchable NAME field weighted with a keyword, @handle, bio (150 chars: value plus topic plus proof), goal-matched link, category label, story highlights, the first-9 grid, and up to 3 pinned posts. Triggers on "review my Instagram profile", "fix my bio", "optimize highlights", "profile audit". The whole follow decision happens on the profile header. Not for writing captions (use ig-caption-writer).
Report artifact output-format contract: decide the format by who consumes the artifact, not by which skill produces it — human-read reports get a derived HTML beside their Markdown source, machine-consumed artifacts stay Markdown/JSON, dual-read artifacts keep their own format (Markdown or JSON) as the single source. Holds the one product registry the whole library routes through and the one shared renderer hosts call instead of hand-writing HTML. Triggers — 「报告格式」「产物格式」「报告输出契约」「给人看的报告」「报告写 HTML」「HTML 报告」「机器看的写 Markdown」 / report output format, report artifact format, report HTML, derived HTML view. Do NOT use as a general Markdown-to-HTML converter, for concept explanations (explain-clearly owns those pages), or for queue acceptance views (goal-driven-queue owns those).
Challenge Course — Skill especializada para design, implementação e avaliação de programas de desafio e aventura, focando em desenvolvimento de equipes e liderança.
Two-mode skill for structured software project development using the harness engineering pattern.
**Mode 1 — Project Architect** (`/architect` or starting a new project): Interview the user about their project, guide them through architecture and technology decisions (language, framework, storage, build tooling, CI/CD, testing), record Architecture Decision Records, then generate three files: CLAUDE.md (agent harness), docs/ARCHITECTURE.md, and a phased docs/PROJECT_STATUS.md with implementation phases, per-phase file lists, test requirements, and done criteria.
**Mode 2 — Build Next** (`/build-next` or "implement the next phase"): Read docs/PROJECT_STATUS.md, find the first incomplete (⬜) phase, implement exactly that one phase, run tests, verify they pass, then update the status document. Enforce: one phase per session, tests must pass before marking complete, conventional commit message.
Use this skill whenever: the user is starting a greenfield project and needs architecture guidance; the user says "/architect"; the user says "/build-next" or "implement the next phase" or "work on the next phase"; the user references PROJECT_STATUS.md and wants to make progress; the user wants to break a project into implementation phases.
Perform a structured audit of a codebase covering security, code quality, performance, dependencies, architecture, and testing hygiene, then produce a prioritized findings report. Use this skill whenever the user asks for a code review, code audit, security review, codebase assessment, "look over this repo", "what's wrong with this codebase", legacy-code triage, pre-acquisition technical due diligence, or any request to systematically evaluate the health of a project. Trigger even when the user is casual ("can you eyeball my repo?") — this skill imposes the structure that ad-hoc review misses. This skill audits a whole repository at a point in time — for reviewing a diff or PR use the built-in code-review skill; for security checks on pending changes use security-review.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
Structural decision trees for container types, form states, table layouts, and page-level patterns. Use before vois-tokens. Routes to righter skill for all microcopy (labels, errors, buttons, helpers). Use when building pages, forms, features, workflows.
Simulate 5 buyer personas reading any landing page, email, ad, sales page, proposal, or offer, section by section, then report who would buy, who would bounce, where friction clusters, and what to fix first. Generates a visual HTML report with conversion score, buyer-by-buyer walkthroughs, section-by-section friction map, prioritized fixes, and rewrite suggestions. MANDATORY TRIGGERS: 'buy or bounce this', 'run buy or bounce', 'simulate buyers', 'buyer sim this', 'would they buy this', 'who would bounce', 'test this before launch'. STRONG TRIGGERS: 'review this like a buyer', 'where would people drop off', 'why is this not converting', 'pressure test this landing page', 'simulate conversion objections'. Do NOT trigger on requests for brand voice editing, general proofreading, or analytics interpretation after a live launch.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
How is this score calculated?
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
How is this score calculated?
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Score
58
How is this score calculated?
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Score58
How is this score calculated?
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
58
How is this score calculated?
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Score
58
How is this score calculated?
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.