Coach leaders and managers to prepare, run, and review high-bandwidth meetings that advance real work and decisions. Use for meeting retrospectives, employee work reviews, decision meetings, agenda and question design, direct feedback, meeting-quality diagnosis, or repeated low-value discussions. Preserve direct standards without taking over the worker's work or degrading the truth signal.
日本語の概要は準備中です。原文の説明を表示しています。
shareAI-lab/lab-skills☆ 3152026年9月16日 更新
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
日本語の概要は準備中です。原文の説明を表示しています。
lingxling/awesome-skills-cn☆ 3092026年10月7日 更新
Implements the UK Age Appropriate Design Code (Children's Code) 15 standards under the Data Protection Act 2018 Section 123. Covers best interests assessment, age-appropriate application, transparency, data minimization, geolocation restrictions, and profiling defaults. Keywords: AADC, Children's Code, ICO, age appropriate design, UK.
日本語の概要は準備中です。原文の説明を表示しています。
mukul975/Privacy-Data-Protection-Skills☆ 3072026年3月17日 更新
Implement the NIST Privacy Framework PROTECT function covering PR.AC access control, PR.DS data security, and PR.PO protective policies. Provides technical control implementation guidance, encryption standards, access management architectures, and security-privacy integration patterns.
日本語の概要は準備中です。原文の説明を表示しています。
mukul975/Privacy-Data-Protection-Skills☆ 3072026年3月17日 更新
Implements HIPAA Privacy Rule requirements under 45 CFR §164.500-534 for covered entities and business associates. Covers minimum necessary standard, treatment-payment-operations exceptions, directory opt-out, personal representative rules, and authorization requirements. Keywords: HIPAA Privacy Rule, PHI, minimum necessary, TPO, authorization, covered entity.
日本語の概要は準備中です。原文の説明を表示しています。
mukul975/Privacy-Data-Protection-Skills☆ 3072026年3月17日 更新
Guides compliance with South Korea's Personal Information Protection Act (PIPA, 개인정보 보호법). Covers pseudonymisation framework, notification requirements, PIPC enforcement, consent standards, and cross-border transfer rules under the 2023 amendments. Keywords: PIPA, Korea data protection, PIPC, pseudonymisation, consent, cross-border transfers.
日本語の概要は準備中です。原文の説明を表示しています。
mukul975/Privacy-Data-Protection-Skills☆ 3072026年3月17日 更新
Implements HIPAA minimum necessary standard under 45 CFR §164.502(b). Covers role-based access policies per workforce member category, routine vs non-routine disclosure protocols, reasonable reliance doctrine, documentation requirements, and HITECH amendments. Keywords: minimum necessary, role-based access, workforce, routine disclosure, HIPAA.
日本語の概要は準備中です。原文の説明を表示しています。
mukul975/Privacy-Data-Protection-Skills☆ 3072026年3月17日 更新
Guides compliance with China's Personal Information Protection Law (PIPL, effective 1 November 2021). Covers consent requirements, cross-border transfer mechanisms (CAC security assessment, standard contracts, certification), separate consent triggers, and critical information infrastructure obligations. Keywords: PIPL, China data protection, CAC security assessment, cross-border transfer, separate consent, CIIO.
日本語の概要は準備中です。原文の説明を表示しています。
mukul975/Privacy-Data-Protection-Skills☆ 3072026年3月17日 更新
Guides managing conflicting privacy requirements across jurisdictions. Covers data localisation vs transfer freedom, consent standards variation, age thresholds, breach timelines, and resolution frameworks for incompatible obligations. Keywords: conflicting laws, data localisation, consent variation, age thresholds, resolution framework.
日本語の概要は準備中です。原文の説明を表示しています。
mukul975/Privacy-Data-Protection-Skills☆ 3072026年3月17日 更新
Implements strict data minimization and retention limits for children's personal data under GDPR Art. 5(1)(c), Recital 38, UK AADC Standard 8, and COPPA Section 312.7. Covers strict necessity testing, shorter retention periods, limited profiling, parental dashboard design, and automated deletion. Keywords: data minimization, children, retention, necessity test, parental dashboard.
日本語の概要は準備中です。原文の説明を表示しています。
mukul975/Privacy-Data-Protection-Skills☆ 3072026年3月17日 更新
Manages deletion requests for children's personal data. Covers parental-initiated versus child-initiated requests, age of capacity assessment, identity verification, scope determination, third-party notification obligations, and regulatory timelines under GDPR Art. 17, COPPA Section 312.6, and UK AADC Standard 15. Keywords: deletion, children, right to erasure, parental request, data deletion, COPPA.
日本語の概要は準備中です。原文の説明を表示しています。
mukul975/Privacy-Data-Protection-Skills☆ 3072026年3月17日 更新
Designs and implements privacy notices for children that comply with GDPR Articles 12-14, UK AADC Standard 4, and COPPA Section 312.4. Covers plain language, visual explanations, layered information, age-appropriate vocabulary, and interactive notice elements. Keywords: children privacy notice, transparency, plain language, visual, age-appropriate, layered notice.
日本語の概要は準備中です。原文の説明を表示しています。
mukul975/Privacy-Data-Protection-Skills☆ 3072026年3月17日 更新
Implements profiling restrictions for children under GDPR Recital 71, Article 22, UK AADC Standard 12, and COPPA. Covers prohibition of behavioural advertising to children, recommendation algorithm limitations, nudge technique prohibition, and automated decision-making safeguards. Keywords: profiling, children, behavioural advertising, recommendation algorithm, AADC, automated decision.
日本語の概要は準備中です。原文の説明を表示しています。
mukul975/Privacy-Data-Protection-Skills☆ 3072026年3月17日 更新
Guides audit follow-up and verification processes including follow-up scheduling, remediation effectiveness testing, finding closure criteria, re-testing procedures, status reporting, and escalation of unremediated findings. Implements IIA Standard 2500 monitoring requirements and ISO 19011 follow-up guidance for privacy audit engagements. Keywords: audit follow-up, verification testing, finding closure, remediation effectiveness, re-testing, follow-up audit.
日本語の概要は準備中です。原文の説明を表示しています。
mukul975/Privacy-Data-Protection-Skills☆ 3072026年3月17日 更新
Conducts digital forensics investigations following a personal data breach, covering evidence preservation, chain of custody documentation, log analysis, scope determination, and root cause analysis. References industry-standard tools including Splunk, ELK Stack, and Wireshark. Provides forensic workflow from initial evidence collection through final investigation report. Keywords: digital forensics, breach investigation, evidence preservation, chain of custody, root cause analysis, Splunk, ELK, Wireshark.
日本語の概要は準備中です。原文の説明を表示しています。
mukul975/Privacy-Data-Protection-Skills☆ 3072026年3月17日 更新
Guides privacy audit evidence collection processes including evidence planning, sampling strategies, documentation standards, chain of custody, interview techniques, system walkthrough procedures, and evidence evaluation. Covers ISO 19011 evidence categories (records, statements of fact, observations) and ISACA audit evidence requirements for privacy compliance assessments. Keywords: audit evidence, evidence collection, sampling, chain of custody, audit documentation, interview techniques.
日本語の概要は準備中です。原文の説明を表示しています。
mukul975/Privacy-Data-Protection-Skills☆ 3072026年3月17日 更新
OI-3 spike harness — the INLINE (non-forked) readability-guidance variant. Surfaces the shared readability standard into the calling skill's own context. Use only when a spike consumer skill invokes it.
日本語の概要は準備中です。原文の説明を表示しています。
testdouble/han☆ 3032026年10月15日 更新
OI-3 spike harness — heavy consumer skill, INLINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow via an inline (non-forked) guidance skill. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.
日本語の概要は準備中です。原文の説明を表示しています。
testdouble/han☆ 3032026年10月15日 更新
Surfaces Han's shared standard for explaining technical work to a reader who will not implement it into the calling skill's own context, so the caller writes its escalations, confirmation turns, and stops as a concrete outcome the reader could observe rather than as a mechanism. Use when a skill is about to ask a person a question, stop for an input, or explain a technical consequence to someone who will not open the code. Governs what a run says to a person in a turn, where readability-guidance governs the shape of a written deliverable. Runs in the caller's context and hands control straight back; it does not produce a deliverable of its own, rewrite anything, or judge the caller's work. Carries guidance only and adds no self-check step.
日本語の概要は準備中です。原文の説明を表示しています。
testdouble/han☆ 3032026年10月15日 更新
OI-3 spike harness — heavy consumer skill, BASELINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow by reading a file directly, with NO Skill-tool call. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.
日本語の概要は準備中です。原文の説明を表示しています。
testdouble/han☆ 3032026年10月15日 更新
OI-3 spike harness — heavy consumer skill, FORKED arm. Builds an incident post-mortem and sources the readability standard mid-workflow via a forked (context fork) guidance skill. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.
日本語の概要は準備中です。原文の説明を表示しています。
testdouble/han☆ 3032026年10月15日 更新
Write RULES.md, the project standards the AI must follow, with registry-verified dependency versions and permanent rule IDs.
日本語の概要は準備中です。原文の説明を表示しています。
nurettincoban/ai-prd-workflow☆ 3012026年10月9日 更新
Audit and recommend improvements for a repository's agent-readable context, including AGENTS.md, CLAUDE.md, WARP.md, CONTRIBUTING.md, .agents/skills, and specs/ PRODUCT.md and TECH.md contracts. Use when asked to review, score, assess, or standardize repo instructions, agent onboarding, spec workflows, or cross-repo agent-context conventions. Use agentsmd-scaffold instead when the user wants to generate or apply root/scoped AGENTS.md files.
日本語の概要は準備中です。原文の説明を表示しています。
majiayu000/spellbook☆ 2882026年10月8日 更新
Design, audit, or implement application structured logging architecture from repository evidence. Use when a user asks whether or where to add logs, how to choose or migrate a logger, how to standardize events/fields/levels/redaction, how to add HTTP access or panic logs, or why production logs cannot answer an incident question. Do not use merely to tail platform logs or to design a full metrics, tracing, SLO, and incident-management program.
日本語の概要は準備中です。原文の説明を表示しています。
majiayu000/spellbook☆ 2882026年10月8日 更新