skills/hierarchical-skill-repr/SKILL.md
Representations for hierarchical skill structures including knowledge graphs and ontological decomposition
npx skillsauth add curiositech/windags-skills hierarchical-skill-reprInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Load this skill when facing problems involving autonomous skill acquisition, sensorimotor grounding, hierarchical control composition, or bridging symbolic reasoning with continuous control. Particularly effective when agents must learn domain-general capabilities without task supervision.
IF object_uncertainty > convergence_threshold:
IF low-cost_visual_exploration available:
→ Execute visual inspection from multiple angles
→ Update Bayesian belief over object affordances
ELSE IF tactile_exploration safe:
→ Execute gentle contact with surface normals
→ Track force convergence patterns
ELSE:
→ Default to most probable schema based on priors
IF object_uncertainty ≤ convergence_threshold:
IF goal_affordance_confidence > action_threshold:
→ Execute goal schema (grasp, manipulate)
ELSE:
→ Select schema maximizing I(action; goal_affordance)
IF schema_convergence_rate < stability_threshold:
→ Check prerequisite schemas are stable
→ Reduce DOF constraints further
→ Increase practice iterations before advancement
IF schema_convergence_rate ≥ stability_threshold:
IF subordinate_schemas available AND superior_schema stable:
→ Attempt nullspace composition: subordinate ⊳ superior
ELSE IF next_complexity_level unlocked:
→ Add sensorimotor resource (additional DOF, sensor modality)
→ Initialize new schema learning
IF multiple_control_objectives active:
Rank by criticality:
IF safety_constraint violated:
→ All controllers ⊳ collision_avoidance
ELSE IF visual_track required for task:
→ force_control ⊳ visual_track
→ orientation_adjust ⊳ (force_control ⊳ visual_track)
ELSE:
→ Apply standard priority hierarchy from training
Calculate: a_combined = a_superior + (I - J_superior†J_superior) * a_subordinate
Detection Rule: If subordinate controller performance degrades when superior controller activates, or if combined error increases monotonically
Detection Rule: If schema reports "converged" but goal affordance uncertainty remains high (H(g) > threshold)
Detection Rule: If complex schema learning fails repeatedly and prerequisite schemas show instability
Detection Rule: If object recognition confidence decreases over time despite consistent sensory input
Detection Rule: If mutual information I(a; g) never decreases below action threshold despite multiple exploratory actions
Initial State: Robot with 7-DOF arm, RGB camera, force sensors. No prior cup knowledge.
Phase 1 - Visual Tracking (L1)
Phase 2 - Reach Coordination (L2)
Phase 3 - Force Integration (L3)
Final affordance model: Cup = {rim_visual_tracking: [x,y,θ] distribution, surface_force_tracking: normal directions, grasp_points: force + visual intersection}
Scenario: Ambiguous cylindrical object (cup vs. can vs. bottle) partially occluded.
Decision trace:
Do NOT use for:
Delegate when:
Resource requirements:
data-ai
license: Apache-2.0 NOT for unrelated tasks outside this domain.
development
Use when designing caching strategies (cache-aside, write-through, write-behind), implementing distributed locks, building rate limiters, leaderboards, real-time streams (XADD/consumer groups), pub/sub, or tuning eviction policies. Triggers: thundering-herd on cache miss, dogpile on key expiry, Redlock vs SET-NX-PX choice, sliding-window rate limiter, hot-key on a single cluster slot, big-key blowup, MULTI/EXEC across slots, KEYS in production. NOT for Redis Cluster operations/admin (different domain), embedded KV (SQLite, leveldb), in-process LRU caches, or Memcached.
tools
Drawing the `'use client'` boundary correctly in React Server Components apps (Next.js App Router, RSC frameworks) — leaf-pushing, slot composition, serialization rules, and environment poisoning prevention. Grounded in react.dev and Next.js 16 docs.
development
Use when designing rate limiting for an API, choosing between token bucket / sliding window / leaky bucket / fixed window, implementing it in Redis, deciding edge (Cloudflare/Upstash) vs origin enforcement, sizing per-user vs per-IP vs per-endpoint quotas, returning the right 429 response with Retry-After, or fixing the boundary-burst bug in fixed-window limiters. Triggers: 429 too many requests, INCR + EXPIRE, ZADD + ZREMRANGEBYSCORE + ZCARD, X-RateLimit-Remaining header, Cloudflare WAF rate limiting rules, Upstash @upstash/ratelimit, leaky bucket shaping vs policing, distributed rate limiter consistency. NOT for DDoS mitigation specifically (different scale), CAPTCHA / bot management, full WAF design, or per-user quota billing.