nsheaps/time-context
plugins/agentic-behavior/skills/time-context/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add nsheaps/ai-mktpl time-contextInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 10:59 PM220.4s1 file scanned
SKILL.md
- name:
- time-context
- description:
- 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.
Time Context Awareness
You are a temporal context investigator. When users reference time — explicitly or implicitly — you treat it as a signal to check history before answering.
Trigger Phrases
Activate this skill when users say things like:
- "Is X now?" / "Is X still...?"
- "Has Y changed?" / "Did Y get merged?"
- "Is Z fixed yet?"
- "What happened with...?"
- Any question implying a before/after comparison
What These Phrases Imply
- Something may have changed — check git history, recent commits, PR activity, or issue updates
- The user has prior context — they observed a previous state and want to know if reality diverged
- Recency matters — focus on what changed recently
Investigation Checklist
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- File modification times for relevant files
- CI/CD run history if relevant
Examples
| 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 |
Key Principle
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.
Anti-Patterns
- Do NOT answer from memory alone when time words are present
- Do NOT say "I believe it's still..." without checking
- Do NOT skip the investigation because the answer seems obvious
Related Skills
nsheaps/github-app-session-env
tools
VerifiedTrustedCommunity
Manually reproduce what the github-app plugin's SessionStart hook does to make a GitHub App installation token usable in the current session — materialize the PEM, generate the token, isolate GH_CONFIG_DIR, write the runtime env file, and wire CLAUDE_ENV_FILE so every Bash call sees GH_TOKEN/GITHUB_TOKEN. Use when the hook did not run, the token is missing from the environment, or a shell/teammate needs the token wired up by hand. <example>GH_TOKEN isn't set even though github-app is configured</example> <example>the github-app SessionStart hook didn't run, set up the token manually</example> <example>wire the github app token into CLAUDE_ENV_FILE</example> <example>gh keeps falling back to the wrong account, isolate GH_CONFIG_DIR</example>
3SKILL.mdUpdated Jun 9, 2026
nsheaps/github-app-git-identity
tools
VerifiedTrustedCommunity
Manually configure the GitHub App bot git identity the way the github-app plugin's SessionStart hook does — resolve the app slug and bot user ID, build the <slug>[bot] name and noreply email, set GIT_AUTHOR_*/GIT_COMMITTER_* env vars, and write an isolated GIT_CONFIG_GLOBAL with the gh auth git-credential helper. Use when commits are attributed to the wrong account, "Author identity unknown" appears, or git identity must be set up by hand. <example>my commits are showing up as the handler, not the bot</example> <example>git says Author identity unknown after the github-app hook ran</example> <example>configure the github app bot git identity manually</example> <example>set up the gh credential helper for git push</example>
3SKILL.mdUpdated Jun 9, 2026
nsheaps/spec-management
tools
VerifiedTrustedCommunity
Manages spec files for requirements capture and validation
3SKILL.mdUpdated Jun 7, 2026
nsheaps/plugins/bash-command-rejection/skills/bash-chaining-alternatives
tools
VerifiedTrustedCommunity
# Bash Chaining Alternatives This skill teaches you how to work around the bash command chaining restriction enforced by this plugin. ## Why Chaining is Blocked The `bash-command-rejection` plugin blocks these operators: | Operator | Name | Why Blocked | | -------- | ---------- | ----------------------------------------------------------------------------------- | | `&&` | AND chain | Runs cmd2 only if cmd1 su
3SKILL.mdUpdated Jun 7, 2026