secretflow
Guides SecretFlow workflows for runtime setup, federated data containers, the component CLI, preprocessing/statistics/classical ML, and privacy-oriented deployment tasks.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- secretflow
- license
- Apache 2.0
- metadata
- { "disco-role": "operating" }
- description
- Guides SecretFlow workflows for runtime setup, federated data containers, the component CLI, preprocessing/statistics/classical ML, and privacy-oriented deployment tasks.
- disable-model-invocation
- true
02 资源文件 4
- 参考文档references/repo-provenance.md1.2 KB
- 参考文档references/repo-routing-metadata.json505 B
- 参考文档references/troubleshooting.md4.4 KB
- 脚本scripts/check_secretflow_install.py1.1 KB
03 SKILL.md 正文
SecretFlow
SecretFlow is a unified framework for privacy-preserving data intelligence and
machine learning. Use this skill when the task mentions the secretflow
package, sf.init, PYU, SPU, HEU, TEEU, VDataFrame, HDataFrame,
FedNdarray, component, preprocessing, statistics, classical ML, PSI,
Kuscia, or TEE-style deployment.
Start here
- Use Python 3.10 for the most reliable runtime coverage.
- Install
secretflowin the target environment and keeppython -m pip checkclean. - Minimal import check:
python -c "import secretflow as sf; print(sf.__version__)" - If you are validating an installed environment, run
scripts/check_secretflow_install.py. - Read
references/repo-provenance.mdwhen checking whether this skill still matches the repository snapshot that produced it. - Read
references/troubleshooting.mdwhen the install, import, CLI, backend, or deployment path is failing.
Route map
sub-skills/runtime-data/
Use this route for local startup, device creation, reveal/to/wait behavior, FedNdarray, HDataFrame, VDataFrame, MixDataFrame, CSV/ORC IO, and small local simulation flows.
Typical triggers:
sf.initwithlocalor a simplecluster_configPYU,SPU,HEU,TEEUreveal,to,waitread_csv,read_orc,partition- device-mismatch or direct-to-SPU/HEU errors
sub-skills/component-cli/
Use this route for the component registry and the secretflow component
command family, component evaluation payloads, model export, serving model
inferencer, and plugin packaging.
Typical triggers:
secretflow component ls|inspect|translate|get_translation|runcomp_eval,Registry,NodeEvalParam,StorageConfig,DistData- model export or serving package generation
- plugin entry-point or component registration questions
sub-skills/analytics/
Use this route for preprocessing, statistics, score-card helpers, and direct classical ML APIs.
Typical triggers:
StandardScalerpsi_eval,table_statistics,categorical_statistics,ScoreCardSSGLM,SSRegression,FlLogisticRegressionMix,FlLogisticRegressionVertical,HESSLogisticRegressionKMeans,GNB,GPC,KNNClassifer, and related model workflows
sub-skills/privacy-orchestration/
Use this route for PSI, secure aggregation/comparison, Kuscia, TEEU simulation, and deployment-mode questions.
Typical triggers:
psi_df,psi_eval,SPUAggregator,PlainComparatorKusciaTaskConfig,get_sf_cluster_config,convert_domain_data_to_individual_tableTEEU,auth_manager, Ray/Kuscia setup, simulation/production mode choice- deployment and orchestration troubleshooting
Working style
- Read the nearest sub-skill first, then cross-reference the shared root troubleshooting guidance when something fails.
- Keep runtime instructions inside this skill tree; do not rely on the original repository checkout being present later.
- For backend-specific work, prefer the smallest environment that can truthfully cover the selected task. CPU coverage is enough for the core local runtime and component CLI paths in this skill; advanced GPU, Kuscia, or TEE paths are routed to their own guidance.
Companion files
references/repo-provenance.md— source snapshot and refresh baseline.references/repo-routing-metadata.json— router metadata for repo-skills routing.references/troubleshooting.md— cross-cutting install/import/backend issues.scripts/check_secretflow_install.py— quick environment and API smoke check.
04 同仓库更多 Skills
passnet-triton-opt
Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block/grid/warp tuning, autotune policy, launch overhead, and per-op numeric recipes to pass the dtype baseline tolerances. Use when a pass matches and is correct but speedup below expected, or when correctness fails by small numeric margins.
passnet-solve
END-TO-END playbook for solving one PassNet sample: analyze the computation graphs, decide the optimization strategy (what to fuse, what to replace, what to leave alone), drive the iteration loop, and maximize the sample score. This is the ENTRY skill — invoke it first for any PassNet optimization task; it tells you when to use passnet-pattern-fusion, passnet-triton-opt and passnet-feedback.
passnet-skill
PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under ./pass_dir/, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.
passnet-pattern-fusion
Author PassNet pass files: write patterns that actually MATCH the FX graph, pick fusion regions (which ops to absorb into one Triton kernel), and structure multi-pass submissions with the mandatory shared-dispatch architecture. Use when creating or fixing pattern()/replacement_args()/replacement_func() files, when a pass "failed to match", or when deciding how to fuse multiple kernels/ops.
passnet-orchestrate
Round/batch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep/revert decisions. For solving one concrete sample end to end, use passnet-solve as the entry skill; consult this skill only when you need broader planning or a specific decision gate.
passnet-feedback
Fast, deterministic feedback for PassNet work: pre-flight pattern/match verification WITHOUT burning a GPU evaluation, per-node bottleneck analysis of a sample's graphs, and eval-log parsing into per-variant status + estimated score + failure classification. Use BEFORE every GPU evaluation (check_pattern), at the START of a sample (analyze_graph), and AFTER every evaluation (parse_eval_log).