fluxly Search skills… ⌘K 中文 Publish

newsbox

DevOps Community
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
DevOps
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
88 / 100 · community maintained
Author / version / license
@tomevault-io · no license declared
Token usage
Moderate
Setup complexity
Manual integration
External API key
Not required
Operating systems
Docker
Runtime requirements
Python · Docker
Permissions
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
External requests
Install commands
26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview newsbox.preview 
---
name: newsbox
description: newsbox 是「采集层」CLI + SDK：从 RSS / 网页采集 AI 信源 → 落进 ~/.newsbox/raw.db（业务投影是 articlesraw 表；另有 sources…
category: devops
runtime: Python / Docker
---

# newsbox output preview

## PART A: Task fit
- Use case: newsbox 是「采集层」CLI + SDK：从 RSS / 网页采集 AI 信源 → 落进 ~/.newsbox/raw.db（业务投影是 articlesraw 表；另有 sourcestate 表记每个信源的最近抓取/失败状态，你通过 state 命令读，不需要自己直查）。它只采集，不做内容筛选 / 打分 / 摘要 / 日报（这些是消费方/agent 自己干）。 makes outbound network calls; runs on Python. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “数据怎么进、怎么出 / 场景 1：信源管理 / 加信源” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “newsbox 是「采集层」CLI + SDK：从 RSS / 网页采集 AI 信源 → 落进 ~/.newsbox/raw.db（业务投影是 articlesraw 表；另有 sourcestate 表记每个信源的最近抓取/失败状态，你通过 state 命令读，不需要自己直查）。它只采集，不做内容筛选 / 打分 / 摘要 / 日报（这些是消费方/agent 自己干）。 makes outbound network calls; runs on Python. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “数据怎么进、怎么出 / 场景 1：信源管理 / 加信源” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands, read environment variables; may access external network resources; usually needs no extra API key.

## Running Rules
- read files, write/modify files, run shell commands, read environment variables; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.
Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

  • Core job: newsbox 是「采集层」CLI + SDK：从 RSS / 网页采集 AI 信源 → 落进 ~/.newsbox/raw.db（业务投影是 articlesraw 表；另有 sourcestate 表记每个信源的最近抓取/失败状态，你通过 state…
  • Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
  • Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

  • Structure: The skill is organized around “数据怎么进、怎么出”, “场景 1：信源管理”, “加信源”, “录入前先侦察”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
  • Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
  • Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

  • Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
  • Invocation: Name newsbox directly; if the source includes slash commands, start with the command and then add task context.
  • Validation: Start small and check whether the result follows “数据怎么进、怎么出 / 场景 1：信源管理 / 加信源” before expanding.

Boundaries And Review

  • Dependencies: It usually needs no extra API key, so start with a small validation task.
  • Permissions: Declared permissions include read / write / shell-exec / env-read; ask the agent to state file, command, and rollback boundaries before acting.
  • Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.