An AI skill is a structured system prompt or set of custom instructions that gives AI assistants like ChatGPT, Claude, and Gemini specialized capabilities. It includes a clear role definition, specific knowledge areas, step-by-step processes, and quality criteria that help AI perform specific professional tasks.

How does Skill This work?

Simply describe your professional expertise in plain text. Our free AI skill generator analyzes your input and transforms it into a structured system prompt. The skill is then graded on clarity, specificity, and usefulness. You can share your skill via a unique URL or copy it to use as custom instructions with any AI assistant like ChatGPT, Claude, or Gemini.

Is Skill This free to use?

Yes, Skill This is completely free. No account or payment is required. You can create unlimited skills and share them with anyone.

How is my skill graded?

Skills are graded on a scale from A+ to F (0-100 points). The grade reflects how clear, specific, and actionable your skill is. Higher grades indicate skills that AI assistants can use more effectively.

How do I use my skill with an AI assistant?

Copy your generated skill and paste it into the system prompt or custom instructions of any AI assistant. For ChatGPT, use Personalization > Custom Instructions. For Claude, add it to a Project's instructions. For Cursor or other IDEs, save it as a .cursorrules or CLAUDE.md file. The AI will then adopt that skill and perform tasks according to your expertise.

AI Skill Report Card

Applying Re Bricolage Framework

B+78·Oct 31, 2026·Source: Web

Markdown
---
name: applying-re-bricolage-framework
description: Deconstructs proven solutions into reusable abstract building blocks and recombines them with foreign-domain principles to solve unrelated wicked problems, enforcing single-use scarcity so components cannot be lazily reapplied. Use when generating breakthrough innovation from existing IP, running cross-domain ideation workshops, escaping solution lock-in, or building a disciplined building-block vault for enterprise R&D portfolios.
---

# Re-Bricolage Framework for Solution Engineering

Quick Start13 / 15

Given a proven solution, run this four-stage loop:

Disintegrate: Strip the solution's name/domain away. List each pillar as Abstract Concept + Operational Mechanism.
Collide: Cross each mechanism against 3-5 totally unrelated fields (Mycology, Quantum Electrodynamics, Art Provenance, Marine Ecology, Structural Geology...). For each pairing ask: "What unsolved problem in Field B could Mechanism A dissolve?"
Re-Bricolage: Build new pillars as 50/50 hybrids (original mechanism + foreign principle). Name the new solution.
Govern: Mark every building block used as EXHAUSTED. If a block is shared across proposals, trigger a Proxy Search for an equal-or-greater-value replacement from yet another unrelated field. Dismantle losing alternatives and move their blocks to QUARANTINED (reserved only for more-wicked future problems).

Example mechanism extraction:

Source: "Accountability Fabric for Autonomous Systems" (AI Liability) → Abstract Concept: Verifiable Attribution → Operational Mechanism: Immutable Cryptographic Ledgering → Vaulted as unassigned raw material, fully disassociated from AI/liability.

Recommendation▾

Add a counter-example showing a failed/bad application (e.g., shallow collision or 51% recycling in practice) to contrast with good outcomes, not just describe the pitfall abstractly

Workflow14 / 15

Progress:
- [ ] Stage I: Strategic Disintegration — deconstruct source solution into Concept/Mechanism pairs
- [ ] Stage I: Catalog all pairs into Residual Inventory (unassigned, domain-agnostic)
- [ ] Stage II: Build Divergent Matrix — Mechanisms (Axis A) x Unrelated Fields (Axis B)
- [ ] Stage II: Force collision at each cell — synthesize a new problem statement
- [ ] Stage III: Generate hybrid pillars (mechanism + foreign principle, 50/50)
- [ ] Stage III: Map operational flow between hybrid pillars; name the new solution
- [ ] Stage IV: Check for shared/duplicate blocks across active solutions
- [ ] Stage IV: Run Proxy Search for any shared block; replace with new equal/greater-value component
- [ ] Stage IV: Mark used blocks EXHAUSTED; quarantine blocks from rejected alternatives
- [ ] Final: Register new construct in Building Block Inventory & Status Registry

Stage I: Strategic Disintegration

Sever the solution name/problem pairing completely — do not let original context bias Stage II.
Every pillar decomposes into exactly two atomic layers: Abstract Concept (principle) and Operational Mechanism (functional engine).
Deposit into the vault as raw, unlabeled material — strip branding and domain jargon.

Stage II: Targeted Sweep & Divergent Collision

