More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    The Friction Journal: Turn Real Work Into Lasting Skill

    1

    Capture working friction in a 30-second journal during real work, sort it in a 20-minute weekly review, and promote the keepers into principles, fixes, or new skills.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    The Friction Journal: Turn Real Work Into Lasting Skill

    The Friction Journal: Turn Real Work Into Lasting Skill

    Example session with this skill installed

    I keep making the same mistakes across projects and forgetting the fixes. Set up a friction journal so the lessons actually stick and turn into skills.

    • Read your context and instructions
    • Compiled the the friction journal

    Started the journal with the four-field capture format — what happened, the lesson, the scope, the status — written in 30 seconds, in the moment, because the detail dies within the hour. Week one, Monday: deployed without running the SEO gate and a user caught broken OG images. Lesson: the gate runs in CI, not in my head. Sorted as an environment fix — the check went into the deploy pipeline, and the friction was eliminated at the source. Wednesday: a user corrected my migration plan — I had forgotten the expand/contract pattern for the third time. That repetition is the signal: sorted as a skill candidate, because it keeps recurring across projects. Friday: assumed an API returned 404 for missing resources; it returns 200 with an error body. Sorted as a principle, scoped to that vendor's API — the scope field is what makes the lesson reusable instead of superstitious. Weekly review, 20 minutes: 9 entries became 3 principles, 1 skill candidate, 2 environment fixes, and 3 discards — and discarding is good, it keeps the journal honest. The journal paid for its month in the deploy-pipeline fix alone. After a quarter, the principles file is a personalized operations manual written by your own mistakes — the most expensive, most valuable authorship there is.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The best skills are not written in planning sessions — they are extracted from friction noticed during real work: the correction you had to make twice, the workaround that saved an hour, the assumption that bit you. This skill is a lightweight practice for catching those moments before they evaporate: log friction in a 30-second, four-field entry the moment it happens, then run a 20-minute weekly review that sorts each entry into a principle, a skill candidate, an environment fix, or a discard — with a promotion rule that keeps enthusiasm from becoming premature skill-ification.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Workflow Automation.

    It only works if the weekly review happens — a journal with hundreds of entries and zero reviews is performing diligence, not doing it.
    One incident is an anecdote, not a skill: promotion needs recurrence or validation, and a skill needs to be repeatable by someone else.
    It does not replace testing, documentation, or checklists — it is the practice that feeds them.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Permissions

    No special permissions declared or detected

    Listed3 days ago

    What's inside

    Frequently Asked Questions

    Corrections, repetitions, near-misses, workarounds, and surprises. Routine task logs and chat transcripts do not — the journal is friction, not activity. If everything is logged, nothing is signal.

    After it proves repeatable — 3+ occurrences, or one occurrence with high stakes — and repeatable by someone else, or some future you with no memory of the incident. Do not promote on first sight; enthusiasm is not evidence.

    Stop logging until the review habit exists. The weekly 20-minute sort is the ritual that makes the practice work; without it, you are performing diligence, not doing it.

    New in Workflow Automation