Individual skill
add-pattern
Use this skill when you learn one or more design pattern(s) in the Langroid (multi) agent framework, and want to make a note for future reference for yourself. Use this either autonomously, or when asked by the user to record a new pattern.
plugins/langroid/skills/add-pattern/SKILL.md
Source commit 9a5216b4b94bffa3e590d9c815c147d1be5ee12e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,031
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- cli Repository topic
- cli-agent Repository topic
- llm Repository topic
- tmux Repository topic
- code-agent Repository topic
- codex Repository topic
- codex-cli Repository topic
- context Repository topic
- design Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,031 bytes
Read excerpt
# add-pattern
## Instructions
When you learn a new Langroid design pattern, do the following:
1. Add an entry in the sibling `patterns/SKILL.md` file in the appropriate category
section, containing a DESCRIPTION of the goal of the pattern (i.e. what it enables
you to implement), accompanied by a `- Reference:` pointer to a markdown DOCUMENT
in the `patterns/` directory.
IMPORTANT - The DESCRIPTION should be clear enough that future YOU can effectively
use it to MATCH design problems you may encounter in future.