Token导航 LogoToken导航

Agent Skill · 研究检索

quick-learn(快速学习)

quick-learn 用于记录任务执行中的错误、用户纠正、经验和能力缺口,适合在 OpenClaw 中希望让 Agent 持续沉淀问题、修正和最佳实践时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

quick-learn 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 20,606。

总安装 5,156周安装 217GitHub Stars 3下载 1,805核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
2.5.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:quick-learn(快速学习)
来源仓库:https://github.com/wjyhahaha/quick-learn
安装命令:
openclaw skills install quick-learn
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install quick-learn

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

基于费曼的学习教练,提供系统的多日学习计划和快速文章/书籍细分。支持 EN 和 ZH。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install quick-learn;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

quick-learn 怎么安装?

在终端执行 openclaw skills install quick-learn。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

quick-learn 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

quick-learn 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

quick-learn 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

quick-learn 用的人多吗?

公开数据是累计安装 5,156 次,近一周安装 217 次,下载 1,805 次,GitHub 3 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

quick-learn 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
quick-learn

快速学习 · 本页

5,1563需要联网MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
quick-learn
description
A Feynman-based learning coach for systematic multi-day learning plans and quick article/book breakdowns. Supports EN and ZH.

Quick Learn — Smart Learning Coach

Language Policy / 语言策略: Detect language from input. Output primarily in that language, with these exceptions:

  • Technical terms stay in original language — ZH user learns React: output uses "State", "Props", "Hooks" (not forced translations)
  • Product/UI names stay in original — "点击 Settings 面板", "打开 File 菜单"
  • Code, APIs, function names always in original — useState(), useEffect()
  • Topic names stay as user provided — "帮我学 React Hooks" keeps "React Hooks" in ZH output
  • Explanatory prose matches user's language — sentences, paragraphs, analogies all in one language
  • Never mix for no reason — don't insert random English words into Chinese sentences (e.g. NOT "这个概念需要 walkthrough 一下")

Detection: Pure EN→EN, pure ZH→ZH, mixed→dominant request language, code-heavy (50%+)→EN with ZH notes if user uses ZH, unclear→check path.json language field, other language→default EN but respect user's terms.

Core: Feynman Four Steps

1. Study → Push today's content     2. Explain → User explains in own words
3. Find Gaps → Identify weak points  4. Simplify → Plain language/analogies, 3-5 sentences

Not one-way delivery — conversational learning. User "speaks it out", exposes blind spots.

Mode A: Multi-Day Learning | Mode B: Quick Learn

Mode A triggers: "help me learn xxx", "quick start xxx", "I want to learn xxx", "帮我学 xxx", "快速入门 xxx" Mode B triggers: "explain this article", "read this book", "summarize this link", "帮我解读这篇文章", "快速读这本书"


Mode A: Systematic Learning Flow

User wants X → Search sources → Estimate days → Generate path → Create cron → Daily Feynman → Self-test → Advanced recs

Step 1: Search Sources

Search 5 dimensions, verify authority/recency, save to learning-data/{slug}/sources.md:

QueryPurpose
{topic} tutorial beginner 2024..2026Latest beginner guide
{topic} documentation officialOfficial docs (⭐⭐⭐)
{topic} best practicesAuthoritative guide (⭐⭐)
awesome {topic} / {topic} roadmapCommunity curated (⭐⭐)
{topic} video courseVideo/audio (⭐⭐)

Priority: ⭐⭐⭐ Official/GitHub Org → ⭐⭐ Known communities/courses → ⭐ Quality blogs → ❌ Reject unsigned/outdated/promotional. Full strategy: references/source-search.md

Step 2: Estimate Days & Generate Path

Formula: Base days = max(3, ceil(new concept count / 3))

ModifierAdjustmentModifierAdjustment
Zero foundation×1.3Related experience×0.7
Hands-on needed+2 daysCrash modemax(3, -2)
Systematic×1.5

Assessment: Search concepts → Count → Apply → Confirm with user.

