Skip to content
Back to skills

Tensorflow Privacy

ASecurity

"Routes TensorFlow Privacy users who need differentially private

  • 247 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 9, 2026
businesspythonbash

Works with

  • cli

Security analysis

A92/100
  • mediumInstalls packages at runtime which could introduce malicious dependencies

Pro scans all 20 files and shows the line behind each finding

Scanned September 9, 2026

npx -y skills add VectorSpaceLab/AREX-Skill --skill tensorflow-privacy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Tensorflow Privacy?

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

Security grade badge for Tensorflow Privacy
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vectorspacelab-tensorflow-privacy/badge)](https://www.skillsdirectory.com/skills/vectorspacelab-tensorflow-privacy)

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: tensorflow-privacy
description: "Routes TensorFlow Privacy users who need differentially private
  training, privacy accounting, query mechanisms, empirical privacy tests, or
  fast gradient clipping."
disable-model-invocation: true
metadata:
  disco-role: operating
license: Apache 2.0
---

# TensorFlow Privacy

Use this skill for TensorFlow Privacy workflows: DP-SGD training, privacy-budget accounting, lower-level DP queries, membership inference and secret-sharer analysis, and fast gradient clipping.

## Start here

Read `references/install-and-scope.md` before installing or choosing a route. It captures the minimum verified CPU-only environment, the published package names, and the optional paths that are out of scope for the default runtime.

Run `scripts/check_env.py` when you want a quick import and smoke check against an installed environment.

Read `references/repo-provenance.md` when you need to check whether this skill matches the current TensorFlow Privacy checkout, or before refreshing the skill after repo drift.

## Route map

- `sub-skills/training/` — differentially private training with optimizers, Keras model wrappers, estimators, and logistic regression helpers.
- `sub-skills/privacy-accounting/` — epsilon, delta, and noise-multiplier calculations plus the privacy accounting CLIs.
- `sub-skills/queries/` — lower-level `DPQuery` stacks, Gaussian/discrete/Skellam mechanisms, and tree aggregation query helpers.
- `sub-skills/privacy-tests/` — membership inference, privacy reports, callbacks, and secret-sharer exposure analysis.
- `sub-skills/fast-clipping/` — fast gradient clipping, layer registries, and sparse-noise helpers.

## Package surface

The public Python package is `tensorflow_privacy`. The repo also ships empirical privacy-test modules under the same import tree.

Typical install choices:

- Published packages: `pip install tensorflow-privacy tensorflow-empirical-privacy`
- Working from a checkout: install the repo's runtime requirements first, then editable install the root package

Minimal import check:

```bash
python -I -c "import tensorflow_privacy; print(tensorflow_privacy.__version__)"
```

If you want a slightly stronger check, inspect the public privacy-accounting helper too:

```bash
python -I -c "from tensorflow_privacy.privacy.analysis import compute_dp_sgd_privacy_lib as cdp; print(cdp.compute_dp_sgd_privacy_statement)"
```

## How to choose a sub-skill

If the task is about training a differentially private model, start with `training`.
If the task is about epsilon/noise calculation or the privacy CLI flags, start with `privacy-accounting`.
If the task is about custom mechanisms or DPQuery internals, start with `queries`.
If the task is about membership inference, privacy reports, or secret sharing, start with `privacy-tests`.
If the task is about faster clipping or sparse-noise internals, start with `fast-clipping`.

## Cross-cutting caution

This skill's minimum verified environment is CPU-only. GPU or TPU helpers are optional and should only be claimed when the user explicitly asks for them and the matching hardware and package variant are available.

Do not expect the original repository checkout to remain available at runtime. Use the bundled references and scripts inside this skill tree instead of source checkout paths.

Files in this skill

  • SKILL.md3.3 KB
  • references/api-overview.md3 KB
  • references/install-and-scope.md2.3 KB
  • references/repo-provenance.md1.3 KB
  • references/repo-routing-metadata.json332 B
  • references/troubleshooting.md4.1 KB
  • scripts/check_env.py1.4 KB
  • sub-skills/fast-clipping/SKILL.md2.1 KB
  • sub-skills/fast-clipping/references/api-reference.md3 KB
  • sub-skills/fast-clipping/references/troubleshooting.md2 KB
  • sub-skills/fast-clipping/scripts/tiny_fast_clipping_smoke.py1.7 KB
  • sub-skills/privacy-accounting/SKILL.md2.2 KB
  • sub-skills/privacy-accounting/references/api-reference.md2 KB
  • sub-skills/privacy-accounting/references/troubleshooting.md2.1 KB
  • sub-skills/privacy-accounting/scripts/compute_dp_sgd_privacy.py2.3 KB
  • sub-skills/privacy-accounting/scripts/compute_noise_from_budget.py1.7 KB
  • sub-skills/privacy-tests/SKILL.md2 KB
  • sub-skills/privacy-tests/references/api-reference.md3.6 KB
  • sub-skills/privacy-tests/references/troubleshooting.md2.5 KB
  • sub-skills/privacy-tests/scripts/tiny_mia_smoke.py1.2 KB

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.

Comments

Loading comments…