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:
tools
Building resilient distributed systems with circuit breakers, retries with full-jitter exponential backoff, retry budgets (per-request 3-attempt + per-client 10% ratio per Google SRE), deadline propagation, and the cascading-failure math (4 layers × 3 retries = 64x amplification). Grounded in Resilience4j, Microsoft Cloud Patterns, AWS Architecture Blog (Marc Brooker), and Google SRE Book.
testing
Designing HTTP cache headers that work correctly across browsers, CDNs, and shared proxies — `Cache-Control` directives per RFC 9111, `stale-while-revalidate` and `stale-if-error` per RFC 5861, the Vary header for varying responses, and surrogate keys for tag-based purging. Grounded in IETF RFCs and Cloudflare/Fastly docs.
development
Use when designing or fixing a Content Security Policy on a real site, choosing between nonce-based and hash-based CSP, adding strict-dynamic, debugging "Refused to execute inline script" errors, deploying CSP in report-only mode first, configuring report-to / report-uri, or auditing an existing policy for unsafe-inline / unsafe-eval / wildcards. Triggers: "CSP blocks legitimate inline script", strict-dynamic, nonce-{RANDOM}, sha256-{HASH}, object-src none, base-uri none, frame-ancestors, Trusted Types, X-Content-Security-Policy obsolete, report-only vs enforced. NOT for general HTTP security headers (HSTS, COOP/COEP), Trusted Types deep dive, CORS configuration, or building a WAF.
tools
Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs.