Skip to content

jeremylongshore/tons-of-skills-marketplace / plugins/business-tools/general-legal-assistant/skills/freelancer-review

freelancer-review

Verified

Review a freelancer's supplied agreement across fourteen commercial lenses, with clause evidence, actual-work questions and scoped classification limits. Use when assessing a client or independent-contractor agreement. Trigger with "freelancer-review" or "review this contract as a freelancer".

FileKindSize
SKILL.mdskill md6.7 KB
references/freelancer-review-lenses.mdmarkdown4.7 KB

references/freelancer-review-lenses.md

View on GitHub
# Freelancer review lenses

## Fourteen commercial lenses

Use relevant lenses as questions, not universally required protections or a
classification/fairness score.

| Lens                  | Evidence and questions                                                                                           |
| --------------------- | ---------------------------------------------------------------------------------------------------------------- |
| Worker classification | Contract wording versus actual control, financial arrangements and relationship; which legal/tax regime applies? |
| IP ownership          | Defined deliverables/materials, assignment/license wording, background IP, exclusions and related terms.         |
| Payment terms         | Invoice trigger, acceptance conditions, due dates, disputed amounts and remedies actually stated.                |
| Payment amount        | Supplied rate, scope, currency, expenses and revision costs; no market-fairness claim without a benchmark.       |
| Cancellation          | Notice, work-in-progress fees, committed expenses, deposits and stated cancellation charges.                     |
| Scope definition      | Deliverables, milestones, assumptions, dependencies and acceptance criteria.                                     |
| Scope changes         | Who approves changes, how they are documented, and how time/price adjusts.                                       |
| Non-compete           | Restricted activities, duration, geography and user goals; enforceability is a separate applicable-law question. |
| Non-solicitation      | Restricted contacts/activities, exceptions and duration, with context for legal review.                          |
| Confidentiality       | Covered information, exceptions, disclosures, duration and interaction with portfolio use.                       |
| Termination rights    | Each party's triggers, notice/cure, fees and continuing duties.                                                  |
| Liability/insurance   | Caps, exceptions, indemnities and insurance requirements considered together.                                    |
| Dispute process       | Forum, procedure, fees and practical accessibility for the user.                                                 |
| Credit/portfolio      | Attribution, publication permissions, timing, confidentiality and license dependencies.                          |

For each relevant lens, record source locators, observed terms, missing facts,
possible effect and next question. Not relevant requires a reason; unreviewed
material is not a pass. Priorities must follow actual objectives and obligations.

## Classification evidence and limits

Reviewed 2026-10-25: [IRS independent-contractor guidance](https://www.irs.gov/businesses/small-businesses-self-employed/independent-contractor-self-employed-or-employee)
groups control/independence evidence under behavior, finances and relationship.
Its common-law discussion evaluates the whole relationship; no fixed count of
factors or isolated factor decides status. This is US federal employment-tax
guidance, not a universal test for labor law, state law or other jurisdictions.

A historical factor list can suggest questions when relevant to an identified
regime, but do not invent numerical cutoffs or classify someone from a contract
alone. Record which facts come from text, the user or verified sources. If the
applicable scheme or facts are unknown, leave the conclusion unresolved.

[IRS Form SS-8 information](https://www.irs.gov/forms-pubs/about-form-ss-8) describes
an official federal-tax determination process. Linking it is not authorization to
prepare, file or contact an agency. Such action is a separate requested workflow.

## Preferences, recommendations and evidence

Treat desired payment periods, deposits, cancellation compensation, revision
limits and portfolio rights as user goals unless a verified applicable rule or
contract term establishes a legal entitlement. Do not call a custom checklist a
statutory bill of rights or infer market standards from a template.

Present options with their tradeoffs and required facts. If drafting is requested,
label original proposed language and business assumptions. If a template is used,
verify its actual source, version, relevant text and license before attributing or
copying it. Do not invent a template section or default percentage.

## Report review

Check party mapping, coverage, clause quotations and cross-references, actual-work
facts, priority rationale and unresolved legal/tax questions. Preserve original
contracts and save only the requested report. A numeric preference score, if
explicitly requested, must not be represented as a classification probability or
legal approval.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall