esg-longitudinal
Skill1 starsChanged 23 days agoNo licenceView on GitHub
Build and re-run an agent that tracks companies' ESG / CSR / sustainability commitments over time using free public data. Given a company (or a list), a domain (climate, circular economy, biodiversity, social/governance), and a time range, it finds free sustainability and annual reports, extracts the targets and metrics into a tidy time-series, saves a timestamped snapshot, and diffs against earlier snapshots to surface what changed. Use this skill whenever the user wants to analyze ESG/CSR/sustainability data over time, track a company's climate or circular-economy or biodiversity or social targets, compare disclosures across years, build a longitudinal ESG dataset, extract metrics from sustainability report PDFs, monitor changes in corporate sustainability commitments, or set up an analysis they can re-run next year to see what moved. Also use it when the user mentions ESG databases, CSR reports, sustainability reports, Scope 1/2/3 or net-zero or circular-revenue targets, or scaling ESG analysis across many companies (hundreds to tens of thousands).
- Installs packages
In this repository14 other files it gives its agents.
- advisor-bridgeSkill
- climatepoint-contact-intelligenceSkill
- epd-expiry-leadsSkill
- find-cold-leadsSkill
- fix-pr-reviewsSkill
- lca-saveSkill
- linkedin-outreach-odooSkill
- ollama-workersSkill
- orchestrateSkill
- outlook-draftSkill
- reviewing-plansSkill
- ship-fleetSkill
- ship-repairSkill
- shipSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
3
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.