Library
v1.0.1Authorized SansFiction library manager. Adds books to your library, updates reading status, logs progress, and can schedule a daily “how much did you read today?” check-in. Requires a SansFiction personal token (read/write).
⭐ 3· 1.7k·1 current·1 all-time
by@fgbytes
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill's name/description (SansFiction library manager) aligns with using a SansFiction personal token and calling the service's MCP endpoint. However, the runtime instructions assume use of the OpenClaw CLI (openclaw cron add) without listing that CLI as a required binary — a minor coherence gap. Overall capabilities requested are plausible for the described feature set.
Instruction Scope
The SKILL.md instructs the agent to have the user paste the SANSFICTION_TOKEN 'once' into chat and then persist it into ~/.openclaw/openclaw.json or env vars. This is contradictory and risky: asking the user to paste a secret into chat exposes it to chat logs and platform storage. The document also contains a hard rule 'Never echo the token back or write it into chat logs' which conflicts with the 'paste in this chat' step — the conflict is a practical security concern because the platform may retain chat history. Apart from that, the instructions otherwise stay within the library management scope (search/add/status/log/stats) and call only the documented SansFiction MCP endpoint.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, which minimizes install-time risk. It requires the 'curl' binary (declared). No remote downloads or extracted archives are present.
Credentials
The skill uses a single primary credential (SANSFICTION_TOKEN), which is appropriate for an API-based library manager. That token is justified by the described read/write operations. Caveat: the SKILL.md's suggested token handling (paste into chat then persist to ~/.openclaw/openclaw.json) increases exposure risk compared with using a secure secret store; also the metadata lists curl as a required binary but the instructions rely on the OpenClaw CLI for cron scheduling without declaring it.
Persistence & Privilege
The skill is not marked always:true (good). It can be invoked autonomously (disable-model-invocation:false), which is the platform default; combined with the ability to schedule a cron job, the skill can cause recurring agent actions (daily check-in). This is reasonable for a reminder feature but increases the impact if the skill were misused, so be cautious about granting it persistent token access.
What to consider before installing
This skill appears to implement the described SansFiction functionality, but do not paste your personal token into chat unless you understand how your platform treats chat history -- that step introduces real risk. Prefer storing the token via a secure platform secret or directly editing ~/.openclaw/openclaw.json yourself rather than sending it in chat. Confirm the skill will not echo the token and that OpenClaw will treat it as a hidden secret. Ask the publisher (or verify on the SansFiction docs) why the skill hard-codes Europe/Warsaw as the default cron timezone and why the OpenClaw CLI is used without being listed as a required binary. Only install if you trust the skill source and are comfortable with an agent that can schedule recurring reminders using your token.Like a lobster shell, security has layers — review code before you run it.
latestvk973q821cttfm91qmbx0snmn8980c7kf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📚 Clawdis
Binscurl
Primary envSANSFICTION_TOKEN