Skip to content
Back to skills

Legal Skill Operations

ASecurity

Consolidated workflow layer copied and merged from legal-builder-hub. Use this skill as the exposed entry point while preserving detailed source workflows under references/source-workflows.

  • 417 stars
  • 0 votes
  • 0 copies
  • 6 views
  • Added September 8, 2026
documentationgo

Security analysis

A100/100

Scanned September 8, 2026

npx -y skills add infometa/workbuddyskills --skill legal-skill-operations --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Legal Skill Operations?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Legal Skill Operations
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/infometa-legal-skill-operations/badge)](https://www.skillsdirectory.com/skills/infometa-legal-skill-operations)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: legal-skill-operations
description: Consolidated workflow layer copied and merged from legal-builder-hub. Use this skill as the exposed entry point while preserving detailed source workflows under references/source-workflows.
---

# Legal Skill Operations Workflows

This skill is a merged entry point. The porting method is copy → merge → modify → optimize:

1. Source README / practice profile / SKILL.md / agent markdown files were copied into `references/source-workflows/`.
2. Hook and slash-command behavior was removed because this marketplace uses experts, agents, and skills.
3. The exposed skill below consolidates the copied source workflows into a smaller routing surface.
4. Local adaptation should be done cautiously through jurisdiction notes, not by replacing the source workflow wholesale.

## Copied source materials

See `references/source-workflows/` in this plugin for the debranded source workflow text used during consolidation.

## Consolidated behavior

## Capabilities

- legal skill intake and catalog review
- related skill surfacing from approved local materials
- skills QA and hidden-instruction review
- license, freshness, and tool-scope gates
- update impact review for internally maintained skills
- disable / retirement recommendations for unsafe or stale skills

## Operating rule

Use this as a structured checklist. Do not treat it as legal advice or a substitute for qualified legal review.
## Working across jurisdictions

Use the source workflow as the operating skeleton, but read the matter through the jurisdiction the user is actually working in. If the facts point to China or another non-US setting, first anchor the analysis in the applicable law, regulator, industry, contract language, and document purpose. Keep the familiar review flow, while translating only the parts that are jurisdiction-shaped: legal labels, deadlines, regulator references, employment classifications, data-protection vocabulary, and court or filing procedures.

When the local rule is not in the provided materials or a current source you can inspect, say so naturally in the analysis and treat it as something for counsel to verify. The goal is a localized draft that still feels like the original workflow, not a new legal product rebuilt from scratch.


## Legal-output boundary

Outputs are lawyer-review drafts, not legal advice. Mark assumptions, sources, and attorney-review points.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in documentation →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.