1,963 件 ・ 関連度順
概要と使いどころ
Govern discovery, eligibility, and submission of a plugin or skill to official directories, registries, marketplaces, and curated GitHub lists. Use when preparing or sending plugin listings, marketplace forms, directory PRs, or repository recommendations; require current policy evidence and a final human confirmation before every external submission.
日本語の概要は準備中です。原文の説明を表示しています。
Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.
日本語の概要は準備中です。原文の説明を表示しています。
Generates Angular code and provides architectural guidance. Trigger when creating projects, components, services, or HTTP communication, or for best practices on reactivity (signals, linkedSignal, resource, httpResource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, naming conventions, or CLI tooling.
日本語の概要は準備中です。原文の説明を表示しています。
Write minimal, accessible web UI without over-engineering, adapting to whatever stack the project uses — React, Vue, Svelte, Angular, web components, or plain HTML. Use this skill on every project and every task that writes or reviews markup or components, builds forms, adds interactive elements like buttons, dialogs, accordions, or tabs, or audits code for accessibility — even when the user never mentions accessibility, and even inside a framework, CMS, or design system. It's non-negotiable regardless of project type, stack, or deadline. About to reach for ARIA attributes, a dialog library, a focus-trap package, or a headless UI component? Use this skill first.
日本語の概要は準備中です。原文の説明を表示しています。
Apply semantic HTML/JSX and WAI-ARIA correctly and minimally. Apply when implementing any UI, especially forms, interactive components, or when accessibility is mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing, reviewing, or implementing Settings/Preferences for Apple-platform apps — what belongs in Settings vs Inspector/Toolbar, grouped forms, native controls, secure storage, launch at login, and destructive actions.
日本語の概要は準備中です。原文の説明を表示しています。
Transforms data into compelling visual narratives by applying narrative structure, annotation techniques, scrollytelling patterns, and honest framing to data journalism, presentations, and infographics. Use when creating data-driven articles or reports, designing infographics with narrative, building scrollytelling experiences, annotating charts to guide interpretation, or when user mentions data storytelling, presentation design, annotated chart, narrative visualization.
日本語の概要は準備中です。原文の説明を表示しています。
Use when an agent needs to drive a real Chrome window via opencli — inspect a page, fill forms, click through logged-in flows, or extract data ad-hoc. Covers the selector-first target contract, compound form fields, stale-ref handling, network capture, and the agent-native envelopes the CLI returns. Not for writing adapters — see opencli-adapter-author for that.
日本語の概要は準備中です。原文の説明を表示しています。
Route ordinary public-web information tasks to the correct Tavily CLI operation. Use when the task concerns publicly accessible webpages and needs web discovery, clean extraction, URL mapping, same-site crawling, or public-web-only research, but the exact Tavily operation is not yet clear or several operations must be sequenced. Prefer the specific leaf skill when intent is clear: tavily-search for discovery without a URL, tavily-extract for known URLs, tavily-map for URL/site-structure discovery, tavily-crawl for content from many pages on one site, tavily-research for cited multi-source synthesis, and tavily-dynamic-search for programmatic filtering with context isolation. Do not use for named social/community/media/career/code platforms, login or cookie-dependent content, platform-native discussions, or cross-platform collection; use Agent Reach there. Do not use for local files, Git operations, deployments, or ordinary code editing.
日本語の概要は準備中です。原文の説明を表示しています。
Discover ordinary public webpages with LLM-optimized Tavily search results. Use when no specific URL is known and the user needs a quick public-web lookup, articles, recent news, sources, or domain-filtered results. This is the default Tavily leaf for simple public-web discovery. Do not use when the user already supplied the target URL (use tavily-extract), wants URLs under one known site (tavily-map), wants many pages' content (tavily-crawl), needs a full cited synthesis (tavily-research), or needs named platforms, login state, platform-native content, or cross-platform collection (Agent Reach).
日本語の概要は準備中です。原文の説明を表示しています。
MUST USE when user wants to 调研/research/搜索/search/查/找/look up anything on the internet — e.g. 全网调研 X / 帮我调研一下 X / 查一下 X / 搜搜 X / 看看大家怎么评价 X / X 上有什么讨论 / research this topic。 Also MUST USE when user mentions any platform or shares any URL/链接: 小红书/xiaohongshu/xhs, Twitter/推特/X, B站/bilibili, Reddit, V2EX, LinkedIn/领英/招聘/求职/jobs, YouTube, GitHub code search, 小宇宙播客, 雪球/股票行情, RSS feeds, or any web URL. 13 platforms, multi-backend routing (OpenCLI / per-platform CLIs / APIs). Zero config for 6 channels. Run `agent-reach doctor --json` to see which backend serves each platform right now. NOT for: 写报告/数据分析/翻译等内容加工（本 skill 只负责从互联网获取内容）； 发帖/评论/点赞等写操作；已有专门 skill 的平台（先用专门 skill）。 【路由方式】SKILL.md 包含路由表和常用命令，复杂场景需按需阅读对应分类的 references/*.md。 分类：search / social (小红书/推特/B站/V2EX/Reddit) / career(LinkedIn) / dev(github) / web(网页/文章/RSS) / video(YouTube/B站/播客)。
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
日本語の概要は準備中です。原文の説明を表示しています。
GEO-first SEO analysis tool. Optimizes websites for AI-powered search engines (ChatGPT, Claude, Perplexity, Gemini, Google AI Overviews) while maintaining traditional SEO foundations. Performs full GEO audits, citability scoring, AI crawler analysis, llms.txt generation, brand mention scanning, platform-specific optimization, schema markup, technical SEO, content quality (E-E-A-T), and client-ready GEO report generation. Use when user says "geo", "seo", "audit", "AI search", "AI visibility", "optimize", "citability", "llms.txt", "schema", "brand mentions", "GEO report", or any URL for analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Brand mention and authority scanner for AI visibility. Analyzes brand presence across platforms that AI models rely on for entity recognition and citation decisions. Produces a Brand Authority Score (0-100) with platform-specific recommendations.
日本語の概要は準備中です。原文の説明を表示しています。
Implement project-consistent UI through page classification, bounded references, semantic tokens, skeleton-first delivery, and responsive screenshot QA. Use for frontend redesigns, dashboards, forms, settings, mobile pages, screenshot recreation, visual polish, or generic-looking generated UI.
日本語の概要は準備中です。原文の説明を表示しています。
INTERNAL sub-agent, not a user-facing skill. Performs context-isolated nine-dimension rubric scoring for cheat-score, cheat-predict, and cheat-bump. Accepts only script and rubric-note paths, returns strict JSON, and refuses post-publish evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the 文档/交付 role maintains client-facing project delivery document packages, especially Word/DOCX deliverables such as delivery lists, demo scripts, acceptance forms, change confirmations, quote notes, contract-adjacent materials, README/docs indexes, and internal handoff notes.
日本語の概要は準備中です。原文の説明を表示しています。
Explicit compatibility adapter for the collection's legacy PDF workflow and delivery conventions. Prefer the installed official PDF skill for generic PDF reading, generation, rendering and forms.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing, redesigning, or improving a frontend interface in Angular, React, or Blazor. Use for landing pages, dashboards, components, forms, and responsive layouts that must work mobile-first and then scale to desktop.
日本語の概要は準備中です。原文の説明を表示しています。
Use when auditing UI code for interface-guideline compliance (accessibility, forms, animation, images, performance, UX copy) and/or validating a deployed page against Lighthouse 95+ targets. Produces evidence-based findings (file:line + Lighthouse JSON) and turns confirmed pendencies into Draft SPECs via write-specs. Do NOT use to design/build UI from scratch (use design) or to fix findings inline — fixes go through the SPEC pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
Conduct reproducible web searches and decision-oriented research across official sites, search engines, news, papers, forums, social platforms, and public datasets. Use when Codex must investigate a person, organization, product, market, technical resource, reputation, career choice, or other current topic; compare candidates; verify claims; collect dated citations; distinguish facts from inference and anecdote; or write an evidence-backed research report.
日本語の概要は準備中です。原文の説明を表示しています。
Browse the web for any task — research topics, read articles, interact with web apps, fill forms, take screenshots, extract data, and test web pages. Use whenever a browser would be useful, not just when the user explicitly asks.
日本語の概要は準備中です。原文の説明を表示しています。
Browse the web for any task — research topics, read articles, interact with web apps, fill forms, take screenshots, extract data, and test web pages. Use whenever a browser would be useful, not just when the user explicitly asks.
日本語の概要は準備中です。原文の説明を表示しています。
Compose a comparison newsletter from Ahmad's OpenMark saves — A vs B vs C, side-by-side, table-driven. Use when Ahmad wants to compare tools, models, frameworks, approaches, or platforms across his saves. Trigger phrases include "compare", "X vs Y", "head to head", "which should I use", "differences between", "trade-offs between", "/newsletter-comparison". Output centers a markdown table with consistent columns, supports it with short prose blocks, ends with a clear recommendation.
日本語の概要は準備中です。原文の説明を表示しています。