/cs:gc-review <plan> — General Counsel interrogation of contracts, IP, regulatory, term sheets, and employment-law surface. Use when reviewing a term sheet before signing, redlining a customer MSA, or checking IP assignment and regulatory exposure on a new product.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Command: /cs:gc-review <plan>
The General Counsel lens. Six questions before any contract, term sheet, IP move, or regulatory commitment. This is a lane gstack has zero of — and one where a single missed clause costs more than a year of engineering.
⚠️ Not legal advice. This command surfaces the right questions to ask before talking to outside counsel. Always engage qualified counsel for binding decisions.
Who owns the IP being created or shared in this transaction?
What's the liability cap, and what's carved out from it?
What personal data is involved, and is a DPA in place?
What's the termination right, what's the notice period, and what's auto-renew?
Does this expose the company to a new regulatory regime?
If this is a hire or contractor: jurisdiction, classification, equity grant, IP assignment?
# GC Review: <plan>
**Date:** YYYY-MM-DD
## Document
- Type: <contract / term sheet / grant / DPA>
- Counterparty: <name>
- $ value or scope: <amount>
## Issues
| # | Issue | Risk | Recommendation |
|---|---|---|---|
| 1 | <e.g., uncapped IP indemnity> | HIGH | Cap at fees paid, mutual |
| 2 | <e.g., 5-year auto-renew> | MED | 1-year max, 60-day notice |
| 3 | <e.g., no DPA, EU data> | HIGH | Require DPA before sign |
## Regulatory Trigger
- New regime triggered? <yes/no>
- Specific frameworks: <HIPAA / GDPR / etc.>
## Outside Counsel Action Items
- [ ] <specific item 1>
- [ ] <specific item 2>
- [ ] <specific item 3>
## Verdict
🟢 SIGN AS-IS (rare)
🟡 NEGOTIATE — counter on top-3 issues
🔴 DO NOT SIGN — material risk
/cs:ciso-review — for any data-touching contract/cs:cfo-review — for any commitment > 1 year or > 1% of revenue/cs:decide — log the verdict after outside counsel reviewgeneral-counsel-advisor skillSince v2.5.1, this command is backed by a full skill at ../../../c-level-advisor/skills/general-counsel-advisor/ with two Python tools:
# Automated contract scan (12 founder-killer patterns)
python ../../../c-level-advisor/skills/general-counsel-advisor/scripts/contract_risk_scanner.py path/to/contract.txt
# Term sheet scoring (0-100 founder-friendliness)
python ../../../c-level-advisor/skills/general-counsel-advisor/scripts/term_sheet_analyzer.py path/to/term_sheet.json
The cs-general-counsel-advisor agent orchestrates both tools plus 3 references (contracts playbook, IP + regulatory, term sheet decoder).
general-counsel-advisor — full skill with Python tools + referencescs-general-counsel-advisor../../../ra-qm-team/../../../c-level-advisor/skills/ma-playbook/Version: 1.0.0
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Accessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to generate, iterate, or scale ad creative for paid advertising. Use when they say 'write ad copy,' 'generate headlines,' 'create ad variations,' 'bulk creative,' 'iterate on ads,' 'ad copy validation,' 'RSA headlines,' 'Meta ad copy,' 'LinkedIn ad,' or 'creative testing.' This is pure creative production — distinct from paid-ads (campaign strategy). Use ad-creative when you need the copy, not the campaign plan.
日本語の概要は準備中です。原文の説明を表示しています。
Adversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.
日本語の概要は準備中です。原文の説明を表示しています。
Answer Engine Optimization (AEO) skill — optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers — 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools.
日本語の概要は準備中です。原文の説明を表示しています。
Mint a tamper-evident, post-quantum-signed receipt for a consequential agent action (deploy, delete, pay, grant-access, model decision) so it can be verified later from the certificate alone. Use when an autonomous agent takes a side-effecting action that may need to be proven later, or when satisfying EU AI Act Article 12 record-keeping. Three decisions: whether an action needs a receipt, minting it, verifying it. Signing is delegated to the open-source OpenAgentOntology package. Not after-the-fact log analysis; not a hosted notary; not a legal opinion.
日本語の概要は準備中です。原文の説明を表示しています。