lawyer-analyst

Other Community v1.0.0
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Other
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
89 / 100 · community maintained
Author / version / license
@rysweet · v1.0.0 · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No special requirements
Permissions
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools,默认拥有全部工具权限。; 上游仓库已 198 天未更新,可能与最新 agent 行为不一致。

Output preview lawyer-analyst.preview
---
name: lawyer-analyst
description: | Analyze events through the disciplinary lens of law, applying rigorous legal methodologies (st…
category: other
runtime: no special runtime
---

# lawyer-analyst output preview

## PART A: Task fit
- Use case: | Analyze events through the disciplinary lens of law, applying rigorous legal methodologies (statutory interpretation, case law analysis, legal reasoning), constitutional principles, procedural frameworks, substantive legal doctrines across multiple domains (contracts, torts, property, criminal, constitutional, administrative, international), and profess….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Purpose / When to Use This Skill / Core Philosophy: Legal Thinking” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “| Analyze events through the disciplinary lens of law, applying rigorous legal methodologies (statutory interpretation, case law analysis, legal reasoning), constitutional principles, procedural frameworks, substantive legal doctrines across multiple domains (contracts, torts, property, criminal, constitutional, administrative, international), and profess…”.
- **02** When the source has headings, the agent prioritizes “Purpose / When to Use This Skill / Core Philosophy: Legal Thinking” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.
Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

  • Core job: | Analyze events through the disciplinary lens of law, applying rigorous legal methodologies (statutory interpretation, case law…
  • Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
  • Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

  • Structure: The skill is organized around “Purpose”, “When to Use This Skill”, “Core Philosophy: Legal Thinking”, “Theoretical Foundations (Expandable)”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
  • Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
  • Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

  • Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
  • Invocation: Name lawyer-analyst directly; if the source includes slash commands, start with the command and then add task context.
  • Validation: Start small and check whether the result follows “Purpose / When to Use This Skill / Core Philosophy: Legal Thinking” before expanding.

Boundaries And Review

  • Dependencies: It usually needs no extra API key, so start with a small validation task.
  • Permissions: Declared permissions include read / write / shell-exec; ask the agent to state file, command, and rollback boundaries before acting.
  • Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.