686 件 ・ 関連度順
概要と使いどころ
Plan and execute a comprehensive, MITRE ATT&CK-aligned red team engagement spanning threat modeling, reconnaissance, initial access, and post-exploitation to evaluate an organization's detection, prevention, and response against APT-style behavior. Use when scoping or running a full-scope, objective-based engagement, or purple-teaming against a specific threat actor's TTPs.
日本語の概要は準備中です。原文の説明を表示しています。
Social media campaign analysis and performance tracking. Calculates engagement rates, ROI, and benchmarks across platforms. Use when analyzing social media performance, calculating engagement rate, measuring campaign ROI, comparing platform metrics, or benchmarking against industry standards. Also use when the user mentions "social media audit," "engagement rate," or "which platform performs best."
日本語の概要は準備中です。原文の説明を表示しています。
Client-facing red-team deliverable format — codifies the Subject / Observations / Description / Impact / Recommendation / PoC structure used for external red-team engagements (not bug-bounty platform reports). Different audience, different tone, different cadence. Built from an authorized engagement deliverable where 14 findings were packaged into a 52KB MD + 2.2MB DOCX with 16 embedded screenshots. Use when the engagement is "external red team for an enterprise client" (not H1/Bugcrowd/Intigriti), when generating the final report, when the client has specified a custom report format, or when packaging findings into DOCX/PDF.
日本語の概要は準備中です。原文の説明を表示しています。
Methodology for detecting client SOC patches, attacker activity, and security-state changes that occur DURING a red-team engagement — and converting those observations into deliverable findings. Built from authorized red-team work where the client patched a confirmed SQLi within 30 minutes of detection AND an external attacker locked multiple new accounts during a single test session. Use when (a) running ANY active engagement against a monitored target, (b) a previously-confirmed finding stops reproducing, (c) baseline timing shifts unexpectedly, or (d) you notice response patterns changing during testing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "set up my founder social-selling routine", "build a daily engagement block for target accounts", or "turn funding / hiring signals into selling plays"; produces the founder/seller daily operating block — a time-boxed engagement-block spec (substantive value-add comments on target-account posts, never a pitch), warm-touch-before-ask cadence rules, trigger-response plays consuming the social-pulse-monitor B2B trigger watchlist (funding / hiring / launch signals), and a quarterly diagnostic that reads LinkedIn SSI as an input diagnostic only (Estimated, vendor-defined — never a target metric). All volume norms are Estimated/community-derived; all execution is human — zero mass-DM, zero connection-request automation, zero engagement automation (LinkedIn UA §8.2 red line); 1:1 pitch and DM mechanics route to outreach-manager. Not for cold email sequences — use cold-outbound-sequencer. 社交销售/创始人日常互动块/热身触达节奏/触发信号剧本
日本語の概要は準備中です。原文の説明を表示しています。
Search LinkedIn posts by keywords, sorted by engagement or date. Use when researching what people are saying about a topic on LinkedIn, finding high-engagement content, identifying thought leaders, or discovering warm leads through post engagement. Returns author, post text, reactions, comments, shares, post URL, and date. No LinkedIn cookies or login required.
日本語の概要は準備中です。原文の説明を表示しています。
Write a client proposal, quote, scope of work, or engagement letter for a service business. Covers project understanding, scope, timeline, pricing presentation, and terms. Use whenever the user asks for a proposal, quote, project proposal, client proposal, SOW, statement of work, engagement letter, or B2B service engagement document — for web dev, consulting, trades, or any service business.
日本語の概要は準備中です。原文の説明を表示しています。
Social media campaign analysis and performance tracking that calculates engagement rates, ROI, and cross-platform benchmarks. Use for analyzing social performance, calculating engagement rate, or measuring campaign ROI.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "plan a red team engagement", "scope a penetration test", "design a security assessment methodology", "create rules of engagement", or "plan an adversary simulation".
日本語の概要は準備中です。原文の説明を表示しています。
Run the 12-Part engagement workflow from intake to growth plan, checkpointed. "start a new engagement"
日本語の概要は準備中です。原文の説明を表示しています。
Turn the people who like and comment on a source account's LinkedIn posts (a competitor, or one of the client's own customers) into ICP-filtered prospect rows, with an optional copy-ready personalization line when the campaign asks for one. Triggers on "who engages with our competitors", "likers and commenters", "LinkedIn engagement list", "people commenting on competitor posts", "who engages with our customers' posts", "warm LinkedIn audience", "competitor engagers". Outputs one clean prospect row per engager; engagement_line only on request.
日本語の概要は準備中です。原文の説明を表示しています。
Authorized red team engagement planning, C2 architecture design, attack methodology, lateral movement strategy, OPSEC, and professional reporting
日本語の概要は準備中です。原文の説明を表示しています。
Guides data subject and stakeholder consultation requirements during Data Protection Impact Assessments under GDPR Article 35(9). Covers consultation planning, data subject engagement methods, DPO involvement per Art. 35(2), and documentation of views received. Keywords: DPIA consultation, stakeholder engagement, Art. 35(9), data subject views, DPO advice, public consultation, representative groups.
日本語の概要は準備中です。原文の説明を表示しています。
Your most loyal users aren't just customers - they're potential advocates, contributors, and community members who can become the engine of your growth. Community-led growth isn't about broadcasting to an audience - it's about creating a space where your users connect with each other, share knowledge, and become invested in your success. This skill covers community strategy, platform selection, engagement tactics, ambassador programs, and the metrics that matter. Whether you're building a Discord for developers or a forum for power users, the goal is the same: creating genuine value that makes members want to stay and contribute. Use when "community, discord, forum, user group, ambassador, champions, developer relations, devrel, community engagement, community growth, power users, superfans, community, discord, engagement, devrel, ambassador, forum, user-community, growth, retention, champions" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Your team has high autonomy — and standups are vague, weekly meetings drift into status reports, and 1:1s produce nothing but "I'm fine." This playbook fixes all three layers at once. What's inside: • Daily Standup system — 3-field format, good sample, 4 COO principles to keep it honest • Weekly Meeting — strict 25-min agenda, Scrum Master rotation, 0–10 pulse check • 1:1 Framework — 9-dimension quantified pulse, 5-group deep question bank, bilateral feedback structure • Diagnostic layer — "stuck-at" detection: info / authority / collaboration / capability / direction • FAQ for 4 common failure modes (dead standups, status-report meetings, "I'm fine" 1:1s, scaling beyond 10 people) 🇨🇳 你的团队自由度很高——但 standup 越来越糊，例会变成汇报，1:1 问不出真话。这套三层 Motivation 操作手册解决的正是这件事：standup 是信息层，例会是对齐层，1:1 是个人层。三件事做好了，motivation 不是管出来的，是长出来的。 🇯🇵 チームの自律性は高いのに、スタンドアップは曖昧で、週次ミーティングは進捗報告になり、1on1では「大丈夫です」しか返ってこない——このプレイブックは、その3層すべてを同時に解決します。 🇰🇷 팀의 자율성은 높은데 스탠드업은 두루뭉술하고, 주간 회의는 진척 보고가 되어버리고, 1:1에서는 진심을 들을 수 없다면 — 이 플레이북이 세 레이어 모두를 동시에 해결합니다. Triggers: "团队 motivation" | "standup 没人写" | "例会变成汇报" | "1:1 问不出真话" | "高自由度团队管理" | "COO 如何管人" | "team motivation" | "standup best practices" | "1on1 framework" | "weekly meeting template" | "チームモチベーション" | "팀 동기부여" | "AI startup team ops" | "remote team alignment" | "engagement下降"
新号没粉丝、推文没人看、怎么度过冷启动时用。涨粉四步漏斗(曝光→展开→Profile门面→关注)诊断丢哪步,按边际回报排序投六策略:大V评论区抢占(最高)/引用转发+深度观点/每日发推/互关社区(≤15/天)/蹭热点/互动率优先;前24h主动加热突破初始池。Trigger:"没粉丝""帖子没人看""冷启动""怎么起量""0 followers""no engagement""cold start"。不适用:开业前装修/蓝V/养号(→x-account-setup)、已有稳定粉丝日常运营、限流封号排查(→x-account-pitfalls)、纯评论技巧(→x-comment-engagement)。
日本語の概要は準備中です。原文の説明を表示しています。
当用户想在大V帖下评论获取曝光、纠结Repost还是Quote、或问"怎么引发互动""怎么在别人帖下获曝光又不被当蹭流量"时调用。六种评论互动法(有价值提问/A-B引战/坎宁汉姆定律/真诚请教/生活日常/找骂)+高质量回复吃原帖流量+Repost vs Quote区分。Trigger:评论互动/蹭流量/Quote还是Repost/评论区抢占/comment engagement/quote vs repost/how to reply for exposure。不适用于:自己发原创帖(用x-short-content-craft)、冷启动整体策略排序(用x-cold-start-playbook)。
日本語の概要は準備中です。原文の説明を表示しています。
Use when analyzing published content (blog posts, social media, newsletters) for sentiment, structural quality, hook effectiveness, readability, topic classification, and engagement correlation. Invoke for daily post analysis, content audits, or engagement driver identification.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive social media operations for B2B SaaS brand building and engagement. Use this skill to develop LinkedIn strategy, decide whether to run a LinkedIn newsletter and how to scope it, capture consented registrations from LinkedIn Events, check LinkedIn Live eligibility, manage Twitter/X presence, create YouTube content, engage on Reddit communities, decide whether and how to answer on Quora, build community, develop influencer and creator partnerships, vet a creator before paying them, start or fix a B2B podcast, book podcast guests and guest appearances, judge whether a podcast is worth appearing on when you cannot audit its numbers, write show notes and transcripts, run social listening (what are people saying about us, share of voice, brand monitoring, validated sentiment, alert thresholds, routing signals to the right owner), and execute organic social campaigns. Also triggers on: LinkedIn, LinkedIn newsletter, LinkedIn Events, LinkedIn Live, event registration form, subscribe to our newsletter on LinkedIn, marketing consent checkbox, Notify Employees, Twitter/X, YouTube, Reddit, community, influencer, creator partnerships, influencer vetting, engagement rate, fake followers, engagement pods, FTC disclosure, sponsored post disclosure, media kit, social media strategy, organic social, employee advocacy, podcast, podcast strategy, podcast guesting, how do I know if this podcast has real listeners, the host says they get 50k downloads, is this podcast worth going on, podcast RSS feed research, IAB podcast measurement certification, Listen Score, Apple Podcasts reviews, show notes, audiogram, episode transcript, social media account access, who has admin on our LinkedIn page, the person who ran our social accounts left, locked out of our company account, social media offboarding, YouTube channel owner, Slack primary owner, social account MFA, social media approval workflow, pause all scheduled posts, social listening, what are people saying about us, brand monitoring, brand mentions, share of voice, social share of voice vs competitors, sentiment analysis, is our sentiment dashboard accurate, listening query, boolean query, mention alerts, spike alert, CrowdTangle replacement, Reddit API access, which platforms can our listening tool see, someone on Reddit asked for a tool like ours, comment mining, voice of customer from social.
日本語の概要は準備中です。原文の説明を表示しています。
Write a penetration test scope document. Use when the user says "pentest scope", "pen test scope document", "penetration testing scope", "scope of engagement", "rules of engagement", "what to include in a pentest", "security assessment scope", "red team scope", "bug bounty scope", or needs to define the boundaries, objectives, and rules for a penetration testing engagement - even if they don't explicitly say "scope".
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when defining patient engagement portal requirements for Health Cloud: appointment scheduling, secure in-portal messaging, health assessments, patient education, and self-service features. NOT for care team workflows, SDOH barriers and care gaps — use admin/care-coordination-requirements. NOT for patient portal licensing and cloud topology — use architect/health-cloud-multi-cloud-strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when configuring MCAE (Account Engagement / Pardot) lead scoring models, grading profiles, score decay rules, or automation rules that fire on score/grade thresholds. Covers: scoring point values per activity, score decay for inactivity, Profiles for fit grading, combined MQL definitions (Score + Grade), and automation rules vs completion actions. NOT for defining the MQL model before build — use admin/lead-scoring-requirements. NOT for Engagement Studio nurture programs — use admin/lead-nurture-journey-design.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when designing or documenting a lead scoring model in Salesforce Sales Cloud or Account Engagement: qualifying criteria, MQL/SQL threshold definitions, scoring dimensions (demographic, firmographic, behavioral), and sales handoff SLA. NOT for configuring the scoring, grading, and automation rules in Account Engagement — use admin/mcae-lead-scoring-and-grading. NOT for the whole marketing program's lifecycle stages and platform scope — use admin/marketing-automation-requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing nonprofit fundraising lifecycle stages, donor pipeline workflows, cultivation-to-stewardship cycles, or Salesforce Opportunity sales process configuration for NPSP or Nonprofit Cloud. Trigger keywords: fundraising lifecycle, donor pipeline, cultivation stage, solicitation workflow, major gift process, moves management, NPSP Opportunity stages, stewardship cycle, NPC fundraising stages. NOT for lapsed donor re-engagement or portfolio segmentation — use admin/donor-lifecycle-requirements. NOT for Engagement Plan setup — use admin/npsp-engagement-plans.
日本語の概要は準備中です。原文の説明を表示しています。