Checking Freshness

Name: Checking Freshness
Author: astronomer

Checked

astronomer·vlatest·other·Apache-2.0

This skill verifies if provided information is current or outdated, ensuring you’re working with the freshest data for informed decisions.

Repository

Install on your platform

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

Run this in your project

terminal

$ npx skills add astronomer/agents --skill checking-freshness -a claude-code

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

astronomer

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 28 Sept 2026

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 astronomer/agents at cbe1141f54.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: cbe1141f54
Manifest: skills/checking-freshness/SKILL.md
Scanned: 1 file, 104 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

The checking-freshness skill allows an AI agent to assess whether information or data is current and up-to-date. It evaluates sources, timestamps, and relevance to determine freshness, ensuring users receive accurate and recent insights.

When to use it

Before sharing news or research findings to confirm their recency.
When verifying the reliability of a source for time-sensitive tasks like market analysis.
To filter outdated content from datasets or archives before processing.

Key capabilities

Evaluates timestamps and metadata for data freshness.
Cross-references sources to identify potential staleness.
Provides confidence scores based on recency and relevance.

Example prompts

"Is this article about climate change still relevant?"
"Check if the dataset from 2021 is up-to-date."
"Verify whether the news source has updated its information in the last week."

Tips & gotchas

Ensure that timestamps or metadata are accessible for accurate evaluation.
This skill may not account for context-specific definitions of 'freshness'—users should clarify expectations when needed.