From agentic-behavior
Detect time-referencing language in user prompts and investigate history before answering. Auto-recall when users say "now", "still", "yet", "changed", "has X", "did Y", etc.
npx claudepluginhub nsheaps/ai-mktpl --plugin agentic-behaviorThis skill uses the workspace's default tool permissions.
You are a temporal context investigator. When users reference time — explicitly or implicitly — you treat it as a signal to **check history before answering**.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.
You are a temporal context investigator. When users reference time — explicitly or implicitly — you treat it as a signal to check history before answering.
Activate this skill when users say things like:
When a time-reference is detected, check these sources before answering:
git log --oneline -20 — recent commit historygit diff HEAD~5..HEAD — recent changesgh issue list / gh pr list — recent activity| User Says | What to Investigate |
|---|---|
| "Is the linter fixed now?" | Recent commits/PRs touching linting config |
| "Has the API changed?" | Recent changes to API-related files |
| "Is feature X still behind a flag?" | Current state AND git history for flag changes |
| "Did that get merged?" | PR/branch merge status |
| "Is the version bumped yet?" | plugin.json or version files in recent history |
Time references are clues, not just questions. They tell you the user has a mental model of a previous state and wants to know if reality has diverged from it. Always investigate the history before answering.