fv-thc/wot
Provides reference documentation and architectural guidance for WoT implementation via vGPIO paths.
Install
mkdir -p .claude/skills/fv-thc-wot && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11402" && unzip -o skill.zip -d .claude/skills/fv-thc-wot && rm skill.zipInstalls to .claude/skills/fv-thc-wot
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
THC Wake-on-Touch (WoT) — corrected architecture (GPIO IP / vGPIO wake path), WoG (Not POR / ISH-based), Linux/Windows implementation, platform config, validation, debugKey capabilities
- →Clarify Wake-on-Touch (WoT) architecture
- →Distinguish GPIO IP from THC IP in wake path
- →Guide Linux/Windows driver implementation for WoT
- →Provide platform configuration details for WoT
- →Detail validation and debug procedures for WoT
How it works
The skill provides complete documentation clarifying that WoT wake comes from GPIO IP, not THC IP, and details the driver-side role of THC, hardware configuration, and validation steps.
Inputs & outputs
When to use fv-thc/wot
- →Debug wake functionality
- →Implement touch wake on linux
- →Validate platform wake architecture
About fv-thc/wot
Clarifies the wake architecture by distinguishing between GPIO IP and THC IP roles. It guides users through driver implementation and validation steps.
THC Wake-on-Touch (WoT) — corrected architecture (GPIO IP / vGPIO wake path), WoG (Not POR / ISH-based), Linux/Windows implementation, platform config, validation, debug
When not to use it
- →When THC IP is expected to generate platform wake signals
- →When Wake-on-Gesture (WoG) is expected to be a fully validated feature
- →When the touch device is not on a separate power rail that remains active
Limitations
- →THC cannot generate platform wake signals
- →WoG (Wake on Gesture) is not POR (Product of Record)
- →D3 state only supports SW wake, not touch device wake
How it compares
This skill corrects a common misconception about WoT architecture by explicitly stating the wake path bypasses THC IP, providing accurate guidance for implementation and debugging compared to prior incorrect assumptions.
Compared to similar skills
fv-thc/wot side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| fv-thc/wot (this skill) | 0 | 3mo | Review | Advanced |
| chrome-devtools | 41 | 7mo | Review | Intermediate |
| python-performance-optimization | 27 | 2mo | No flags | Intermediate |
| analyzing-logs | 14 | 27d | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
chrome-devtools
mrgoonie
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automation, and JavaScript debugging.
python-performance-optimization
wshobson
Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance.
analyzing-logs
jeremylongshore
Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.
redis-inspect
civitai
Inspect Redis cache keys, values, and TTLs for debugging. Supports both main cache and system cache. Use for debugging cache issues, checking cached values, and monitoring cache state. Read-only by default.
obsidian-performance-tuning
jeremylongshore
Optimize Obsidian plugin performance for smooth operation. Use when experiencing lag, memory issues, or slow startup, or when optimizing plugin code for large vaults. Trigger with phrases like "obsidian performance", "obsidian slow", "optimize obsidian plugin", "obsidian memory usage".
obsidian-observability
jeremylongshore
Set up comprehensive logging and monitoring for Obsidian plugins. Use when implementing debug logging, tracking plugin performance, or setting up error reporting for your Obsidian plugin. Trigger with phrases like "obsidian logging", "obsidian monitoring", "obsidian debug", "track obsidian plugin".