skill update

Engineering Community

Skill notes

Hard caps (enforced by scripts/skilllinter.py)

SKILL.md ≤ 150 lines reference/*.md ≤ 200 lines (reference/scenarios/*.md ≤ 400 lines) README.md ≤ 100 lines Every SKILL.md has YAML frontmatter with name + description No DO NOT / MUST NOT / NEVER outside an ## Anti-Patterns section

Principles

Brevity first. Every file short, simple, human-readable. Challenge every token. Progressive disclosure. SKILL.md navigates; reference/ holds detail; reference/scenarios/ holds concrete exploit flows. Separation of concern. SKILL.md = WHAT + when. reference/role-*.md = HOW agents behave when spawned. Single canonical home for any cross-cutting rule (output discipline, credential loading, brute-force, etc.). Other files reference, never restate.

When to update an existing skill

Process the techniques and failure modes from completed engagements. Promote a learning to the skill base only if all four hold: Generalizable. Reusable pattern, not target-specific lore. No machine names, lab IDs, target IPs, preserved flags, writeup attributions. Material improvement. Adds coverage, efficiency, or decision-quality for future engagements. Not already captured elsewhere in the skill base. (scripts/skill_linter.py flags duplicates.)

Reframing recipe

Always frame as a reusable pattern: "when encountering X condition, try Y approach" — never "on box-N, Y worked". Use <TARGET_IP>, <DC_FQDN>, <DOMAIN> placeholders in tool examples.

Pre-write check

Before writing, run python3 scripts/skill_linter.py. Reject any change that: Re-introduces challenge-specific lore. Pushes a SKILL.md past 150 or a reference past its cap. Duplicates a single-owner rule (brute-force, output discipline, env-reader). Adds DO NOT / MUST NOT / NEVER outside an Anti-Patterns block.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@transilienceai · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview skill-update.preview
# Workflow / Quick start

<≤30 lines>

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.