「main」の検索結果

微信私域运营 (企微 + 个人号 + 公众号 + 视频号 + 小程序 + 朋友圈 + 社群 全链路 — 引流 / 沉淀 / 触达 / 转化 / 复购 / 裂变) (WeChat private-domain operations — 微信生态(企微 + 个人号 + 公众号 + 视频号 + 小程序)的私域操盘) Master OS — automated mastery of WeChat private-domain operations — 微信生态(企微 + 个人号 + 公众号 + 视频号 + 小程序)的私域操盘: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on WeChat private-domain operations — 微信生态(企微 + 个人号 + 公众号 + 视频号 + 小程序)的私域操盘 problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「私域」「私域运营」「私域操盘」「微信私域」「企业微信」

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

GitHub 解封 — 账号封禁/限制/恢复的领域操作系统。覆盖：(a) GitHub 官方政策体系 (TOS / 可接受使用政策 / Trust & Safety 执行模式 / 公开申诉路径 / 受制裁地区解读)；(b) 封号原因诊断学 (spam / abuse / 制裁误标 / 2FA 丢失 / ToS 违规 / 账号劫持误判 / ban evasion 等子类型 + 症状→原因映射 + 自我分诊压测)；(c) 申诉实操 craft (写一封能让 T&S 快速判误伤的英文申诉信 + 升级阶梯 + 法务介入边界 + Don'ts)；(d) 制裁与合规硬边界 (OFAC SDN 名单 / 哪些国家或地区真不可达 / VPN 误判路径 / 中国大陆不是美国制裁地区的反复重申)；(e) 中国大陆开发者特别处境 (sanctioned region 误标 + SMS 验证不支持 +86/+852 + Gitee/GitLab/Codeberg/JihuLab 备用迁移 + 私有自托管 Gitea/Forgejo)；(f) 真实案例库 (~30+ 公开案例分类拆解：误伤 / 真违规 / 制裁误标三类各自赔率与申诉成功路径)。伦理锚绝不软化：不教 ban evasion / 不教撒谎式申诉 / 真违规承认改进 / 丢 2FA 无恢复因子则诚实告知 / 中国制裁误标靠申诉不靠换 VPN / 申诉 6 个月窗口必算清 / 约 3% (业内估) 真违规恢复 vs 约 79% (业内估) 误伤申诉成功率分层标。 (GitHub Account Reinstatement — the domain operating system for GitHub (and analogous platform) account suspension, restriction, appeal, and recovery. Covers: (a) GitHub official policy architecture (TOS / Acceptable Use Policies / Trust & Safety enforcement patterns / public appeals pathways / sanctioned-region interpretation); (b) suspension-cause diagnostics (spam / abuse / sanctions mis-flag / 2FA loss / ToS violation / account hijack false-positive / ban evasion taxonomy + symptom→cause mapping + self-triage pressure test); (c) appeal craft (writing an English appeal letter that gets T&S to fast-track a false-positive ruling + escalation ladder + legal-engagement boundary + Don'ts); (d) sanctions and compliance hard boundaries (OFAC SDN list / which countries/regions are truly unreachable / VPN false-positive paths / China is NOT a US-sanctioned region — repeated emphasis); (e) mainland China developer special circumstances (sanctioned-region mis-flag + SMS verification does not support +86/+852 + Gitee/GitLab/Codeberg/JihuLab fallback migration + self-hosted Gitea/Forgejo); (f) real-case library (~30+ public cases with categorized analysis: false-positive / genuine violation / sanctions mis-flag, each with win-rate and appeal success path). Ethical anchors absolutely not softened: do NOT teach ban evasion (creating new accounts turns a temp ban into a permanent one — the single biggest mistake); do NOT teach social engineering or lying in appeals (misuse + actually confirms violation); genuine violations: admit + improve beats denial; lost 2FA + no recovery factor → do not pretend recovery is possible; China sanctioned-region mis-flag → fix via appeal, not repeated VPN switching; appeal form 6-month window must be counted carefully; historical 约 3% (业内估) genuine-violation recovery vs 约 79% (业内估) false-positive appeal success rate stratification must be honestly labeled. Anti-samples (explicitly describe harm, never endorse): developer permabanned for ban evasion / open-source team org-banned for personal attacks in public issues / cases where repeated VPN switching escalated risk-control severity.) Master OS — automated mastery of GitHub Account Reinstatement — the domain operating system for GitHub (and analogous platform) account suspension, restriction, appeal, and recovery. Covers: (a) GitHub official policy architecture (TOS / Acceptable Use Policies / Trust & Safety enforcement patterns / public appeals pathways / sanctioned-region interpretation); (b) suspension-cause diagnostics (spam / abuse / sanctions mis-flag / 2FA loss / ToS violation / account hijack false-positive / ban evasion taxonomy + symptom→cause mapping + self-triage pressure test); (c) appeal craft (writing an English appeal letter that gets T&S to fast-track a false-positive ruling + escalation ladder + legal-engagement boundary + Don'ts); (d) sanctions and compliance hard boundaries (OFAC SDN list / which countries/regions are truly unreachable / VPN false-positive paths / China is NOT a US-sanctioned region — repeated emphasis); (e) mainland China developer special circumstances (sanctioned-region mis-flag + SMS verification does not support +86/+852 + Gitee/GitLab/Codeberg/JihuLab fallback migration + self-hosted Gitea/Forgejo); (f) real-case library (~30+ public cases with categorized analysis: fa

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

Domain-driven modeling patterns for Axone contracts. Use when introducing domain concepts, encoding invariants, or deciding boundaries between domain, handlers, services, gateways, queries, and state.

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

Merge the public openai/codex-security main branch into this fork's main branch and push the result to the fork remote. Use when asked to sync or merge upstream main for this repository.

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

Active Directory exploitation after domain credentials exist: Kerberos (AS-REP/Kerberoast including cracking the ticket then using the account), delegation, NTLM coercion/relay, lateral movement, ACL abuse, ADCS ESC1-ESC17 and CVE paths, dMSA/BadSuccessor, Kerberos reflection, identity confusion, management-plane, domain trust, and domain persistence. Own the current AD chain through crack-and-use to DA, equivalent domain control, or the targeted host SYSTEM. Do not stop after requesting TGS. Host C2 belongs to /post. Operator chooses next modules.

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

履歴書（main.tex）に本人の情報を記入して out/main.pdf をビルドする。「履歴書を書いて／埋めて」「履歴書のPDFを出して」「職歴を追加して」など、このリポジトリの履歴書の内容を作成・更新・出力するときに使う。レイアウト（rirekisho.sty）の改修そのものには使わない。

Enumerate subdomains using passive and active techniques (subfinder, amass, chaos, assetfinder, crtsh, DNS brute force). Use when the user has a root domain in scope and needs the full subdomain list before probing.

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

Build or update a CONTEXT.md domain glossary for the current project. Establishes shared vocabulary with term definitions, avoid-aliases, and relationships so agents use consistent, concise language. This skill should be used when starting a new project, when domain terminology is inconsistent across sessions, when the user says "build a glossary", "define our terms", "shared vocabulary", or "domain language", or when an existing CONTEXT.md needs updating after new domain concepts emerge.

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

Communicate an integrated insight in a way that is accessible, actionable, and preserves the multi-domain nature of the understanding. Integrated insights are multi-dimensional — linearizing them risks losing the relationships that make them valuable. This skill provides a structured procedure for choosing the right form, expressing the gestalt with honest attribution, and inviting productive challenge. Use after integrate-gestalt has formed a cross-domain understanding that needs to be communicated to an audience — domain specialists, generalists, or decision-makers.

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

Triage maintenance problems by severity, document findings with context, route to appropriate specialist agent or human, and create actionable issue reports. Use when a maintenance task encounters problems beyond automated cleanup: code that is unsafe to delete, configuration changes requiring domain expertise, breaking changes detected during cleanup, complex refactoring needed, or security-sensitive findings such as hardcoded secrets or vulnerabilities.

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

Use when pinning down domain terminology, maintaining the domain model, or when a term conflicts or needs sharpening.

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

Route one eligible transition in Proto UI's governed autonomous-maintenance protocol. Use for maintenance missions, drift discovery, finding verification, accepted remediation, independent maintenance review, run-ledger closure, or residual-risk planning. Do not use for ordinary user-directed development.

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

Use when a user asks to investigate, check, or characterize a domain or hostname. Chains VirusTotal, URLScan (search existing scans), Shodan (DNS resolve + host), OTX, ransomware.live (victim-status sweep), and optionally Censys. Returns reputation, resolution, hosting fingerprint, ransomware-claim status, and pivot candidates. Invoked by /cti-orchestrator when the target is a domain.

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

"Habitual Domain (HD) theory by Taiwanese scholar P.L. Yu (游伯龍, 1977) — integrates four domains (potential/actual/reachable/activated), eight general hypotheses, seven-layer decision structure, and nine HD-expansion tools to analyze decision blind spots, break cognitive inertia, and support cross-domain integration. Use for diagnosing why alternatives are invisible, decision paralysis, breaking cognitive frames, or explaining perception gaps between people. Triggers: 『思維框架』『打破盲點』『創新思考』『決策盲區』『跨域整合』『游伯龍』『習慣領域』『HD 理論』『七層決策』『四領域』『八大通性』『P.L. Yu』. Especially for NYCU EMBA HD course, 政大科管所, 中山企管系 decision-analysis/innovation/leadership courses. Taiwan-origin theory cited in J. Optimization Theory, Theory & Decision, Human Systems Management.".

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

Execute a complete Active Directory penetration test from initial enumeration to domain dominance. Use this skill for AD security assessments including LDAP enumeration, Kerberos attacks (Kerberoasting, AS-REP roasting), BloodHound attack path analysis, credential dumping with Mimikatz, lateral movement via PsExec/WMI/DCOM, DCSync for NTDS extraction, and Golden/Silver ticket forging. Covers the full kill chain from domain user to domain admin.

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

See recently acquired and lost backlinks for a domain using Ahrefs. Shows new referring domains in the last 30 days and any lost referring domains. Use when user says "new backlinks", "new links", "recently acquired links", "lost links", or "new referring domains".

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

Show a domain's Domain Rating trend over time from Ahrefs. Reveals DR growth, drops, and significant changes. Use when user says "DR history", "domain rating history", "DR trend", "domain rating over time", or "DR changes".

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

Analyze preventive and predictive maintenance scheduling systems including CMMS/EAM work order optimization, asset condition scoring with Facility Condition Index, PM compliance tracking, maintenance backlog reduction, reliability-centered maintenance strategy.

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

Analyze defense maintenance and readiness systems — MRO optimization, mission capable rate tracking, reliability-centered maintenance (RCM), condition-based maintenance (CBM+), depot-level analytics, configuration management, and workforce planning. Audit weapon system sustainment software per MIL-STD-3034, AR 750-1, and DoD CBM+ frameworks.

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

Diagnoses, predicts, and mitigates node disruptions during Compute Engine host maintenance and hardware or software maintenance events for GPU and TPU workloads on GKE. Use when diagnosing node disruptions, predicting host maintenance events on GPU/TPU nodepools, inspecting node interruption PromQL metrics, auditing node taints, or configuring workload protection strategies (graceful termination, opportunistic maintenance, PodDisruptionBudgets). Don't use for general GKE cluster creation, network policy configuration, or non-disruption workload deployment.

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

Drafts IRC 664–compliant Charitable Remainder Trust agreements (CRAT/CRUT), covering payout math, remainder qualification, trustee powers, and tax compliance. Use when drafting a CRT, CRAT, CRUT, unitrust, annuity trust, or charitable remainder planning document, or when ensuring IRC 664 compliance.

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

Domain-aware complexity routing. Scans task description for domain keywords, matches against domain-complexity.csv, returns complexity level, workflow intensity, and execution tier. Extends Phase 0 orchestration.

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

Domain-Driven Design system for software development. Use when designing new systems with DDD principles, refactoring existing codebases toward DDD, generating code scaffolding (entities, aggregates, repositories, domain events), facilitating Event Storming sessions, creating bounded context maps, or performing code reviews with a DDD lens. Covers both strategic design (bounded contexts, subdomains, context maps, ubiquitous language) and tactical design (entities, value objects, aggregates, domain services, repositories). Supports all major architecture patterns (Hexagonal/Ports & Adapters, CQRS, Event Sourcing, Clean Architecture) with language-agnostic guidance and concrete examples in Python and TypeScript.

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

Monitors Certificate Transparency (CT) logs to detect unauthorized certificate issuance, discover subdomains via CT data, and alert on suspicious certificate activity for owned domains. Uses the crt.sh API and direct CT log querying based on RFC 6962 to build continuous monitoring pipelines that catch rogue certificates, track CA behavior, and map the external attack surface. Activates for requests involving certificate transparency monitoring, CT log auditing, subdomain discovery via certificates, or certificate issuance alerting.

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