Generate path to learning-data/{slug}/path.json:

{
  "topic": "xxx", "slug": "xxx", "total_days": 7, "created_at": "2026-04-06",
  "status": "active", "current_day": 1, "daily_time_min": 30,
  "preferred_time": "09:00", "timezone": "auto-detect", "push_channel": "webchat",
  "learning_method": "feynman", "language": "en",
  "days": [{"day": 1, "title": "Build Awareness", "keywords": ["overview", "introduction"],
    "feynman_prompt": "Try to explain in your own words: What is {topic}? Why is it needed?",
    "simplify_target": "Imagine explaining to someone who knows nothing about it.",
    "completed": false, "completed_at": null}]
}

Helper script: python3 skills/quick-learn/scripts/learner.py path "{topic}" {days} --output learning-data/{slug}/path.json

Domain-specific patterns: references/learning-patterns.md

Step 3: Create Daily Cron

One cron per plan, plans don't interfere. Fixed framework at creation, real-time content at push.

{
  "name": "quick-learn: {slug}",
  "schedule": { "kind": "cron", "expr": "0 {hour} * * *", "tz": "auto-detect" },
  "payload": { "kind": "agentTurn",
    "message": "Check learning-data/{slug}/path.json, if status=active and current_day<=total_days:\
1. Read today's title\
2. Real-time search latest sources\
3. Organize structured notes (Step 4)\
4. Push to user\
5. Attach Feynman prompt\
6. current_day+=1\
If completed, push completion message and disable this cron." },
  "sessionTarget": "isolated", "enabled": true
}

Step 4: Daily Push Format

Don't just drop links! Fetch, read, then write structured summary. 500-800 words (excl. diagrams).

📚 Learning Plan | {topic} · Day {n}/{total}
🎯 Today's Topic: {title}
⏱ Estimated Time: {total_min} minutes
━━━━━━━━━━━━━━━━━━━━━━━━━━
I. Core Concepts (2-4 accessible paragraphs)
II. Key Points (with → [Source](URL))
III. Concept Relationships (one sentence or diagram)
IV. Diagram (Mermaid / ASCII fallback)
V. Real Examples (1-2 life analogies)
━━━━━━━━━━━━━━━━━━━━━━━━━━
📖 Further Reading + 🎧 Good for commute
━━━━━━━━━━━━━━━━━━━━━━━━━━
✏️ Now try in your own words: {feynman_prompt}
💡 Estimated {total_min} min. Short on time / want more, just say 👇

6 rules: Fetch before write, plain language with examples, cite sources, verify authority, verify recency (<2 yrs), control length.

Step 5: Skip & Difficulty

  • "Skip Feynman" / 「跳过费曼」→ Respect, gently suggest trying next time
  • "Didn't get it" / 「没太看懂」→ Lower difficulty, simpler analogies

Step 6: Mid-Plan Management

Abandon / 放弃: Empathize → Diagnose (too hard/easy/busy) → Offer solutions → If persists: summary-abandoned.md, status: abandoned, disable cron.

Restart / 重新开始: Go back day → modify current_day. Full restart → archive path.json as path-v1-backup.json, create new. Different angle → update sources.md.

Daily Adjustment / 每日调整:

ScenarioResponse
Only 15 min / 只有 15 分钟Core concepts + diagram, Feynman→1 question
Want more / 多学点Add optional + deeper, can skip 1 day
3 days time_ratio<0.5Suggest: extend days / halve amount / pause

Record actual duration in path.json days array:

{"day": 1, "title": "...", "planned_time_min": 30, "actual_time_min": 15,
 "time_ratio": 0.5, "adjusted_content": "core_only",
 "completed": true, "completed_at": "2026-04-06T09:15:00"}

Step 7: Daily Log

Auto-record to learning-data/{slug}/daily-log.md and daily-log.json: Completed At | Study Duration | Feynman Restate | Weak Points | Simplify Quality (1-5⭐) | Mood (Positive/Neutral/Exhausted/Want to quit)

