Skip to content
Back to skills

Tensorflow

ASecurity

Avoid common TensorFlow mistakes — tf.function retracing, GPU memory, data pipeline bottlenecks, and gradient traps.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 11, 2026
code-qualitypythongotestingdebugging

Security analysis

A100/100

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

Scanned November 11, 2026

npx -y skills add johnalbertini14-glitch/openclaw-skills --skill tensorflow --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Tensorflow?

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

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

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
description: Avoid common TensorFlow mistakes — tf.function retracing, GPU memory, data pipeline bottlenecks, and gradient traps.
metadata: {"clawdbot":{"emoji":"🧠","requires":{"bins":["python3"]},"os":["linux","darwin","win32"]}}
---

## tf.function Retracing
- New input shape/dtype causes retrace — expensive, prints warning
- Use `input_signature` for fixed shapes — `@tf.function(input_signature=[tf.TensorSpec(...)])`
- Python values retrace — pass as tensors, not Python ints/floats
- Avoid Python side effects in tf.function — only runs once during tracing

## GPU Memory
- TensorFlow grabs all GPU memory by default — set `memory_growth=True` before any ops
- `tf.config.experimental.set_memory_growth(gpu, True)` — must be called before GPU init
- OOM with large models — reduce batch size or use gradient checkpointing
- `CUDA_VISIBLE_DEVICES=""` to force CPU — for testing without GPU

## Data Pipeline
- `tf.data.Dataset` without `.prefetch()` — CPU/GPU idle time between batches
- `.cache()` after expensive ops — but before random augmentation
- `.batch()` before `.map()` for vectorized ops — faster than per-element
- `num_parallel_calls=tf.data.AUTOTUNE` — parallel preprocessing
- Dataset iteration in eager mode is slow — use in tf.function or model.fit

## Shape Issues
- First dimension is batch — `None` for variable batch size in Input layer
- `model.build(input_shape)` if not using Input layer — or first call errors
- Reshape errors unclear — `tf.debugging.assert_shapes()` for debugging
- Broadcasting silently succeeds — may hide shape bugs

## Gradient Tape
- Variables watched by default — tensors need `tape.watch(tensor)`
- `persistent=True` for multiple gradients — otherwise tape consumed after first use
- `tape.gradient` returns None if no path — check for disconnected graph
- `@tf.custom_gradient` for custom backward — not all ops have gradients

## Training Gotchas
- `model.trainable = False` after compile does nothing — set before compile
- BatchNorm behaves differently in training vs inference — `training=True/False` matters
- `model.fit` shuffles by default — `shuffle=False` for time series
- `validation_split` takes from end — shuffle data first if order matters

## Saving Models
- `model.save()` saves everything — architecture, weights, optimizer state
- `model.save_weights()` only weights — need model code to restore
- SavedModel format for serving — `tf.saved_model.save(model, path)`
- H5 format limited — doesn't save custom objects well, use SavedModel

## Common Mistakes
- Mixing Keras and raw tf ops incorrectly — use `layers.Lambda` to wrap tf ops in Sequential
- `tf.print` vs Python print — Python print only runs at trace time in tf.function
- NumPy ops in graph — use tf ops, numpy executes eagerly only
- Loss returns scalar per sample — Keras averages, custom loops may need `tf.reduce_mean`

Files in this skill

  • SKILL.md2.9 KB
  • _meta.json277 B

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 code-quality →

Comments

Loading comments…

Newsletter

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