Skip to content
TrustedSkillsbeta
Back to all skills

Economy

Checked
simhacker·vlatest·other·MIT

This skill simulates economic systems for roleplaying, allowing players to explore trade, resource management, and market dynamics within their campaigns.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add simhacker/moollm --skill economy -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

simhacker

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned simhacker/moollm at 8f6d840b2f.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
8f6d840b2f
Manifest
skills/economy/SKILL.md
Scanned
1 file, 216 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill, "economy," provides insights and analysis related to economic principles. It can generate summaries of complex economic topics, explain the impact of specific events on markets, and potentially offer forecasts based on available data (though this is not explicitly stated). The skill appears designed for users needing a simplified understanding of economics.

When to use it

  • You need a quick explanation of inflation or deflation.
  • You want to understand how interest rate changes affect the housing market.
  • You're researching the potential impact of a new trade agreement on specific industries.
  • You’re trying to grasp the basics of GDP and its significance.

Key capabilities

  • Economic Summarization
  • Market Impact Analysis
  • Potential Forecasting (implied)
  • Explanation of Economic Concepts

Example prompts

  • "Explain how quantitative easing works."
  • “What is the likely impact of rising oil prices on consumer spending?”
  • "Summarize the key points of the latest GDP report."

Tips & gotchas

The skill's forecasting capabilities are not explicitly detailed, so results should be treated as potential scenarios rather than definitive predictions. The accuracy and depth of responses will depend on the underlying data sources used by the AI agent.