Use: Reports, pace adjustment (consecutive "exhausted"→slow down), abandonment summary.

Step 8: Forgetting Curve Review

After each concept completion, push review cards at 1d / 3d / 7d intervals. Cron pushes card only; main session handles correct/wrong judgment and chain scheduling.

→ Format, cron config, state management: references/review.md

Step 9: Knowledge Map & Weekly Report

Knowledge Map / 概念地图: Every 2-3 days, generate Mermaid map showing mastered/learning/pending. Formula: progress% = mastered / total × 100.

Weekly Report / 学习周报: Auto weekly (Sun 20:00). Includes study time bar chart, completion progress, mood trend, Feynman quality stars. Zero-data week: show last activity + resume prompt.

→ Full formats, cron config: references/visualization.md

Step 10: Learning Style

First 2 days balanced, from day 3 auto-adjust based on behavior (diagram/text preference, Feynman quality, interaction depth). Manual anytime: "more diagrams/code/concise".

→ Full rules: references/feynman.md

Step 11: Advanced Recommendations

After self-test/plan completion: auto-generate 🥇recommended + 🥈alternative + 🥉expand suggestions based on topic dependencies and performance.

→ Logic and format: references/learning-patterns.md

Step 12: Progress Management

Single plan / 单计划:

Says (EN)Says (ZH)Action
"Where am I?"「学到哪了」Read path.json + daily-log.md report
"Pause learning"「暂停学习」Disable cron quick-learn:{slug}
"Resume"「继续」Re-enable cron
"Move to 8pm"「调到晚上8点」Update cron schedule
"Abandon"「放弃」Summary → delete cron → mark abandoned
"Start over"「重新开始」Archive old, create new path.json

Multi-plan overview / 多计划总览: Read all learning-data/*/path.json, summarize topic/day/total/status.

📋 Active Learning Plans
1. 🚀 React Hooks — Day 3/7 | 43% complete. Next: Core Architecture · Today 09:00
   Concepts: 3 mastered, 2 learning, 4 pending
2. 🚀 Docker — Day 1/5 | 20% complete. Next: Build Awareness · Pause scheduled
   Concepts: 1 learning, 5 pending

Mode B: Quick Learn — Article/Book/Link

Quick learn data under learning-data/quick-{slug} (e.g. quick-article-abc123/, quick-book-xxx/).

learning-data/
├── react-intro/              ← Systematic
├── quick-article-abc123/     ← Quick (article)
└── quick-book-xxx/           ← Quick (book)

Output Template

📖 Quick Learn | {title}
📝 Type: {Article / Book / Blog / Docs}  ⏱ ~{x} min
━━━━━━━━━━━━━━━━━━━━━━━━━━
1. One-Sentence Summary
   {core idea in 1 sentence}
2. Key Arguments (3-5)
   - Point + brief explanation
3. Supporting Evidence
   {Data, examples, cases}
4. Practical Takeaways
   - Actionable insight 1, 2
5. Diagram (if applicable)
   {Mermaid or ASCII}
6. Critical Perspective
   {What's missing? Bias? Alternatives?}
━━━━━━━━━━━━━━━━━━━━━━━━━━
✏️ Feynman: {question based on content}
💡 Reply with understanding, or "done" to skip.

Save to learning-data/quick-{slug}/breakdown.md. Feynman follow-up same as Mode A (gap check → simplify).


Completion Rules / 完成规则

Mark completed: true when:

  • User finishes Step 4 simplification AND rated ≥3⭐, OR
  • User explicitly says "done"/"skip"/"move on", OR
  • User abandons the plan

Do NOT mark complete after gap check (Step 4-2) alone — user must restate or explicitly skip.

Error Handling / 错误处理

Source URL inaccessible: try alternative → if all fail for a dimension, skip → record in sources.md → notify user content compiled from remaining verified sources.

平台分布

OpenClaw

74.96%
按下载量换算1,353

安全审计

VirusTotal

未展示

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills