Skip to content
TrustedSkillsbeta
Back to all skills

Checking Changes

Official
streamlit·vlatest·data·Apache-2.0

This skill checks for modifications to a document or data source, ensuring you’re always working with the latest version and preventing errors.

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 streamlit/streamlit --skill checking-changes -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

streamlit

Matched to the vendor's own GitHub organisation.

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 streamlit/streamlit at 3741d77bbf.

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

Commit
3741d77bbf
Manifest
.claude/skills/checking-changes/SKILL.md
Scanned
1 file, 27 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 enables AI agents to detect and analyze modifications within Streamlit applications, ensuring code consistency after updates. It specifically monitors changes to the application state and UI components to maintain stability.

When to use it

  • Verifying that recent code commits did not break existing dashboard layouts or data widgets.
  • Auditing configuration files before deploying a new version of a Streamlit app to production.
  • Identifying unintended side effects when refactoring shared utility functions used by the app.
  • Comparing current application behavior against a known-good baseline after environment changes.

Key capabilities

  • Detects structural changes in Streamlit session state variables.
  • Monitors updates to custom components and layout configurations.
  • Validates consistency between source code modifications and running instances.
  • Provides feedback on potential conflicts introduced by new dependencies or library versions.

Example prompts

  • "Check if the latest commit altered the data loading logic in my Streamlit dashboard."
  • "Analyze changes made to the session state management since yesterday's deployment."
  • "Identify any modifications to the sidebar navigation components in the current codebase."

Tips & gotchas

Ensure your development environment has access to version control history for accurate change detection. This skill is most effective when paired with automated testing suites that validate UI interactions after changes are detected.