Axis B fields must be genuinely non-adjacent to the source domain — reject anything with an obvious conceptual bridge already in common use.
For each matrix cell, force the question even if the first instinct is "no connection exists." The friction is the point.
Output must be a crisp, actionable problem statement — not a vague observation.

Stage III: Hybrid Re-Bricolage

Reject pillars that are >50% recycled mechanism with no foreign contribution — every pillar needs a genuinely new element.
Map how hybrid pillars interface (data/energy/trust flow between them), not just list them.
Give the new construct a standalone name — it must not reference the parent solution.

Stage IV: Governance, Scarcity & Proxy Exchange

Single-Use Rule: once a block is selected for a primary build, mark EXHAUSTED immediately — no backsliding.
Proxy Sourcing: if the same block appears in two active proposals, the secondary use must be replaced via Proxy Search, never the primary.
Quarantine: losing alternative builds get dismantled; their blocks go to QUARANTINED, reserved exclusively for problems unsolvable by any active block.

Recommendation▾

The two examples are solid but both are 'successful' outcomes — include a worked example of the Proxy Search replacement process end-to-end with full before/after block states

Registry Templates

Building Block Inventory

Component ID	Original Source Domain	Abstract Concept / Mechanism	Status	Assigned Deployment
BB-01	Distributed Systems / Law	Cryptographic Ledgering	EXHAUSTED	Marine Ecosystem Tracking
BB-02	Marine Mycology	Nutrient Exchange Logic	ACTIVE	Bio-Dynamic Supply Networks
BB-03	Chaos Theory	Lorenz Attractor Boundaries	QUARANTINED	Reserved for More Wicked Problems

Status values: ACTIVE (available), EXHAUSTED (spent, unreusable), QUARANTINED (retired, reserved).

Project Ledger fields: Project Lead, Execution Date, Target Domain, Source Legacy Solution, Proxy Search Log (Original Block → Target Domain → Proxy Replacement → Value Justification).

Examples15 / 20

Example 1: Input: Source solution = "Zero-Trust Network Access" (Cybersecurity). Target sweep fields = Epidemiology, Urban Traffic Engineering, Coral Reef Symbiosis. Output:

Mechanism extracted: Continuous Identity Re-Verification (abstract: Never-Trust Persistence)
Collision with Epidemiology → New problem: "How do you prevent asymptomatic super-spreader contact chains in dense urban transit without blanket lockdowns?"
Hybrid pillar: Continuous Identity Re-Verification + Epidemiological Contact-Tracing Decay Curves → "Trust-Decay Transit Passport": a rider's access privileges continuously re-verify against real-time exposure risk, decaying like a half-life rather than binary allow/deny.
BB "Continuous Identity Re-Verification" marked EXHAUSTED for this deployment.

Example 2: Input: Two active proposals both use BB-04 "Vacuum Fluctuation Forging" (Quantum Electrodynamics mechanism for generating value from apparent emptiness). Output: Proxy Search triggered for the secondary proposal (On-Demand Virtual Supply Chains keeps original; the second, in Agricultural Fallow-Land Monetization, is reassigned a proxy from Structural Geology — "Subduction Zone Recycling" — reframed as "dormant-land value is recycled back into the productive cycle like subducted crust resurfacing as volcanic soil."

Recommendation▾

Quick Start example is truncated mid-process (doesn't show the full Collide→Re-Bricolage→Govern loop for that source), making it less immediately actionable than the full workflow below it

Best Practices

Force genuine domain distance in Stage II — if a bridge feels obvious, the field isn't divergent enough.
Always extract two layers (concept + mechanism) per pillar; skipping the abstract layer causes literal, uncreative transposition.
Treat EXHAUSTED as truly permanent within a portfolio cycle — the scarcity is what drives novel sourcing, not a formality.
Quarantined blocks are not dead; revisit them specifically when a new problem is rated "more wicked" than anything solvable by active inventory.
Name hybrid solutions independently — a name tied to the parent system signals incomplete disintegration.

Common Pitfalls

Skipping disassociation: jumping straight to "how do we reuse X" without formally severing it from its origin domain re-anchors thinking to the old problem.
Shallow collision: accepting the first weak analogy instead of pushing until a precise, actionable problem statement emerges.
51% recycling: building "hybrid" pillars that are almost entirely the original mechanism with cosmetic foreign flavor — violates the newly-discovered-element requirement.
Silent reuse: allowing a block to quietly serve two active solutions without triggering Proxy Search — defeats the scarcity mechanism's purpose.
Permanent hoarding: treating QUARANTINED blocks as a backup pool for convenience rather than reserving them strictly for genuinely more-wicked problems.