[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CST8Z0WY2ENMY09GE2JQDR":3,"skill-same:01M7CST8Z0WY2ENMY09GE2JQDR":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7CST8Z0WY2ENMY09GE2JQDR","brief",null,"Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.","Henrique1601\u002FSkiilsToIAs","Henrique1601","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92006691?v=4","01M7CRXVT0GVXVK80JT1GR687S","Henrique Bezerra Dos Santos","01M7CRXVTN5Y8TMWJ1MDSKCQ1T",0,"MIT","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fbusiness-management\u002Fbrief\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: brief\ndescription: Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.\nargument-hint: \"[daily | topic \u003Cquery> | incident]\"\n---\n\n# \u002Fbrief -- Legal Team Briefing\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nGenerate contextual briefings for legal work. Supports three modes: daily brief, topic brief, and incident brief.\n\n**Important**: This command assists with legal workflows but does not provide legal advice. Briefings should be reviewed by qualified legal professionals before being relied upon.\n\n## Invocation\n\n```\n\u002Fbrief daily              # Morning brief of legal-relevant items\n\u002Fbrief topic [query]      # Research brief on a specific legal question\n\u002Fbrief incident [topic]   # Rapid brief on a developing situation\n```\n\nIf no mode is specified, ask the user which type of brief they need.\n\n## Modes\n\n---\n\n### Daily Brief\n\nA morning summary of everything a legal team member needs to know to start their day.\n\n#### Sources to Scan\n\nCheck each connected source for legal-relevant items:\n\n**Email (if connected):**\n- New contract requests or review requests\n- Compliance questions or reports\n- Responses from counterparties on active negotiations\n- Flagged or urgent items from the legal team inbox\n- External counsel communications\n- Regulatory or legal update newsletters\n\n**Calendar (if connected):**\n- Today's meetings that need legal prep (board meetings, deal reviews, vendor calls)\n- Upcoming deadlines this week (contract expirations, filing deadlines, response deadlines)\n- Recurring legal team syncs\n\n**Chat (if connected):**\n- Overnight messages in legal team channels\n- Direct messages requesting legal input\n- Mentions of legal-relevant topics (contract, compliance, privacy, NDA, terms)\n- Escalations or urgent requests\n\n**CLM (if connected):**\n- Contracts awaiting review or signature\n- Approaching expiration dates (next 30 days)\n- Newly executed agreements\n\n**CRM (if connected):**\n- Deals moving to stages that require legal involvement\n- New opportunities flagged for legal review\n\n#### Output Format\n\n```\n## Daily Legal Brief -- [Date]\n\n### Urgent \u002F Action Required\n[Items needing immediate attention, sorted by urgency]\n\n### Contract Pipeline\n- **Awaiting Your Review**: [count and list]\n- **Pending Counterparty Response**: [count and list]\n- **Approaching Deadlines**: [items due this week]\n\n### New Requests\n[Contract review requests, NDA requests, compliance questions received since last brief]\n\n### Calendar Today\n[Meetings with legal relevance and what prep is needed]\n\n### Team Activity\n[Key messages or updates from legal team channels]\n\n### This Week's Deadlines\n[Upcoming deadlines and filing dates]\n\n### Sources Not Available\n[Any sources that were not connected or returned errors]\n```\n\n---\n\n### Topic Brief\n\nResearch and brief on a specific legal question or topic across available sources.\n\n#### Workflow\n\n1. Accept the topic query from the user\n2. Search across connected sources:\n   - **Documents**: Internal memos, prior analyses, playbooks, precedent\n   - **Email**: Prior communications on the topic\n   - **Chat**: Team discussions about the topic\n   - **CLM**: Related contracts or clauses\n3. Synthesize findings into a structured brief\n\n#### Output Format\n\n```\n## Topic Brief: [Topic]\n\n### Summary\n[2-3 sentence executive summary of findings]\n\n### Background\n[Context and history from internal sources]\n\n### Current State\n[What the organization's current position or approach is, based on available documents]\n\n### Key Considerations\n[Important factors, risks, or open questions]\n\n### Internal Precedent\n[Prior decisions, memos, or positions found in internal sources]\n\n### Gaps\n[What information is missing or what sources were not available]\n\n### Recommended Next Steps\n[What the user should do with this information]\n```\n\n#### Important Notes\n- Topic briefs synthesize what is available in connected sources; they do not substitute for formal legal research\n- If the topic requires current legal authority or case law, recommend the user consult a legal research platform (Westlaw, Lexis, etc.) or outside counsel\n- Always note the limitations of the sources searched\n\n---\n\n### Incident Brief\n\nRapid briefing for developing situations that require immediate legal attention (data breaches, litigation threats, regulatory inquiries, IP disputes, etc.).\n\n#### Workflow\n\n1. Accept the incident topic or description\n2. Rapidly scan all connected sources for relevant context:\n   - **Email**: Communications about the incident\n   - **Chat**: Real-time discussions and escalations\n   - **Documents**: Relevant policies, response plans, insurance coverage\n   - **Calendar**: Scheduled response meetings\n   - **CLM**: Affected contracts, indemnification provisions, insurance requirements\n3. Compile into an actionable incident brief\n\n#### Output Format\n\n```\n## Incident Brief: [Topic]\n**Prepared**: [timestamp]\n**Classification**: [severity assessment if determinable]\n\n### Situation Summary\n[What is known about the incident]\n\n### Timeline\n[Chronological summary of events based on available sources]\n\n### Immediate Legal Considerations\n[Regulatory notification requirements, preservation obligations, privilege concerns]\n\n### Relevant Agreements\n[Contracts, insurance policies, or other agreements that may be implicated]\n\n### Internal Response\n[What response activity has already occurred based on email\u002Fchat]\n\n### Key Contacts\n[Relevant internal and external contacts identified from sources]\n\n### Recommended Immediate Actions\n1. [Most urgent action]\n2. [Second priority]\n3. [etc.]\n\n### Information Gaps\n[What is not yet known and needs to be determined]\n\n### Sources Checked\n[What was searched and what was not available]\n```\n\n#### Important Notes for Incident Briefs\n- Speed matters. Produce the brief quickly with available information rather than waiting for complete information\n- Flag any litigation hold or preservation obligations immediately\n- Note privilege considerations (mark the brief as attorney-client privileged \u002F work product if appropriate)\n- If the incident may involve a data breach, flag applicable notification deadlines (e.g., 72 hours for GDPR)\n- Recommend outside counsel engagement if the matter is significant\n\n## General Notes\n\n- If sources are unavailable, note the gaps prominently so the user knows what was not checked\n- For daily briefs, learn the user's preferences over time (what they find useful, what they want filtered out)\n- Briefs should be actionable: every item should have a clear next step or reason for inclusion\n- Keep briefs concise. Link to source materials rather than reproducing them in full\n","# \u002Fbrief -- Legal Team Briefing\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nGenerate contextual briefings for legal work. Supports three modes: daily brief, topic brief, and incident brief.\n\n**Important**: This command assists with legal workflows but does not provide legal advice. Briefings should be reviewed by qualified legal professionals before being relied upon.\n\n## Invocation\n\n```\n\u002Fbrief daily              # Morning brief of legal-relevant items\n\u002Fbrief topic [query]      # Research brief on a specific legal question\n\u002Fbrief incident [topic]   # Rapid brief on a developing situation\n```\n\nIf no mode is specified, ask the user which type of brief they need.\n\n## Modes\n\n---\n\n### Daily Brief\n\nA morning summary of everything a legal team member needs to know to start their day.\n\n#### Sources to Scan\n\nCheck each connected source for legal-relevant items:\n\n**Email (if connected):**\n- New contract requests or review requests\n- Compliance questions or reports\n- Responses from counterparties on active negotiations\n- Flagged or urgent items from the legal team inbox\n- External counsel communications\n- Regulatory or legal update newsletters\n\n**Calendar (if connected):**\n- Today's meetings that need legal prep (board meetings, deal reviews, vendor calls)\n- Upcoming deadlines this week (contract expirations, filing deadlines, response deadlines)\n- Recurring legal team syncs\n\n**Chat (if connected):**\n- Overnight messages in legal team channels\n- Direct messages requesting legal input\n- Mentions of legal-relevant topics (contract, compliance, privacy, NDA, terms)\n- Escalations or urgent requests\n\n**CLM (if connected):**\n- Contracts awaiting review or signature\n- Approaching expiration dates (next 30 days)\n- Newly executed agreements\n\n**CRM (if connected):**\n- Deals moving to stages that require legal involvement\n- New opportunities flagged for legal review\n\n#### Output Format\n\n```\n## Daily Legal Brief -- [Date]\n\n### Urgent \u002F Action Required\n[Items needing immediate attention, sorted by urgency]\n\n### Contract Pipeline\n- **Awaiting Your Review**: [count and list]\n- **Pending Counterparty Response**: [count and list]\n- **Approaching Deadlines**: [items due this week]\n\n### New Requests\n[Contract review requests, NDA requests, compliance questions received since last brief]\n\n### Calendar Today\n[Meetings with legal relevance and what prep is needed]\n\n### Team Activity\n[Key messages or updates from legal team channels]\n\n### This Week's Deadlines\n[Upcoming deadlines and filing dates]\n\n### Sources Not Available\n[Any sources that were not connected or returned errors]\n```\n\n---\n\n### Topic Brief\n\nResearch and brief on a specific legal question or topic across available sources.\n\n#### Workflow\n\n1. Accept the topic query from the user\n2. Search across connected sources:\n   - **Documents**: Internal memos, prior analyses, playbooks, precedent\n   - **Email**: Prior communications on the topic\n   - **Chat**: Team discussions about the topic\n   - **CLM**: Related contracts or clauses\n3. Synthesize findings into a structured brief\n\n#### Output Format\n\n```\n## Topic Brief: [Topic]\n\n### Summary\n[2-3 sentence executive summary of findings]\n\n### Background\n[Context and history from internal sources]\n\n### Current State\n[What the organization's current position or approach is, based on available documents]\n\n### Key Considerations\n[Important factors, risks, or open questions]\n\n### Internal Precedent\n[Prior decisions, memos, or positions found in internal sources]\n\n### Gaps\n[What information is missing or what sources were not available]\n\n### Recommended Next Steps\n[What the user should do with this information]\n```\n\n#### Important Notes\n- Topic briefs synthesize what is available in connected sources; they do not substitute for formal legal research\n- If the topic requires current legal authority or case law, recommend the user consult a legal research platform (Westlaw, Lexis, etc.) or outside counsel\n- Always note the limitations of the sources searched\n\n---\n\n### Incident Brief\n\nRapid briefing for developing situations that require immediate legal attention (data breaches, litigation threats, regulatory inquiries, IP disputes, etc.).\n\n#### Workflow\n\n1. Accept the incident topic or description\n2. Rapidly scan all connected sources for relevant context:\n   - **Email**: Communications about the incident\n   - **Chat**: Real-time discussions and escalations\n   - **Documents**: Relevant policies, response plans, insurance coverage\n   - **Calendar**: Scheduled response meetings\n   - **CLM**: Affected contracts, indemnification provisions, insurance requirements\n3. Compile into an actionable incident brief\n\n#### Output Format\n\n```\n## Incident Brief: [Topic]\n**Prepared**: [timestamp]\n**Classification**: [severity assessment if determinable]\n\n### Situation Summary\n[What is known about the incident]\n\n### Timeline\n[Chronological summary of events based on available sources]\n\n### Immediate Legal Considerations\n[Regulatory notification requirements, preservation obligations, privilege concerns]\n\n### Relevant Agreements\n[Contracts, insurance policies, or other agreements that may be implicated]\n\n### Internal Response\n[What response activity has already occurred based on email\u002Fchat]\n\n### Key Contacts\n[Relevant internal and external contacts identified from sources]\n\n### Recommended Immediate Actions\n1. [Most urgent action]\n2. [Second priority]\n3. [etc.]\n\n### Information Gaps\n[What is not yet known and needs to be determined]\n\n### Sources Checked\n[What was searched and what was not available]\n```\n\n#### Important Notes for Incident Briefs\n- Speed matters. Produce the brief quickly with available information rather than waiting for complete information\n- Flag any litigation hold or preservation obligations immediately\n- Note privilege considerations (mark the brief as attorney-client privileged \u002F work product if appropriate)\n- If the incident may involve a data breach, flag applicable notification deadlines (e.g., 72 hours for GDPR)\n- Recommend outside counsel engagement if the matter is significant\n\n## General Notes\n\n- If sources are unavailable, note the gaps prominently so the user knows what was not checked\n- For daily briefs, learn the user's preferences over time (what they find useful, what they want filtered out)\n- Briefs should be actionable: every item should have a clear next step or reason for inclusion\n- Keep briefs concise. Link to source materials rather than reproducing them in full\n",{"name":5,"description":7,"argument-hint":24},"[daily | topic \u003Cquery> | incident]","main","a73152352c0612252131e5cf84e91312a6cf17dc","business-management\u002Fbrief","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs","https:\u002F\u002Fgithub.com\u002FHenrique1601","https:\u002F\u002Fbezerraportifolio.netlify.app\u002F","Full Stack Developer | React, Next.js, TypeScript, Node.js & IA | Construindo produtos digitais e soluções SaaS","2026-11-15 02:56:04",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Henrique1601\u002FSkiilsToIAs --skill brief",{"tool":39,"command":40},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill brief",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill brief","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fbusiness-management\u002Fbrief\u002FSKILL.md",true,[],[48,55,62,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7E2ANBW9V6AVX5JXNCEAWF8","rag-architect-agent","Agente Arquiteto de RAG, Embeddings & Busca Vetorial. Especialista em design e implementação de pipelines de Retrieval-Augmented Generation de alta fidelidade: chunking semântico, modelagem pgvector no PostgreSQL (Neon\u002FSupabase), busca híbrida (cosseno + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fcustom-agents\u002Frag-architect-agent\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7E29KKF8R02ZRGYE2MJM67G","rag-architecture-patterns","Padrões arquiteturais e implementação de pipelines RAG (Retrieval-Augmented Generation) de alta fidelidade para qualquer projeto ou sistema. Cobre chunking semântico, embeddings, busca híbrida (pgvector + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Frag-architecture-patterns\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7CWRA8E3BJ7CPY8N8EG28J1","skill-repair","Use this to fix and re-install agent skills that have failed installation.\nThis skill provides the necessary context and permissions to surgically update\nthe `manifest.json` after a fix has been applied.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fskill-repair\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7CWR66FZP8FA47WVZ4Z2EXC","security-scan","Scan your Claude Code configuration (.claude\u002F directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-scan\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7CWR0QPY58QPTR1P759TFNG","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7CWQXCE40XWT4FZ3VWZFGDP","security-bounty-hunter","Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-bounty-hunter\u002FSKILL.md",[],[]]