Verify data freshness by checking table timestamps and update patterns against a staleness scale.
Create detailed user stories, acceptance criteria, and feature specs
Example: Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example: Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example: Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example: Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Submit your Claude Code skill and start earning
epx add astronomer/agents --skill checking-freshnessCompatible with
Supported agents
Identifies timestamp columns using common ETL naming patterns ( _loaded_at , _updated_at , created_at , etc.) and queries their maximum values to determine age
Classifies data into four freshness statuses: Fresh (< 4 hours), Stale (4–24 hours), Very Stale (> 24 hours), or Unknown (no timestamp found)
Provides SQL templates for checking last update time and row count trends over rece
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionchecking-freshnessExecute the skills CLI command in your project's root directory to begin installation:
epx add astronomer/agents --skill checking-freshnessFetches checking-freshness from astronomer/agents and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/checking-freshness
Restart Cursor to activate checking-freshness. Access via /checking-freshnessin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Time estimate: 30-60 minutes to see productivity improvements
Prerequisites
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
deslop
cursor/plugins · Productivity · same category
framer-motion
pproenca/dot-skills · Productivity · same category
yt-dlp
lwmxiaobei/yt-dlp-skill · Productivity · same category
wordpress-elementor
jezweb/claude-skills · Productivity · same category
xauusd-trading
huynguyen03dev/xauusd-trading · Productivity · same category
sports-betting-analyzer
onewave-ai/claude-skills · Productivity · same category
I recommend checking-freshness for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in checking-freshness — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: checking-freshness is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for checking-freshness matched our evaluation — installs cleanly and behaves as described in the markdown.
We added checking-freshness from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
checking-freshness reduced setup friction for our internal harness; good balance of opinion and flexibility.
checking-freshness fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for checking-freshness matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: checking-freshness is the kind of skill you can hand to a new teammate without a long onboarding doc.
checking-freshness has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 64