agentleFS
Sign inStart free
databricks-solutionsdatabricks-solutions/genie-code-skills-demo/skills/sentiment-analysis/SKILL.md

sentiment-analysis

Skill15 starsChanged 59 days agoLicence not identifiedView on GitHub

Build sentiment-analysis datasets in SDP pipelines using built-in Databricks AI functions (ai_analyze_sentiment, ai_classify, ai_extract, ai_summarize, ai_query). Use when creating or modifying tables that derive sentiment, topics, or entities from free-form text such as customer reviews, support tickets, social posts, or call transcripts. Always compose this skill with @table-governance and @sdp-basics, and add @pii-management when the source text or surrounding columns contain personal data.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use mean-reversion, position-sizing and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • agiprolabsSkill

    mean-reversion

    Mean-reversion strategy tools including Hurst exponent, half-life estimation, z-score signals, ADF testing, and Ornstein-Uhlenbeck modeling

    Also in 3 projects that use this

  • Bhala-SrinivashSkill

    position-sizing

    Calculate optimal position sizes for NSE/BSE equity trades using fixed fractional, ATR-based, and Kelly criterion methods. Includes portfolio constraints and leverage adjustments.

    Also in 3 projects that use this

  • vivy-yiSkill

    risk-management

    内容风险管控 - 预防、识别和应对账号运营中的各类风险

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 0 are common, 4 are distinctive, and 10 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 10

    Very specific

    Tied to their project's names, files or tools. Probably skip.

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free