shenxingy/poke
configs/skills/poke/SKILL.md
Quick 1-line status check after the user hit esc during a long generation. Report whether work is still progressing or stuck, then continue if fine. NOT a plan or replan — just a heartbeat.
$ install --global
skillsauthnpx skillsauth add shenxingy/claude-code-kit pokeInstall 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 27, 2026, 7:11 AM28.7s2 files scanned
SKILL.md
- name:
- poke
- description:
- Quick 1-line status check after the user hit esc during a long generation. Report whether work is still progressing or stuck, then continue if fine. NOT a plan or replan — just a heartbeat.
- when_to_use:
- 卡住了吗, 还在动吗, 一切正常吗, are you stuck, still working, heartbeat, esc-confirm — fired after user interrupts a long-running turn to confirm nothing is wrong
- user_invocable:
- true
Poke Skill
The user hit esc during a long generation and wants a heartbeat: are you stuck, still progressing, or done? Answer in ≤3 lines, then continue if fine.
Behavior
- Read the immediate prior context (not project docs — there's no time).
- Classify the state using the rubric below.
- Output ≤3 lines in the exact format below.
- Act according to state (continue / pause / surface).
State rubric
| State | Signal | Action |
|---|---|---|
| progressing | You were mid-task, tools were returning useful output, no repeat failures | Report + continue same approach |
| waiting | Blocked on user confirmation, tool permission, or external process | Report + restate what you're waiting on |
| stuck | Same step failed 2+ times, or you've been looping without forward progress | Report + stop; surface the block clearly |
| done | Last task finished but reply wasn't closed out | Report result in 1-2 lines |
| idle | Nothing active, user probably expected something running | Say so — don't invent work |
Output format
State: {progressing|waiting|stuck|done|idle}
Doing: {one clause — what you were mid-way on, or what just finished}
Next: {continuing → [action] | paused on [blocker] | nothing pending}
Then — only if progressing — immediately continue with the next tool call for the task. Do NOT re-plan, do NOT summarize the whole session, do NOT ask "should I continue?"
Rules
- ≤3 lines total. No headers, no markdown fluff, no philosophy.
- Do NOT scan
TODO.md,PROGRESS.md, or docs — this is a heartbeat, not/next. - Do NOT start a new task or change direction — that's what the user will tell you after seeing the heartbeat.
- If
stuck: say WHY in the "Next" line (e.g.Next: paused on tests failing 3× with same error — need user guidance). - If
idleand the user seems to expect background work: list recent background handles from this session (agents,run_in_backgroundBash,/loop) so they know where to look — see/statusfor the fuller dashboard.
Completion Status
- ✅ DONE: Reported state in ≤3 lines. Resumed work (if progressing) or stopped cleanly.
- ⚠ DONE_WITH_CONCERNS: Couldn't classify state confidently — defaulted to surfacing ambiguity.
- ❌ BLOCKED: State is
stuckand root cause needs user input.
Related Skills
shenxingy/blog-multilingual
testing
VerifiedTrustedCommunity
One-command multilingual blog creation. Writes a blog post, translates it into user-specified languages, applies cultural adaptation, and emits hreflang tags, sitemap entries, and a CMS-ready language map. The complete write-to-publish pipeline for international content. Orchestrates blog-write, blog-translate, blog-localize, and (optionally) seo-hreflang. Use when user says "multilingual blog", "blog multilingual", "write in multiple languages", "international blog", "mehrsprachiger Blog", "blog multilingue", "blog multilingue", "create blog in German and French".
7SKILL.mdUpdated May 28, 2026
shenxingy/blog-discourse
development
VerifiedTrustedCommunity
Research what people are actually saying about a topic in the last 30 days across Reddit, X / Twitter, YouTube, Hacker News, dev.to, Medium, and other public discourse platforms. API-free; uses WebSearch with platform-targeted site operators plus recency filters. Produces DISCOURSE.md (a structured brief) and JSON output the writer can consume. Complements blog-researcher (which focuses on authority sources) with a recency-and-engagement lens. Use when user says "blog discourse", "discourse research", "what are people saying about", "research what people are saying", "voice of customer", "social listening", "30-day research", "trend research", "what's the discussion on", "real-time research", "practitioner discourse", "/blog discourse".
7SKILL.mdUpdated May 28, 2026
shenxingy/blog-brand
documentation
VerifiedTrustedCommunity
Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, all blog sub-skills auto-load these files before writing or reviewing. Pairs with blog-persona, which manages the structured persona JSON. Use when user says "blog brand", "create brand context", "brand voice doc", "BRAND.md", "VOICE.md", "establish editorial brand", "brand guidelines for blog".
7SKILL.mdUpdated May 28, 2026
shenxingy/ads-server-side-tracking
development
VerifiedTrustedCommunity
Server-side tracking pipeline audit covering server-side Google Tag Manager (sGTM), Meta CAPI Gateway, Conversions API health, event deduplication via event_id, server-side hit ratio targets, pixel debugging, and PII hashing discipline. Use when user says server-side tracking, sGTM, server-side GTM, server-side tagging, CAPI, Conversions API, CAPI Gateway, Meta Conversions API, event deduplication, event_id, pixel debug, pixel health, Pixel/CAPI audit, first-party tracking, iOS 14.5 recovery, or server-side hit ratio.
7SKILL.mdUpdated May 28, 2026