「word」の検索結果

Use this skill when tool outputs exceed 2000 tokens, tasks span multiple conversation turns, sub-agents need to share state, context window is bloating, plans need to persist across summarization, terminal/log output needs selective querying, or when user mentions "offload context", "dynamic context discovery", "filesystem memory", "scratch pad", "reduce context bloat", or "just-in-time context loading".

日本語の概要は準備中です。原文の説明を表示しています。

App Store / Google Play のメタデータ最適化（ASO）を、4つの専門エージェントチームで実行するスキル。 キーワード調査、宣伝テキスト作成、競合分析、多言語ローカライゼーションの4観点から App Store 向けテキスト一式（タイトル、サブタイトル、キーワード、説明文、宣伝テキスト、What's New）を 生成し、最終レポート(MD)を出力する。多言語対応（日本語・英語+他言語）。 Use when: App Store の説明文を書きたい、ASO対策したい、キーワード選定したい、 宣伝文章を作りたい、App Store テキストを多言語化したい、What's New を書きたい。 Triggers: "ASO", "App Store", "宣伝文", "説明文", "キーワード", "サブタイトル", "What's New", "promotional text", "app description", "keyword optimization", "ストア掲載", "メタデータ", "アプリ紹介文", "Google Play", "多言語ASO"

Use when the deliverable is spoken words to be performed on camera or into a mic: video and podcast scripts, hooks, and CTAs for short-form (TikTok, Reels, Shorts), YouTube long-form, or podcast episodes. Triggers: "write me a reel about X", "I need a hook for my video", "script a 60-second video", "draft a podcast episode", "turn this idea into a script". For motion/timing/shot specs rather than the words, use motion-picture.

日本語の概要は準備中です。原文の説明を表示しています。

Deep receptive attention to extract intent beyond literal words. Maps active listening from counseling psychology to AI reasoning: clearing assumptions, attending to full signal, parsing multiple layers (literal, procedural, emotional, contextual, constraint, meta), reflecting understanding, noticing what is unsaid, and integrating the whole picture. Use when a user's request feels ambiguous, when context suggests something different from the literal words, when previous responses have missed the mark, or before beginning a large task where misunderstanding intent would waste significant effort.

日本語の概要は準備中です。原文の説明を表示しています。

Turn words with two readings into one confirmed ask. Use when the user's words admit two readings that would build different things.

日本語の概要は準備中です。原文の説明を表示しています。

Comprehensive market environment analysis and reporting tool. Analyzes global markets including US, European, Asian markets, forex, commodities, and economic indicators. Provides risk-on/risk-off assessment, sector analysis, and technical indicator interpretation. Triggers on keywords like market analysis, market environment, global markets, trading environment, market conditions, investment climate, market sentiment, forex analysis, stock market analysis, 相場環境, 市場分析, マーケット状況, 投資環境.

最强经理之争——把四位风格迥异的中国权益基金经理（易方达郑希、易方达张坤、易方达武阳、财通金梓才）放进同一个擂台， 用他们各自的全部公开观点原文 + 全部在管基金真实数据（季度持仓/净值/回撤/规模），做可溯源的对比与应用。能做： (1) 经理之争擂台——同口径比收益/最大回撤/回撤恢复/波动/Calmar/换手/规模，给"分场景谁更强、各自长短板"； (2) 行业/个股透视——给一个行业或股票，看四人谁持有/谁加减/谁更早布局，再用各自框架给"四个镜头"的综合看法； (3) 持仓/调仓追踪——逐季还原谁加仓、减仓、新进、清仓（季度颗粒度，公开数据能到的最细）； (4) 多视角参考——用四人的方法和真实操作，多角度帮你理解一只基金/一个行业、校准自己的判断（只呈现不同视角，不替你做决定、不构成建议）； (5) 溯源问答/方法讲解/风格化点评——引用某位经理本人原话答其观点，讲其投资框架，或用其口吻点评； (6) 言行对照——用真实持仓核对某位经理"说的"和"买的"。 (7) 进阶玩法——风格雷达+人设卡、本季调仓快报(共识/分歧)、言行一致性打分、观点时间机器(谁最早看到)、四人会诊(四种视角点评)、自定义擂台(把任意基金/经理拉进来比)。 When the user mentions 最强经理之争 / 经理对比 / 谁更强 / 回撤谁控得好 / 张坤/郑希/武阳/金梓才 / 景气轮动 vs 买入持有 / 风格雷达 / 人设 / 谁最早布局 / 言行一致 / 四人会诊 / 把某基金加进来比， asks who holds a sector or stock, wants 调仓追踪/调仓快报, a 风格化点评, words-vs-holdings, a style radar/persona, an opinion timeline, or to apply their methods to a fund/sector ——use this skill, even without the word "skill", even if the topic isn't in a corpus (fall back to that manager's method). 引用忠于原文、不杜撰；原话/推演/需核实分清；季度颗粒度非逐笔；研究学习辅助，非投资建议。

