synthesize-learnings — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited synthesize-learnings (Agent Skill) and scored it 87/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 3 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 3 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
This skill requires Python 3.8+ and standard library only. No external packages needed.
To install this skill's dependencies:
pip-compile ./requirements.in
pip install -r ./requirements.txtSee ./requirements.txt for the dependency lockfile (currently empty — standard library only).
Take raw analysis output from analyze-plugin and transform it into concrete, actionable improvements for our meta-skills ecosystem. This is the "close the loop" skill that turns observations into evolution.
Learnings are mapped to three improvement targets:
agent-scaffoldersImprovements to the plugin/skill/hook/sub-agent scaffolding tools.
What to look for:
scaffold.py should supportagent-scaffoldersImprovements to ecosystem standards and authoritative source documentation.
What to look for:
agent-scaffolders (Self-Improvement)Improvements to this analyzer plugin itself.
What to look for:
pattern-catalog.mdoracle-legacy-system-analysis)Improvements to the primary domain plugins in this repository — especially the legacy Oracle Forms/DB analysis plugins.
What to look for:
~~category patterns) for tool-agnostic Oracle analysis workflowsCollect all analysis reports from the current session or from referenced analysis artifacts.
Sort every observation into one of these categories:
| Category | Description | Maps To |
|---|---|---|
| Structural Innovation | Novel directory layouts, component organization | Scaffolders |
| Content Pattern | Reusable content structures (tables, frameworks, checklists) | Specs + Catalog + Domain |
| Execution Pattern | Workflow designs, phase structures, decision trees | Scaffolders + Specs + Domain |
| Integration Pattern | MCP tool usage, connector abstractions, cross-tool design | Specs + Domain |
| Quality Pattern | Testing, validation, compliance approaches | Scaffolders + Specs |
| Meta Pattern | Self-referential or recursive designs (skills that build skills) | Analyzer + Scaffolders |
| Anti-Pattern | Things to avoid, documented pitfalls | Specs |
| Domain Applicability | Patterns transferable to legacy code analysis workflows | Domain |
| Novel Discovery | Something entirely new not in existing catalogs | All targets |
For EACH observation, produce a structured recommendation:
### [Recommendation Title]
**Source**: [Plugin/skill where observed]
**Category**: [from table above]
**Target**: [which meta-skill to improve]
**Priority**: [high / medium / low]
**Observation**: [What was found]
**Current State**: [How our meta-skills handle this today, or "not addressed"]
**Proposed Improvement**: [Specific change to make]
**Example**: [Before/after or concrete illustration]Rank recommendations by impact:
| Priority | Criteria |
|---|---|
| High | Universal pattern found across many plugins; would improve ALL generated plugins; addresses a gap in current standards |
| Medium | Common pattern found in several plugins; would improve most generated plugins; refines existing standards |
| Low | Niche pattern from specific domain; would improve specialized plugins; nice-to-have enhancement |
Append any newly discovered patterns to references/pattern-catalog.md in the analyze-plugin skill. This is the self-improvement loop — every analysis makes future analyses better.
Append each recommendation to references/open-recommendations.md using this format:
| [YYYY-MM-DD] | [Title] | [Target] | [Priority] | open |See references/open-recommendations.md for the tracker schema. When a recommendation is implemented, update its status from open to implemented and add the PR or commit reference.
Format new catalog entries as:
### [Pattern Name]
- **Category**: [Structural / Content / Execution / Integration / Quality / Meta]
- **First Seen In**: [plugin name]
- **Description**: [2-3 sentences]
- **When to Use**: [trigger conditions]
- **Example**: [brief illustration]Produce a final synthesis report with:
The synthesis report should be a standalone markdown document suitable for:
Iteration Directory Isolation: Do NOT overwrite existing synthesis reports. Always output to a newly isolated directory (e.g. synthesis-reports/run-1/) so historical recommendations are preserved. Asynchronous Benchmark Metric Capture: Log the total_tokens and duration_ms consumed during the synthesis back to timing.json to track the ROI cost of this meta-analysis.
Always close with a Next Steps section listing the 3 most impactful changes to make first.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.