Loading...
Loading...
Found 757 Skills
Main entry for WeChat Official Account content: completes topic selection, material collection, writing, and review, and independently adds image matching, typesetting, or draft box publishing as requested by users. It is also responsible for distributing style settings, learning & revision, data review, and multi-platform rewriting to the corresponding wewrite-* modules. Trigger keywords: 公众号 (Official Account), 微信文章 (WeChat article), 微信推文 (WeChat tweet), 草稿箱 (draft box), 微信排版 (WeChat typesetting), 写公众号 (write Official Account article), 写一篇 (write an article). General articles, blogs, emails, short videos, and website SEO do not trigger this skill.
Score any website the way an Awwwards jury would, from evidence alone. Screenshots every page type on desktop, a throttled phone and reduced motion, measures LCP, CLS, FPS, axe, keyboard focus and hover feedback, audits SEO and metadata, then a fresh critic that never sees the code scores Design, Usability, Creativity, Content and the six developer areas, with a ranked fix list. Use when someone asks to review, critique, score, rate or roast a website, portfolio or landing page, asks whether a site is good enough for Awwwards or Site of the Day, or wants design QA of a live URL or a local build. Not for building or redesigning a site; use /awwwards for that.
Use when a site needs a combined accessibility and responsive-quality review: alt text, headings, keyboard use, focus, contrast, form labels, reduced motion, phone and tablet layouts, overflow, tables, dialogs, touch targets, sticky bars. It runs one shared runtime pass and routes to the accessibility and mobile specialists. Do not use it to claim WCAG conformance, to replace assistive-technology testing, or for backend or SEO work.
Use to make social content discoverable through SEARCH across social platforms — the social-SEO / keyword-discovery skill. Run when the user says "social SEO," "get found in search," "TikTok SEO," "YouTube SEO," "keywords for social," "searchable captions," or wants search across platforms rather than just the feed. For single-platform depth, route "Instagram SEO" to instagram-seo and Pinterest asks to pinterest-seo; this skill owns the cross-platform framework. Reads brand-profile and audience first. All platforms are search engines; keywords, not hashtags, are the lever. Covers per-platform indexed surfaces, keyword research via autocomplete + native analytics (never fabricates volumes), the triple-mention technique, topical clusters, and the profile as a search asset. Routes hashtags to hashtag-strategy; hands the AI-search/LLM-citation (GEO) layer to ai-search-optimization. Measures via native search insights, not WoopSocial analytics.
Audit Core Web Vitals & page performance — measure LCP, INP, and CLS against p75 field thresholds, diagnose render-blocking resources, unoptimized images, and layout-shift sources, and produce prioritized, advisory-only remediation guidance. Module M15. Feeds the Search SEO score (heavily) and the AI Visibility score (minimally).
Deploy to Cloudflare Workers, Netlify, Vercel, Node.js/Docker, Bun, Railway. Selective SSR (ssr option per route), SPA mode, static prerendering, ISR with Cache-Control headers, SEO and head management.
Build award-caliber websites from a one-line prompt such as "make me a portfolio, my name is Ana". Uses the bar of sites that win Awwwards Site of the Day as a quality standard. Covers concept, art direction, typography, motion choreography, WebGL, page transitions, real content, SEO, accessibility and performance, then visual QA in a browser. Next.js by default, Astro for animation-heavy static showcases, or the stack the project already uses. Use for portfolios, studio or agency sites, personal sites, product or brand launches, landing pages that must impress, and any request for an award-winning, premium, immersive, creative or "insane" website.
Load when operating a Quilium CMS site that already runs — writing or editing content blocks, managing pages, uploading media, adding items to a collection, translating, reordering navigation, auditing or filling SEO metadata, importing from a file. Covers the working discipline of a content session and the mistakes that corrupt data without raising an error. Triggers on "add a page", "edit this block", "add a field to the form", "change the form validation", "the form email", "upload an image", "add an article", "translate this", "publish this", "fill the meta descriptions", "import this spreadsheet", "reorder the menu". For structural work — YAML types, routes, templates, a site that doesn't exist yet — use quilium-builder instead.
Audit and improve website discoverability across traditional search, answer engines, and generative search. Use for technical SEO, on-page content, structured data, question and entity architecture, AI citations, crawler controls, agent-readable content, and reproducible visibility measurement. Do not use for only copy-editing, writing, CMS operations, or generic AI marketing claims without a defined search surface and verification plan.
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitor-alternatives. For sales-specific battle cards, see sales-enablement.
Master Next.js 14+ App Router with Server Components, streaming, parallel routes, and advanced data fetching. Use when building Next.js applications, implementing SSR/SSG, or optimizing React Server Components.
Accuranker integration. Manage data, records, and automate workflows. Use when the user wants to interact with Accuranker data.