日本語の概要は準備中です。原文の説明を表示しています。

Use when sending transactional emails (welcome messages, order confirmations, password resets, receipts), notifications, or bulk emails via Resend API. Triggers on "send email", "transactional email", "welcome email", "Resend API", "password reset email", "order confirmation", "receipt email", "notification email", "bulk email send".

日本語の概要は準備中です。原文の説明を表示しています。

Uses OpenSEO as the measured SEO data plane for keyword volume and difficulty, SERPs, ranked keywords, backlinks, local SEO, rank tracking, Search Console, GA4, and site audits. Use for measured SEO metrics, indexing evidence, organic analytics, local rankings, backlink profiles, or rank trackers. Prefer OpenSEO over guessed metrics when connected; otherwise continue with qualitative web research and mark numeric metrics unknown.

日本語の概要は準備中です。原文の説明を表示しています。

Deep-dive ONE competitor's organic footprint — exact ranking keywords and URLs, content themes, backlink profile, and exploitable gaps — with findings written into brand/competitors.md. Use this skill when the user names a competitor and wants to know what to learn from them, counter, or outrank, including head-to-head comparisons against the user's own domain. For market-level mapping first, use openseo-competitive-landscape. Triggers: "analyze competitor", "competitor keywords", "competitor backlinks", "beat <competitor>", "competitor seo teardown".

日本語の概要は準備中です。原文の説明を表示しています。

Scaffold a new Tip in the ai-product-dev-tips repository following the existing directory/format conventions, and register its link in the root README.md. Use this whenever the user wants to add, create, or write a new Tip in this repo — e.g. "nlp_processing に〜の Tip を追加して", "新しい Tips を作って", "〜の解説 Tip を書いて", "this repo に〜のネタを追加". It picks the right category and next sequential number, matches the README format of nearby Tips, generates code scaffolding (Dockerfile / requirements.txt / *_cpu.sh / *_gpu.sh / *.py) only when the Tip needs runnable code, and inserts the link into the correct <details> section of the root README. Trigger this even if the user doesn't say the word "skill" — any request to add a new entry to this Tips collection should use it.

Use whenever a Word document (.docx) in the workspace is to be written, filled in, edited or commented on and the office_edit tool is available: the user watches your edits appear live in the file pane, under your name, and may edit beside you. Covers drafting a new document section by section, revising one, re-wording, tables, lists, charts, pictures and comment threads. Use the docx skill only when the office tools are not available.

日本語の概要は準備中です。原文の説明を表示しています。

Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop. Use for documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, and API guides. Also use when the user says "STE", "Simplified Technical English", "ASD-STE100", "de-slop", "make this readable", "write for non-native readers", or asks for docs that translate well. Enforces the standard's 53 rules: 20/25-word sentence limits, one word one meaning, simple tenses, active voice, condition before command.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when users want to build, edit, or design pages and layouts on Divi 5 WordPress sites. Triggers include creating landing pages, hero sections, testimonial cards, pricing tables, feature grids, blog listing pages with post loops and pagination; adding or modifying sections on existing pages by page ID; setting up design systems with tokens and presets; theme builder templates for headers, footers, and post/page body layouts; mega menus and site navigation; saving to or loading from the Divi library; auditing or cleaning up presets. Handles animations, hover effects, responsive design, and dynamic content. Also covers special effects like WebGL shader backgrounds and advanced CSS animations via the DiviOps Design Library plugin. Do NOT use for custom PHP/plugins, child theme development, standalone CSS authoring, SQL queries, WooCommerce configuration, SEO setup, standalone Three.js projects without WordPress, or non-Divi builders like Elementor.

日本語の概要は準備中です。原文の説明を表示しています。

Collect and analyze public X posts from keywords, hashtags, OR queries, domains, or known post URLs, then trace them to primary sources, official docs, GitHub repos, benchmarks, and reusable images. Use for launch-day reactions to a new model or product, event hashtags, keynote coverage, new-technology use cases, popularity research, or turning noisy X posts into a source-backed research note. Triggers: X で調べて, X の反応, ハッシュタグ調査, キーワードで X 検索, X 投稿からネタ探し. Not for posting or account operations on X.

Writes expert academic paper summaries for social science research, particularly political science and applied statistics. Use when asked to summarize, review, or create a reading summary of an academic paper, PDF, or research article. Accepts a file (PDF or text format) or a directory of papers. Produces a structured markdown summary — approximately 400–600 words — covering primary contributions, major questions and answers with point estimates, methods and data, and limitations and robustness. Includes BibTeX citation retrieved from Google Scholar and keyword metadata.

日本語の概要は準備中です。原文の説明を表示しています。

Converts LaTeX article-class .tex documents to Quarto .qmd format for multi-format publishing (HTML, PDF, Word). Use when asked to convert, port, migrate, or translate a .tex LaTeX file to Quarto; when porting an academic paper or manuscript from LaTeX to Quarto; when a .tex document needs to render to HTML, Word, or Typst PDF. Covers preamble → YAML front matter, section headings, text formatting, math, citations (natbib/biblatex), cross-references, figures, tables, lists, footnotes, hyperlinks, and special characters.

日本語の概要は準備中です。原文の説明を表示しています。

Cleans a Quarto (.qmd) file by replacing LaTeX holdovers with proper Quarto/Pandoc syntax so the document renders correctly to HTML, PDF (Typst/LaTeX), and Word. Fixes citations (\citep → [@key]), cross-references (\ref → @label), figures (\includegraphics → markdown), tables, text formatting (\textbf → **bold**), inline math (\( \) → $ $), hyperlinks (\href → [text](url)), footnotes (\footnote → ^[]), list environments, section headings, and R Markdown chunk options (dot-style → #| YAML). Use when asked to clean, fix, modernize, or port a Quarto or R Markdown document; when LaTeX commands appear in a .qmd file; when a document fails to render to Word or Typst; or when citations/cross-references do not appear in non-LaTeX output.

日本語の概要は準備中です。原文の説明を表示しています。

"Implement TF-IDF scoring to measure term importance relative to a document corpus. Use this skill when the user needs to rank documents by keyword relevance, extract important terms from text, or build a basic search relevance engine — even if they say 'find relevant documents', 'keyword extraction', or 'term importance'.".

日本語の概要は準備中です。原文の説明を表示しています。

Execute lateral movement within Active Directory environments using credential material (NTLM hashes and Kerberos tickets) instead of plaintext passwords. Use this skill when engaging in red team operations or internal network penetration tests to expand access, bypass authentication portals, and achieve Domain Dominance without relying on crackable passwords.

日本語の概要は準備中です。原文の説明を表示しています。

Exploit insecure handling of the HTTP Host header to poison password resets, generate cache poisoning vectors, or bypass internal routing restrictions. Use this skill when web applications dynamically generate URLs, links, or redirects based on the arbitrary Host header value supplied by the client rather than relying on a static, trusted server configuration.

日本語の概要は準備中です。原文の説明を表示しています。

Exploit Active Directory environments using Pass-the-Hash (PtH). This skill details how to authenticate to remote systems using the NTLM hash of a user's password instead of the plaintext password, enabling lateral movement and privilege escalation without cracking hashes.

日本語の概要は準備中です。原文の説明を表示しています。

Create, inspect, and edit Word documents (`.docx`) with local code-execution tools. Use for document drafting, structured edits, tables, comments, and layout-sensitive Word deliverables.

日本語の概要は準備中です。原文の説明を表示しています。

Word document automation — generating, templating, and parsing .docx files — use when working with Word documents programmatically.

日本語の概要は準備中です。原文の説明を表示しています。