{"id":5584,"plugin_id":"plugin_asdk_app_695bfc98071c8191bac7bc479aa27de7","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T22:45:27.071Z","digest":"c6a142eb375a2e884b136f0794a3fed019bed2ff47625d7cd57a1b9dd3fb03e1","against":null,"payload":{"name":"box-legal-workflows-ocg","description":"Review outside counsel guidelines, billing guidelines, and outside counsel requirements in Box. Use to compare an OCG with a firm playbook, identify cited obligations or variances, recommend responsible teams, draft an issue register, or add one cited Box comment per issue.","included_files":[],"skill_md_contents":"---\nname: box-legal-workflows-ocg\ndescription: \"Review outside counsel guidelines, billing guidelines, and outside counsel requirements in Box. Use to compare an OCG with a firm playbook, identify cited obligations or variances, recommend responsible teams, draft an issue register, or add one cited Box comment per issue.\"\n---\n\n# OCG review in Box\n\nUse the `box` skill for authentication and operations. For mechanics, use `box/references/ai-and-retrieval.md` and `box/references/collaboration.md` as relevant.\n\n## Assessment basis\n\n- **Playbook comparison:** Use an applicable firm playbook, approved position, or review standard as the baseline. Report a variance only when a cited OCG term differs from a cited firm control, position, threshold, or process. If the playbook is silent, label the item **uncovered requirement**.\n- **OCG-only operational assessment:** Use after the user confirms that no playbook will be used. An explicit statement such as “we do not have a playbook” is already confirmation—proceed without asking again. Identify obligations, ambiguities, internal conflicts, approvals, deadlines, and likely process effects; do not claim firm-policy deviation or noncompliance.\n\nChoose the basis before issue analysis. If the user supplied a playbook, use it. If they explicitly said none exists or should be used, proceed OCG-only. Otherwise ask them to identify the applicable playbook; do not silently assume either basis.\n\n## Workflow\n\n1. Resolve the intended OCG and record its Box file ID and version. Apply the assessment-basis rule above, and record the baseline file ID and version when a playbook is used.\n2. Review every section, subsection, schedule, and appendix. Maintain an internal ledger with section, locator, requirements, assessment basis, status, and issue IDs. Return a compact coverage summary unless the user asks for the full ledger.\n3. If any material is unreadable, truncated, unsupported, or otherwise unrepresented, identify the gap and continue with the assessable sections without claiming complete review.\n4. For each issue, cite the OCG and the playbook when applicable. Separate source facts, supported impact, model inference, and attorney decisions.\n5. Recommend the team with the first concrete action. Use a firm ownership map when available; otherwise use the fallback below. Treat routing as a recommendation, not a binding assignment.\n6. If the user asked only for review or drafting, return the issue preview and do not post comments. If they explicitly asked to add comments, create one self-contained comment per independent issue without another confirmation round, then verify and retain the comment IDs. Clarify only when write-back intent is ambiguous.\n7. Report the assessment basis, source versions, coverage gaps, issue and written-comment counts, recommended teams, unresolved attorney decisions, relevant Box IDs, and failures. If a source changes during review, state that the result applies to the recorded version.\n\n## Issue taxonomy and citations\n\nUse the narrowest applicable label: **playbook variance**, **process change**, **approval or exception**, **deadline or reporting duty**, **ambiguity**, **internal conflict**, **uncovered requirement**, or **attorney decision**.\n\nSplit independent requirements when their impacts, owners, or resolutions differ. Keep related text together when separating it would make the issue misleading.\n\nPrefer section or subsection number and heading, then a verified page, numbered paragraph or line, then a short identifying excerpt. Cite the original files rather than an AI answer and never invent locators.\n\n## Fallback owner routing\n\n- Rates, budgets, invoices, time-entry, e-billing: **Billing Operations**; support from Matter Team or Finance\n- Staffing, matter plans, status reports: **Matter Team**; support from Legal Operations\n- Engagement terms, conflicts, ethics, privilege: **Responsible Attorney**; support from Ethics or General Counsel\n- Security, breach notice, access controls: **Information Security**; support from Privacy or Matter Team\n- Personal data, transfers, privacy retention: **Privacy**; support from Information Security or Records\n- Records, destruction, holds, file return: **Records Management**; support from Matter Team or Privacy\n- Diversity or supplier reporting: **Legal Operations**; support from HR/DEI or Matter Team\n- Taxes, payment terms, currency, expenses: **Finance**; support from Billing Operations\n- Insurance: **Risk Management**; support from Finance or Responsible Attorney\n- Publicity or client-name use: **Marketing/Communications**; support from Responsible Attorney\n- Portals and technical onboarding: **IT**; support from Information Security or Legal Operations\n- Client-owned business terms or obligations: **Client Legal/Business Team**; support from Matter Team\n\nUse a firm-provided map instead. Add a supporting team only when needed. Never infer a person's identity; keep the team label when identity is ambiguous, and do not claim a plain comment creates a targeted mention or notification.\n\n## Issue preview and comment format\n\nFor each issue include a stable ID, citation, requirement, variance or concern, concrete impact, suggested resolution, recommended owner, and any attorney decision.\n\nBefore commenting, check the file's audience. Do not expose confidential playbook text or privileged internal analysis in a comment visible to client or external collaborators; put detailed comparison in a restricted internal artifact when necessary.\n\nUse this shape and shorten it to the current tool limit without dropping its required elements:\n\n```text\nCitation: [verified OCG locator; playbook locator only when appropriate for the audience]\nRisk/impact: [supported consequence; label inference or attorney judgment]\nSuggested resolution: [practical option and any required approval]\nRecommended owner: [team label]\n```\n\n## Legal boundary\n\nDescribe concrete operational or legal-review impact, but do not provide final legal advice, approve a deviation, set a binding risk rating, or make a binding assignment.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}