Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Reward Shaped Nonlinguistic Rule Codes

ASecurity

Reward vs gradient channels shape emergent rule codes differently.

3 stars
0 votes
0 copies
0 views
Added 10/3/2026
ai-agentspythongo

Security Analysis

A100/100

Scanned 10/3/2026

$npx -y skills add hiyenwong/ai_collection --skill reward-shaped-nonlinguistic-rule-codes --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Reward Shaped Nonlinguistic Rule Codes?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Reward Shaped Nonlinguistic Rule Codes
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hiyenwong-reward-shaped-nonlinguistic-rule-codes/badge)](https://www.skillsdirectory.com/skills/hiyenwong-reward-shaped-nonlinguistic-rule-codes)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: reward-shaped-nonlinguistic-rule-codes
description: Reward vs gradient channels shape emergent rule codes differently.
category: ai_collection
trigger_words: emergent communication, signalling game, rule transmission, compositionality, aphasia, invented symbols, reward vs gradient, degenerate pooling equilibrium, non-linguistic code
---

# Learning Non-Linguistic Codes for Inferred Rules From Reward

Methodology from "Learning a non-linguistic code for inferred rules from reward" (arXiv:2609.31192, q-bio.NC, Sep 2026, Cristiano Capone).

## When to Use
- Modeling how rules/inference (not references) transmit between agents without a pre-shared language — computational model of aphasia patients conveying inferred rules by gesture/sketch (Kean et al.)
- Emergent-communication research beyond referential games: rule-execution games where a message must let a blind receiver *execute* a transformation on new input
- Designing multi-agent systems where a teacher must communicate skills/rules to a student through a narrow discrete channel
- Analyzing degenerate solutions (message collapse) in reward-trained communication

## Game Setup (Speaker–Executor)
- **Speaker** network: sees a few worked examples of a transformation; emits 8 symbols from a 32-symbol alphabet (nothing assigned in advance — no grammar, no supervision of meanings)
- **Executor** network: sees ONLY the symbols + a fresh input grid; must produce the correct output
- Three channels compared:
  1. **Reward**: speaker learns only from executor's success/failure
  2. **Gradient**: executor's error backpropagates through the symbols
  3. **Continuous**: real-valued vector replaces symbols (upper bound reference)
- Experience curricula: Staged (singles→pairs→triples), Joint (all at once), Reversed

## Five Core Findings
1. **A code emerges and composes**: it carries rules to held-out 3-step transformations training never computes, and new learners can acquire it. Critical methodology — held-out split audit: training episodes are rotated/reflected/recoloured, so most held-out *pairs* are transformations training already presents in disguise; only held-out *triples* (100 of 300) genuinely test composition.
2. **Discreteness costs little** — provided perception is learned outside the channel (encoder pretrained, frozen during code learning).
3. **Reward and gradient build different codes**: reward sorts many rules under a few fixed labels (pooling); gradient gives each rule its own region of similar messages (graded map). Gradient separates rules far better.
4. **Degenerate solution is measurable**: under reward alone, the speaker drifts to ONE message whatever the rule (analogous to human languages losing words in plain transmission). Staged experience or an information pressure against uninformative messages prevents collapse. Competence tracks **how much the message says about the rule** (mutual information), NOT message variety.
5. **Reward-driven naming saturates** as rules are added; neither tested capacity increase lifted the ceiling.

## Implementation Pattern
```python
# 1. Speaker: encoder(examples) -> discrete bottleneck (8 symbols, alphabet 32, straight-through Gumbel)
# 2. Executor: decoder(symbols, new_input) -> output grid
# 3. Channels:
#    reward-only: REINFORCE/PPO on executor success (exact match)
#    gradient: straight-through estimator lets executor loss flow to speaker
# 4. Metrics:
#    - exact-match accuracy on held-out TRIPLES (composition test)
#    - P(rule | message) — how often a rule is decoded from the message
#    - degeneracy check: entropy of speaker outputs across rules
#    - information pressure: penalize low MI(message; rule) or uniform messages
# 5. Held-out audit: verify test transformations are NOT reachable by composing
#    training programs under rotation/reflection/recolor equivalences.
```

## Design Lessons for Multi-Agent Rule Teaching
- Reward-only channels → pooling equilibria. If you need rule-specific messages, add gradient flow (differentiable channel) or explicit information pressure.
- Curriculum matters: staged (simple→composite) prevents degenerate collapse better than joint training; reversed curriculum is worse.
- Measure the *information content* of messages (MI with the rule), not their diversity — variety without relevance is worthless.
- When auditing generalization in compositional tasks, enumerate algebraic symmetries (rotation/reflection/recolor) of training data; test only on transformations unreachable from the training orbit.
- Discrete bottleneck is fine — put representational capacity in pretrained perception outside the channel, not in the code itself.

Attribution

hiyenwonghiyenwong
View sourceSee grades on GitHubMore from hiyenwong →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →