snowpark-api
Skill49 starsChanged 8 months agoNo licenceView on GitHub
Snowpark Python API conversion path via the SMA CLI. Bundled sub-skill of `spark-migration`, invoked by the parent ONLY when the user explicitly asks for an SMA / Snowpark API rewrite (`snowflake.snowpark`, snake_case `with_column` / `group_by` / `session.create_dataframe`). Owns: SMA CLI detection, conversion, EWI dashboard, notebook migration, EWI fixer, stage conversion, DVP orchestration, and the API-side final summary. Use when: user explicitly asked for SMA / SMA CLI / Snowpark API / `snowflake.snowpark` rewrite, OR user wants to operate on an already-converted SMA output (open dashboard, fix EWIs, run stage conversion, resume DVP). Triggers: snowpark api, sma cli, sma conversion, run sma, snowflake.snowpark rewrite, snake_case snowpark, fix ewis, ewi fixer, sma dashboard, stage conversion, resume dvp, dvp orchestrator, already migrated sma.
In this repository38 other files it gives its agents.
- analyst-literal-searchSkill
- check-agent-accessSkill
- check-model-availabilitySkill
- dbt-model-generatorSkill
- dcr-v1-to-v2Skill
- devops-guidanceSkill
- dynamic-tables-guidanceSkill
- manage-external-lineageSkill
- manage-zerocopy-sapbdcSkill
- migrate-snowsqlSkill
- ml-migrationSkill
- ontology-stack-builder-migrate-to-business-ontologySkill
- ontology-stack-builderSkill
- setup-openflow-privatelinkSkill
- persist-memorySkill
- quickstart-guideSkill
- rbacSkill
- review-skill-sflabsSkill
- semantic-view-patternsSkill
- sfguide-diagramSkill
- snowflake-docsSkill
- snowpipe-bcdrSkill
- snowpro-studySkill
- solutions-installerSkill
- deploy-code-bundleSkill
- deploy-notebookSkill
- spark-migrationSkill
- snowflake-notebook-migrationSkill
- snowpark-connectSkill
- bugfixSkill
- evolveSkill
- featureSkill
- implementSkill
- refactorSkill
- spec-drivenSkill
- streamlit-add-chat-pageSkill
- swap-databasesSkill
- well-architected-framework-assessmentSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.