sylphxai/skills

model-product-abuse-risk

Model product abuse and a least-harm control ladder.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/sylphxai/skills --skill model-product-abuse-risk

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Model Product Abuse Risk

Prefer the least harmful effective control. A high loss estimate does not justify collective punishment, secret confiscation, or inaccessible appeal. Legitimate recovery is first-class. Do not teach an attacker how to bypass the control. A score that cannot be appealed is not a control, it is an unaccountable taking.

Open abuse model and control ladder when actors, assets, or controls need depth. Open decision evidence and adaptive operations when scoring, appeals, or automation need depth.

Related by task

from this repository

More skills

All skills
sylphxai
Community

accessibility-conformance

Assess whether disabled users can complete the selected tasks, and what the current results support saying about conformance. Use when the user asks to review accessibility, audit a conformance claim, or check a VPAT or accessibility statement. Do not use to design the system under review or to fix accessibility defects.

installs
1
GitHub stars
2
Updated
Oct 3
sylphxai
Community

account-recovery

Assess account recovery — alternative authentication, recovery proof, takeover handling, and enterprise operations. Use when the user asks to review password reset, recovery flows, account takeover handling, or SSO recovery. Do not use to design the recovery flow.

installs
1
GitHub stars
2
Updated
Oct 3
sylphxai
Community

analyze-causal-inference

Estimate a causal effect with an explicit estimand, identification assumptions, design, diagnostics, and sensitivity. Use when the user asks whether a change caused an outcome, for difference-in-differences, IV, or target-trial emulation. Do not use to register a product experiment, forecast an unresolved future event, or critique a present explanation.

installs
1
GitHub stars
2
Updated
Oct 3
sylphxai
Community

analyze-critically

Stress-test a claim, plan, diagnosis, or design by writing rejection conditions before interpreting the evidence. Use when the user asks to critique, steelman, red-team, find the kill criterion, or what would change your mind. Do not use for a domain go/no-go review, a causal effect estimate, a resolvable forecast, or ordinary implementation.

installs
1
GitHub stars
2
Updated
Oct 3