executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
export-and-saveCreate TensorFlow Hub-consumable TF2 SavedModels and export text embedding SavedModels.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task is to create a TensorFlow Hub-consumable TF2 SavedModel, prepare a local model for later use with tensorflow_hub.load or tensorflow_hub.KerasLayer, or export a text embedding model from token/vector text files.
Do not use this sub-skill as a current recipe for legacy TF1 TensorFlow Hub Module publishing. In this package version, the current top-level public API is tensorflow_hub.load, tensorflow_hub.resolve, and tensorflow_hub.KerasLayer; legacy top-level publishers such as Module, create_module_spec, load_module_spec, add_signature, and attach_message are absent.
tf.Module or Keras SavedModel export patterns, read references/savedmodel-export.md.tf.Module/Keras object, an explicit signature, or the bundled text embedding workflow.SavedModel with tf.saved_model.save(...). Give callable models an @tf.function __call__ with an input_signature; give signature-only models explicit named signatures.tensorflow_hub.load(export_path). For Keras integration, validate with tensorflow_hub.KerasLayer(...) using signature and output_key when the SavedModel exposes only a dict signature.load-and-wrap sub-skill via the TensorFlow Hub root router.python scripts/export_text_embeddings_v2.py \
--embedding-file embeddings.txt \
--export-path exported_text_embedding \
--verify \
--sample-text "cat dog" --sample-text "unknown-token" ""
The embedding file must contain one whitespace-separated token and numeric vector per line. The exporter writes a TF2 SavedModel, not a legacy TF1 TensorFlow Hub Module.