Token导航 LogoToken导航

Agent Skill · 效率

painpoint(painpoint 效率)

painpoint 用于辅助前端页面、组件、样式和交互逻辑开发,适合在 OpenClaw 中需要维护前端项目、生成组件或检查界面实现时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

painpoint 是效率类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描已通过,按安装量在效率类的 21,003 个 Skill 里排第 17,910。

总安装 2,472周安装 101GitHub Stars 公开资料未说明下载 792核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install painpoint

这个 Skill 是做什么的

效率类 Skill 把重复的整理、汇总、转换工作交给助手完成,减少手工复制粘贴。

汇总 NicheStarter API 每周发布的五大痛点报告。引导用户登录查看完整分析报告详情。提供行业趋势洞察与潜在机会参考。适用宿主包括 OpenClaw,接入前应确认版本、权限和运行环境要求。部分数据需账户授权才能获取完整内容。painpoint 属于效率类 Skill,可作为该场景下的辅助能力补充。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

painpoint 怎么安装?

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

painpoint 支持哪些 AI 工具?

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

painpoint 需要什么权限?

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

painpoint 是免费的吗?

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

painpoint 用的人多吗?

公开数据是累计安装 2,472 次,近一周安装 101 次,下载 792 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

painpoint 安全吗?

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

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

值得选的地方

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

先想清楚的地方

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

适不适合你

更适合

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

不太适合

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

效率类 Skill 对比

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

GitHub 代码协作 · OpenClaw

7,632,918545需要联网MIT-0通过
nano-pdf

Nano PDF 文档 · OpenClaw

4,249,476231需要联网MIT-0通过
auto-updater

自动更新程序 · OpenClaw

2,964,063386操作浏览器MIT-0通过
video-frames

视频帧 · OpenClaw

2,621,304112需要联网MIT-0通过
gemini

Gemini 助手 · OpenClaw

2,547,39648需要联网MIT-0有提醒
painpoint

painpoint 效率 · 本页

2,472—需要联网MIT-0通过

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

SKILL.md 原文

name
nichestarter-weekly-report-preview
description
Summarizes the latest NicheStarter weekly pain-point report from the public preview API, lists top five pain points, and guides users to sign in for the full report and free weekly email subscription. Supports scheduled runs (cron, OpenClaw, or other agents) to deliver the digest with a consistent style. Use when the user asks for the weekly report, Monday digest, top pain points this week, teaser content, or automated weekly delivery.

NicheStarter Weekly Report Preview

Purpose

Turn the latest weekly pain-point report into a short, trustworthy teaser:

  • Brief summary aligned with report.summary and report.report_title
  • Top 5 pain points (title, short description, optional source + insight link)
  • Clear CTA: sign in for the full report and subscribe free for weekly email (Mondays)

Data source (API-first)

Fetch:

  • GET https://www.nichestarter.ai/api/public/weekly-report-preview

No authentication. Response includes report, top_pain_points (5), and cta with URLs.

If the API returns 404, say no report is published yet and point to https://www.nichestarter.ai to explore insights or sign up.

Workflow

  1. Call the preview endpoint and read report, top_pain_points, cta.
  2. Write a 2–4 sentence executive brief (no hype, no invented stats).
  3. List exactly five items when present: rank, title, one-line why it matters, optional primary_source_url, insight_url.
  4. Add CTA block:

- Full report: sign in → Dashboard → Weekly Reports (cta.dashboard_weekly_reports_url or https://www.nichestarter.ai/dashboard#weeklyreport) - Free weekly email: subscribe on the site (cta.message + cta.website)

  1. Do not promise paid-only features to free users; use neutral wording (“see full list and features after sign-in”).

Output format

## Weekly pain-point snapshot — [report_title]
**Report date:** [created_at as human-readable]
[Brief summary paragraph]

### Top 5 this week
1. ...
2. ...
...

### Get the full picture
- Sign in: [sign_in_url or www.nichestarter.ai]
- Open **Weekly Reports** in the dashboard: [dashboard_weekly_reports_url]
- **Free** weekly email with more detail (Mondays): mention www.nichestarter.ai

Rules

  • English unless the user asks otherwise.
  • Do not fabricate pain points, rankings, or subscriber counts.
  • Do not expose internal env vars or non-public APIs.
  • Treat content as community signal, not guaranteed demand.

Scheduled delivery (cron / OpenClaw / other agents)

Use this skill on a fixed schedule so users get the same structure every week.

When to run

  • Default: once per week on Monday, after your platform’s weekly report is published (align with NicheStarter’s “Monday” weekly email messaging).
  • Pick one timezone (e.g. America/New_York 08:00) and keep it stable for recipients.

Cron / scheduler setup (conceptual)

  1. Configure the host (OpenClaw, GitHub Actions, cron, n8n, etc.) to trigger one job per week.
  2. Job steps:

- GET https://www.nichestarter.ai/api/public/weekly-report-preview - If 404 or empty top_pain_points: send a short fallback (“No new weekly report yet — check https://www.nichestarter.ai”). - Else: follow Workflow and Delivery style below, then send via your channel (email, DM, Slack, etc.).

  1. Deduplication: persist the last sent report.id from the JSON. If the next run returns the same report.id, skip sending (avoids double-send if cron overlaps).
  2. Retries: on 5xx, retry with backoff; do not fabricate content if the API never succeeds.

Delivery style (proper format for end users)

Apply the same structure whether the message is email, chat, or push:

  • Subject / first line (email or thread):

NicheStarter — Weekly pain points · [YYYY-MM-DD] or use report.report_title shortened to ~60 characters.

  • Opening: one line context: “Here’s this week’s snapshot from community discussions (teaser).”
  • Body: use the Output format section (headings, numbered top 5, bullets for links).
  • Links: use full https:// URLs from cta and each insight_url / primary_source_url (plain text, one URL per line in chat clients if line-wrapping breaks).
  • Tone: calm, practical, no hype; no emojis required (optional single ✉️ or 📊 if the channel expects it).
  • Length: keep under ~400 words for email; under ~2500 characters for SMS-style limits if applicable.
  • Footer: always include cta.website and one line: sign in for full report + free weekly subscription on the site.

OpenClaw (or similar agent) prompt snippet

When scheduling the agent, attach this skill and use a user task like:

Run the NicheStarter weekly report preview skill.
Fetch the API, build the digest using the Output format and Delivery style sections,
then send it to [recipient / channel] with subject line as specified.
If report.id matches [last_sent_report_id], reply only "Skipped (already sent)."

Store last_sent_report_id in OpenClaw memory, a small file, or your workflow state.

Additional resources

Install (Cursor / other agents)

  • Raw file URL (production): https://www.nichestarter.ai/skills/nichestarter-weekly-report-preview/SKILL.md
  • Copy this folder into your agent’s skills directory (or download SKILL.md + reference.md from the URL above).

平台分布

OpenClaw

74.48%
按下载量换算590

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills