「hr」の検索結果

Searches Threads posts by keyword or hashtag and returns matching posts with engagement metrics, extracted from SSR-embedded JSON. Use when user asks to search Threads posts, find Threads content by topic, scrape Threads search results, collect Threads posts about a keyword, monitor Threads hashtag activity, pull Threads posts mentioning a term, gather Threads content by hashtag, search for posts on Threads, extract Threads search feed, get trending posts on Threads, find Threads discussions about a subject, or fetch recent or top Threads posts by keyword.

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

Discovers Threads user accounts by keyword, extracting profile data including username, display name, verification status, biography, and follower count. Use when user asks to find Threads accounts, search Threads profiles, discover Threads users by keyword, look up Threads creators, find influencers on Threads, search for people on Threads, get Threads user details, collect Threads profile information, find accounts related to a topic on Threads, search Threads for accounts by name or keyword, or enumerate Threads users matching a search term.

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

Guides migration of .NET Framework Thread.Abort usage to cooperative cancellation in modern .NET. USE FOR: modernizing code that calls Thread.Abort, catching ThreadAbortException, replacing Thread.ResetAbort, replacing Thread.Interrupt for thread termination, resolving PlatformNotSupportedException or SYSLIB0006 after retargeting to .NET 6+, migrating ASP.NET Response.End or Response.Redirect(url, true) which internally call Thread.Abort. DO NOT USE FOR: code that only uses Thread.Join, Thread.Sleep, or Thread.Start without any abort, interrupt, or ThreadAbortException usage — these APIs work identically in modern .NET and need no migration. Also not for projects staying on .NET Framework, or Thread.Abort usage inside third-party libraries you do not control.

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

Write viral Twitter/X threads and Reddit posts with proven structures, hooks, and engagement tactics. Includes templates for story threads, listicle threads, contrarian takes, tutorials, and case studies. Can post directly to Reddit. Trigger phrases: "write a thread", "Twitter thread", "X thread", "viral thread", "thread writer", "tweetstorm", "thread template", "thread about", "turn this into a thread", "reddit post", "write a reddit post".

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

Guides migration of .NET Framework Thread.Abort usage to cooperative cancellation in modern .NET. USE FOR: modernizing code that calls Thread.Abort, catching ThreadAbortException, replacing Thread.ResetAbort, replacing Thread.Interrupt for thread termination, resolving PlatformNotSupportedException or SYSLIB0006 after retargeting to .NET 6+, migrating ASP.NET Response.End or Response.Redirect(url, true) which internally call Thread.Abort. DO NOT USE FOR: code that only uses Thread.Join, Thread.Sleep, or Thread.Start without any abort, interrupt, or ThreadAbortException usage — these APIs work identically in modern .NET and need no migration. Also not for projects staying on .NET Framework, or Thread.Abort usage inside third-party libraries you do not control.

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

推特中文圈 AI 自媒体博主 (推特(X) 中文圈 AI 自媒体博主 (从业者视角) — 在 X/推特 用中文做 AI 内容的自媒体博主，重点是**怎么写推文/thread、怎么制作内容**。覆盖: (a) 选题 — AI 模型发布解读 / prompt 技巧 / AI 工具实测 / AI 出海与独立开发(build in public) / 英文一手编译翻译 / 信息差 / AI 资讯快讯 / 深度长推; (b) 文案与内容结构(核心) — 单条推(开头钩子/信息密度/短句断行/配图截图/数据图)、长推与 thread(首条钩子/编号/逻辑链/结尾关注 CTA)、引用锐评(quote tweet)、排版可读性、配图(ray.so/carbon 代码图/产品截图/对比图); (c) 内容制作工作流 — 找信息源(英文一手/arXiv/官方/Reddit/HN)→选题→编译总结加洞察→写推/thread→配图→发布→互动维护; (d) AI 工具用于内容生产 — 英文一手编译总结(GPT/Claude/Kimi)、配图(ray.so/carbon/截图美化)、thread 工具(Typefully/Hypefury)、翻译、排程分析; (e) 平台机制与涨粉 — X 算法时间线(转评赞/互动权重/外链降权)、蹭热点借势、互动与回复、build in public 涨粉、英文区搬运到中文区的信息差红利; (f) 变现(次要) — 广告 / 知识星球 / 社群 / 付费课程 / 咨询 / 导流。学派分歧: 编译搬运(英文一手翻译) vs 原创洞察、快讯资讯 vs 深度长推、锐评玩梗 vs 严肃干货、build in public vs 纯内容、全 AI 自动发 vs 人工精选。代表生态(宝玉/歸藏/向阳乔木/AI 进化论/小互/Gorden Sun 等)。不含: 英文 AI Twitter 圈(聚焦中文圈)、通用 X 增长营销、其他平台、AI 工具技术原理。) Master OS — automated mastery of 推特(X) 中文圈 AI 自媒体博主 (从业者视角) — 在 X/推特 用中文做 AI 内容的自媒体博主，重点是**怎么写推文/thread、怎么制作内容**。覆盖: (a) 选题 — AI 模型发布解读 / prompt 技巧 / AI 工具实测 / AI 出海与独立开发(build in public) / 英文一手编译翻译 / 信息差 / AI 资讯快讯 / 深度长推; (b) 文案与内容结构(核心) — 单条推(开头钩子/信息密度/短句断行/配图截图/数据图)、长推与 thread(首条钩子/编号/逻辑链/结尾关注 CTA)、引用锐评(quote tweet)、排版可读性、配图(ray.so/carbon 代码图/产品截图/对比图); (c) 内容制作工作流 — 找信息源(英文一手/arXiv/官方/Reddit/HN)→选题→编译总结加洞察→写推/thread→配图→发布→互动维护; (d) AI 工具用于内容生产 — 英文一手编译总结(GPT/Claude/Kimi)、配图(ray.so/carbon/截图美化)、thread 工具(Typefully/Hypefury)、翻译、排程分析; (e) 平台机制与涨粉 — X 算法时间线(转评赞/互动权重/外链降权)、蹭热点借势、互动与回复、build in public 涨粉、英文区搬运到中文区的信息差红利; (f) 变现(次要) — 广告 / 知识星球 / 社群 / 付费课程 / 咨询 / 导流。学派分歧: 编译搬运(英文一手翻译) vs 原创洞察、快讯资讯 vs 深度长推、锐评玩梗 vs 严肃干货、build in public vs 纯内容、全 AI 自动发 vs 人工精选。代表生态(宝玉/歸藏/向阳乔木/AI 进化论/小互/Gorden Sun 等)。不含: 英文 AI Twitter 圈(聚焦中文圈)、通用 X 增长营销、其他平台、AI 工具技术原理。: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on 推特(X) 中文圈 AI 自媒体博主 (从业者视角) — 在 X/推特 用中文做 AI 内容的自媒体博主，重点是**怎么写推文/thread、怎么制作内容**。覆盖: (a) 选题 — AI 模型发布解读 / prompt 技巧 / AI 工具实测 / AI 出海与独立开发(build in public) / 英文一手编译翻译 / 信息差 / AI 资讯快讯 / 深度长推; (b) 文案与内容结构(核心) — 单条推(开头钩子/信息密度/短句断行/配图截图/数据图)、长推与 thread(首条钩子/编号/逻辑链/结尾关注 CTA)、引用锐评(quote tweet)、排版可读性、配图(ray.so/carbon 代码图/产品截图/对比图); (c) 内容制作工作流 — 找信息源(英文一手/arXiv/官方/Reddit/HN)→选题→编译总结加洞察→写推/thread→配图→发布→互动维护; (d) AI 工具用于内容生产 — 英文一手编译总结(GPT/Claude/Kimi)、配图(ray.so/carbon/截图美化)、thread 工具(Typefully/Hypefury)、翻译、排程分析; (e) 平台机制与涨粉 — X 算法时间线(转评赞/互动权重/外链降权)、蹭热点借势、互动与回复、build in public 涨粉、英文区搬运到中文区的信息差红利; (f) 变现(次要) — 广告 / 知识星球 / 社群 / 付费课程 / 咨询 / 导流。学派分歧: 编译搬运(英文一手翻译) vs 原创洞察、快讯资讯 vs 深度长推、锐评玩梗 vs 严肃干货、build in public vs 纯内容、全 AI 自动发 vs 人工精选。代表生态(宝玉/歸藏/向阳乔木/AI 进化论/小互/Gorden Sun 等)。不含: 英文 AI Twitter 圈(聚焦中文圈)、通用 X 增长营销、其他平台、AI 工具技术原理。 problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「推特 ai 博主」「推特中文 ai」「x ai 自媒体」「推特 thread」「推特爆款推文」

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

Guides migration of .NET Framework Thread.Abort usage to cooperative cancellation in modern .NET. USE FOR: modernizing code that calls Thread.Abort, catching ThreadAbortException, replacing Thread.ResetAbort, replacing Thread.Interrupt for thread termination, resolving PlatformNotSupportedException or SYSLIB0006 after retargeting to .NET 6+, migrating ASP.NET Response.End or Response.Redirect(url, true) which internally call Thread.Abort. DO NOT USE FOR: code that only uses Thread.Join, Thread.Sleep, or Thread.Start without any abort, interrupt, or ThreadAbortException usage — these APIs work identically in modern .NET and need no migration. Also not for projects staying on .NET Framework, or Thread.Abort usage inside third-party libraries you do not control.

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

Fetches public posts from a Threads user's profile page, extracting post text, engagement metrics, and media info from SSR-embedded JSON. Use when user asks to scrape Threads posts, get someone's Threads feed, pull posts from a Threads account, collect Threads content by username, download Threads user posts, extract Threads profile posts, monitor a Threads user's activity, retrieve recent posts from a Threads handle, gather Threads post data for a creator, or fetch all posts from a specific Threads profile.

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

Write X/Twitter threads that get bookmarked, shared, and drive affiliate clicks. Use this skill when the user asks about writing Twitter threads, X threads, tweet threads for affiliate marketing, or says "write a thread about X", "Twitter thread promoting X", "X thread for affiliate", "write tweets that go viral", "thread that sells without selling", "educational thread with affiliate CTA", "Twitter content for affiliate marketing", "how to promote X on Twitter", "write a thread my audience will bookmark", "tweet storm about affiliate product".

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

Build a threat model for a target codebase. Three modes: "interview" walks an application owner through the four-question framework and produces a threat model from their answers; "bootstrap" derives a threat model from the code plus past vulnerabilities (CVEs, git history, pentest reports) when no owner is available; "bootstrap-then-interview" chains the two when both owner and codebase are present. All write THREAT_MODEL.md in a shared schema. Use when asked to "threat model", "build a threat model", "map the attack surface", or "what should we be worried about in this codebase".

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

Collects every tweet in an X (Twitter) conversation thread given a conversation id (root tweet id) — the focal tweet plus all replies, sub-replies, and quote chains — and returns normalized per-tweet data with text, author, engagement counts, media, hashtags, mentions, in_reply_to mapping, and cursor for pagination. Use when user mentions Twitter conversation, X conversation thread, conversation_id, thread scraper, scrape Twitter replies, all replies to a tweet, replies under a tweet, sub-replies, nested replies, thread harvester, get replies of a tweet, scrape comments on Twitter, scrape comments on X, full thread extraction, conversation export, conversation tree, reply chain, thread dump, X tweet thread, twitter thread scrape, comment scraping twitter, comment scraping x, focal tweet plus context, root tweet plus replies. Also applies to sentiment analysis on a single viral tweet, controversy mapping, harvesting community Q&A threads, capturing AMA threads, recovering long-running discussions, and any paginated bulk reply collection driven by a conversation id.

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

Repurpose existing content into a native Threads post or thread. Take a LinkedIn post, X thread, blog, YouTube script, or newsletter and rewrite it for Threads: warm the tone, de-corporate it, refit to a short post or light thread, rebuild the hook to clear the soft fold, strip off-platform artifacts, run the humanizer, publish via Publora on approval. Not for writing from scratch (use threads-post-writer), auditing a draft (use threads-humanizer), or a hook teardown (use threads-hook-extractor).

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

Plan, draft, audit, and publish posts and threads for Threads (Meta). Use when the user wants to write a single Threads post or a multi-post thread, remove AI tells from a draft, reverse-engineer the hook from a viral Threads post, draft a reply or quote post, or plan a week of Threads content. Posts and threads publish via the Publora API, which auto-splits long content into a connected multi-post thread. User provides notes or a post URL, the skill drafts, the user approves, then it publishes.

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

Query a MISP (Malware Information Sharing Platform) instance via PyMISP to compute event statistics, IOC type breakdowns, threat actor galaxy clusters, and tag trends, and generate threat landscape reports with temporal trends. Use when asked to analyze threat intelligence data, summarize top threat actors or malware families, or produce a CTI landscape report from MISP events.

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

[omh] Attack paths into an operated system: turn a system's components and data flows into assets, trust boundaries, attack scenarios, controls, and the security test that proves each control holds. Use when the user says: application-threat-model, application threat model, threat model, threat modeling, threat modelling, threat modeling session, threat modeling workshop, security threat model.

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

Web 线上展览开发 (虚拟展厅) (Web 线上展览 / 虚拟展厅开发 (从业者/工程视角) — 用 web 技术开发线上展览、虚拟展厅、云展会、数字展馆，覆盖 3D 空间、全景漫游、WebXR、文博数字化、营销云展厅、3D 商品展示等形态。覆盖: (a) 技术栈 — 3D web(Three.js / React Three Fiber / Babylon.js / Google model-viewer / WebGL / WebGPU)、全景(Pannellum / Marzipano / Photo Sphere Viewer / krpano / 720云)、WebXR(WebXR Device API / A-Frame)、资产管线(glTF·GLB / Draco / Meshopt / KTX2 纹理压缩 / gltf-transform / LOD); (b) 自研 vs SaaS 平台选型(国内: 众趣 / 酷雷曼 / 比目鱼 / 会鸽 / 3DVista; 海外: Matterport / Kuula / Artsteps / Spatial); (c) 性能优化(大场景加载 / 模型轻量化 / draw call / 移动端 / 首屏 / 显存)——web 3D 第一性难题; (d) 策展与导览(动线设计 / 热点 hotspot / 语音讲解 / 交互); (e) 文博数字化(IIIF / 数字孪生 / 高清文物) 与 会展·电商商业化(营销云展厅 / 数据埋点 / 线索转化); (f) 部署(CDN / 流式加载 / 跨端兼容 / WebGL 降级)。学派分歧: 自研 Three.js vs SaaS 平台、真 3D 重场景 vs 720 全景轻量、WebGL vs WebGPU、文博考据派 vs 营销转化派、沉浸优先 vs 加载优先。不含: 线下展陈 / 展台搭建、原生 VR App(非 web)、通用 3D 游戏开发、纯 3D 建模教程。) Master OS — automated mastery of Web 线上展览 / 虚拟展厅开发 (从业者/工程视角) — 用 web 技术开发线上展览、虚拟展厅、云展会、数字展馆，覆盖 3D 空间、全景漫游、WebXR、文博数字化、营销云展厅、3D 商品展示等形态。覆盖: (a) 技术栈 — 3D web(Three.js / React Three Fiber / Babylon.js / Google model-viewer / WebGL / WebGPU)、全景(Pannellum / Marzipano / Photo Sphere Viewer / krpano / 720云)、WebXR(WebXR Device API / A-Frame)、资产管线(glTF·GLB / Draco / Meshopt / KTX2 纹理压缩 / gltf-transform / LOD); (b) 自研 vs SaaS 平台选型(国内: 众趣 / 酷雷曼 / 比目鱼 / 会鸽 / 3DVista; 海外: Matterport / Kuula / Artsteps / Spatial); (c) 性能优化(大场景加载 / 模型轻量化 / draw call / 移动端 / 首屏 / 显存)——web 3D 第一性难题; (d) 策展与导览(动线设计 / 热点 hotspot / 语音讲解 / 交互); (e) 文博数字化(IIIF / 数字孪生 / 高清文物) 与 会展·电商商业化(营销云展厅 / 数据埋点 / 线索转化); (f) 部署(CDN / 流式加载 / 跨端兼容 / WebGL 降级)。学派分歧: 自研 Three.js vs SaaS 平台、真 3D 重场景 vs 720 全景轻量、WebGL vs WebGPU、文博考据派 vs 营销转化派、沉浸优先 vs 加载优先。不含: 线下展陈 / 展台搭建、原生 VR App(非 web)、通用 3D 游戏开发、纯 3D 建模教程。: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on Web 线上展览 / 虚拟展厅开发 (从业者/工程视角) — 用 web 技术开发线上展览、虚拟展厅、云展会、数字展馆，覆盖 3D 空间、全景漫游、WebXR、文博数字化、营销云展厅、3D 商品展示等形态。覆盖: (a) 技术栈 — 3D web(Three.js / React Three Fiber / Babylon.js / Google model-viewer / WebGL / WebGPU)、全景(Pannellum / Marzipano / Photo Sphere Viewer / krpano / 720云)、WebXR(WebXR Device API / A-Frame)、资产管线(glTF·GLB / Draco / Meshopt / KTX2 纹理压缩 / gltf-transform / LOD); (b) 自研 vs SaaS 平台选型(国内: 众趣 / 酷雷曼 / 比目鱼 / 会鸽 / 3DVista; 海外: Matterport / Kuula / Artsteps / Spatial); (c) 性能优化(大场景加载 / 模型轻量化 / draw call / 移动端 / 首屏 / 显存)——web 3D 第一性难题; (d) 策展与导览(动线设计 / 热点 hotspot / 语音讲解 / 交互); (e) 文博数字化(IIIF / 数字孪生 / 高清文物) 与 会展·电商商业化(营销云展厅 / 数据埋点 / 线索转化); (f) 部署(CDN / 流式加载 / 跨端兼容 / WebGL 降级)。学派分歧: 自研 Three.js vs SaaS 平台、真 3D 重场景 vs 720 全景轻量、WebGL vs WebGPU、文博考据派 vs 营销转化派、沉浸优先 vs 加载优先。不含: 线下展陈 / 展台搭建、原生 VR App(非 web)、通用 3D 游戏开发、纯 3D 建模教程。 problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「线上展览」「虚拟展厅」「web 线上展览」「云展厅」「数字展馆」

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

Generate a weekly Threads (Meta) content plan from a theme, audience, and content pillars. Produces per-day recommendations (single post vs thread, Threads hook formula, angle, posting time, primary goal), a single-to-thread mix, daily reply and quote-post targets, and a goal-mix balance check across replies, reposts, likes, and quotes. Use when the user wants to plan a week of Threads content instead of ad-hoc posting. Not for drafting one post or thread (use threads-post-writer).

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

Use when handling PyQt/PySide6 threading - QThread patterns, QThreadPool/QRunnable, thread safety rules, moveToThread, Qt Concurrent, QTimer, testing threaded code, lifecycle management

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

Write a threat model document. Use when the user says "threat model", "threat modeling", "STRIDE analysis", "attack surface analysis", "security design review", "what are the threats to this system", "adversarial analysis", "identify threats", "security threat assessment", or needs to systematically identify and document threats to a system or feature - even if they don't explicitly say "threat model".

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

Target a specific Google Chrome user profile for browser automation via CDP. Discovers installed profiles from the Chrome Local State file, launches Chrome with the requested profile attached to a debug port, and connects agent-browser via `agent-browser connect <port>`. Use when "automate using my Work/Personal Chrome", "open site with my saved session", or "use Chrome profile named <name>". NOT for headless scraping without an existing user profile (use mk:agent-browser directly); NOT for importing cookies only (use agent-browser --auto-connect state save).

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

Create, list, read, message, wait on, fork, rename, archive, and pin Codex threads (sidebar tasks), plus automations and app navigation, using the app-native codex_app tools. Use when the session uses a custom (non-OpenAI) model, for example deepseek-v4-flash or mimo-v2.5, and the user asks to create a thread or a new task or agent, list or read threads, send a message to a thread, wait for a thread, fork or rename a thread, archive or pin a thread, set up an automation or reminder, or open something in the Codex app.

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

Implement Anthropic Claude API rate limiting, backoff, and quota management. Use when handling 429 errors, optimizing request throughput, or managing RPM/TPM limits across usage tiers. Trigger with phrases like "anthropic rate limit", "claude 429", "anthropic throttling", "claude retry", "anthropic backoff".

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

Stand up a three.js scene: import maps and the three/addons path, the Scene/PerspectiveCamera/WebGLRenderer trio, the setAnimationLoop render loop, responsive resize, and OrbitControls. Use when starting or debugging a three.js app — when the user mentions three.js, THREE.Scene, WebGLRenderer, PerspectiveCamera, the render loop, resizing, or OrbitControls. For models use threejs-gltf-loading; for materials/lights use threejs-materials-lighting.

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

Quantify homologous recombination deficiency (HRD) from tumor copy number using the three genomic-scar metrics — loss of heterozygosity (LOH), large-scale state transitions (LST), and telomeric allelic imbalance (TAI) — with scarHRD, and via the whole-genome HRDetect and CHORD models. Covers the genomic instability score, the PARP-inhibitor clinical context, whole-genome-doubling correction, and the scar-versus-state distinction. Use when computing an HRD score for PARP-inhibitor eligibility, deriving LOH/LST/TAI scars from allele-specific copy number, deciding between scar-based and mutational-signature HRD methods, or interpreting an HRD result in a BRCA-reverted or low-purity tumor.

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