mcpbeat Sign in

Grad Flow Agent Skill

Apply flow theory to diagnose optimal experience conditions and design environments that balance challenge and skill for sustained engagement. Use this skill when the user needs to explain why users disengage from tasks, optimize task difficulty for peak performance, design learning progressions or gamification systems, or when they ask 'why do people lose focus', 'how to design for engagement', or 'what conditions produce peak performance'.

3k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
223
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/asgard-ai-platform/skills --skill grad-flow

What comes with it

6 870 bytes besides the instruction
examples/sample_scenario.md

The instruction itself

13 sections, as written by the author

Flow Theory

Overview

Flow theory (Csikszentmihalyi, 1990) describes a psychological state of complete absorption in an activity where a person's skills are fully engaged by a commensurate challenge. Flow occurs in a narrow channel between anxiety (challenge exceeds skill) and boredom (skill exceeds challenge), requiring clear goals, immediate feedback, and a perceived skill-challenge balance.

When to Use

  • Diagnosing why users or learners disengage (boredom) or quit (anxiety/frustration)
  • Designing difficulty curves in learning systems, games, or productivity tools
  • Evaluating workplace conditions for sustained deep work
  • Structuring tasks to maximize intrinsic motivation and performance

When NOT to Use

  • When disengagement is caused by external factors (compensation, politics) rather than task design
  • For tasks that are inherently routine and cannot be meaningfully restructured
  • As a universal productivity prescription — flow is state-dependent, not always achievable or desirable

Assumptions

IRON LAW: Flow occurs ONLY when perceived challenge matches
perceived skill — too easy breeds boredom, too hard breeds
anxiety. Both dimensions are SUBJECTIVE perceptions, not
objective measurements.

Key assumptions:

  • Flow is autotelic — the activity becomes intrinsically rewarding, independent of external outcomes
  • Clear proximal goals and immediate feedback are necessary preconditions, not optional enhancements
  • The flow channel is dynamic — as skill grows, challenge must escalate to maintain the balance

Methodology

Step 1 — Map the Skill-Challenge Space

Plot the target activity on the experience quadrant:

High Challenge
      |
 Anxiety  |  FLOW
      |
------+----------
      |
 Apathy   |  Boredom
      |
      Low Skill ——————— High Skill

Step 2 — Assess Flow Preconditions

Check the three necessary conditions:

  • Clear goals: Does the person know what to do next at every moment?
  • Immediate feedback: Can they tell if they are succeeding or failing in real time?
  • Skill-challenge balance: Is the task difficulty calibrated to their current ability?

Step 3 — Identify Flow Blockers

Common blockers: interruptions, ambiguous goals, delayed feedback, fixed difficulty (no adaptive scaling), multitasking, self-consciousness, external evaluation pressure.

Step 4 — Design Flow-Conducive Environment

  • Scaffold difficulty progression (gradually increasing challenge)
  • Provide real-time, informational feedback
  • Minimize interruptions and context-switching
  • Allow autonomy in approach while maintaining clear objectives
  • Build in mastery signals that make skill growth visible

Output Format

## Flow Analysis: [Context]

### Current State Diagnosis
- Perceived skill level: [Low/Medium/High]
- Perceived challenge level: [Low/Medium/High]
- Current experience zone: [Flow/Anxiety/Boredom/Apathy]

### Precondition Check
| Condition | Status | Evidence |
|-----------|--------|----------|
| Clear goals | [Met/Unmet] | [observation] |
| Immediate feedback | [Met/Unmet] | [observation] |
| Skill-challenge match | [Met/Unmet] | [observation] |

### Flow Blockers
- [Blocker and its impact]

### Design Recommendations
1. [Challenge calibration change]
2. [Feedback mechanism improvement]
3. [Environmental modification]

Gotchas

  • Flow is a subjective state — the same task at the same difficulty can produce flow or boredom depending on the individual's perceived skill
  • Flow is not always positive; it can occur in addictive or harmful activities (gambling, doomscrolling) — ethical design requires guardrails
  • Csikszentmihalyi's original research used Experience Sampling Method (ESM), which has self-report limitations
  • Group flow (e.g., jazz ensembles, sports teams) has additional conditions beyond individual flow — shared goals, equal participation, communication
  • Flow does not require peak difficulty — moderate, well-matched challenges are sufficient and more sustainable
  • Interruption recovery time after flow disruption is significant (15-25 minutes); fragmented schedules prevent flow entry

References

  • Csikszentmihalyi, M. (1990). *Flow: the psychology of optimal experience*. Harper & Row.
  • Csikszentmihalyi, M. (1997). *Finding flow: the psychology of engagement with everyday life*. Basic Books.
  • Nakamura, J. & Csikszentmihalyi, M. (2002). The concept of flow. In C. R. Snyder & S. J. Lopez (Eds.), *Handbook of positive psychology* (pp. 89-105). Oxford University Press.

Other skills for the same job

different authors, same section of the catalogue
Protocolsio Integration
by christophacham
×4

Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.

16k tokens
Tailored Resume Generator
by frostant
×4

Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances

3k tokens
Excalidraw Diagram Generator
by github
vendor ×3

Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.

36k tokens scripts
Expo Dev Client
by openai
vendor ×3

Build and distribute Expo development clients locally or via TestFlight

961 tokens
Executing Plans
by ZhanlinCui
×3

Use when you have a written implementation plan to execute in a separate session with review checkpoints

542 tokens
Anndata
by christophacham
×3

Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.

16k tokens
Benchling Integration
by christophacham
×3

Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.

14k tokens
Biopython
by christophacham
×3

Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.

24k tokens

How to use it

Copy the folder

Take asgard-ai-platform/grad-flow from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.