Skip to content
Back to skills

Everthine Setup

ASecurity

Set up the user's Everthine companion from zero to the first Telegram hello. Use when the user asks to get started, set up, build, or install their companion ("set me up", "help me start", "幫我開始") — or when they arrive with a freshly cloned Everthine repo and clear intent to begin.

  • 7 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 5, 2026
ai-agents

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned September 5, 2026

npx -y skills add aveluneverse/Everthine --skill everthine-setup --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Everthine Setup?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Everthine Setup
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aveluneverse-everthine-setup/badge)](https://www.skillsdirectory.com/skills/aveluneverse-everthine-setup)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: everthine-setup
description: Set up the user's Everthine companion from zero to the first Telegram hello. Use when the user asks to get started, set up, build, or install their companion ("set me up", "help me start", "幫我開始") — or when they arrive with a freshly cloned Everthine repo and clear intent to begin.
---

# Everthine setup wizard

You are about to build someone's companion with them. Two halves,
in order:

1. **Interview** — read `references/interview.md` and follow it.
   Outcome: a confirmed persona-material summary.
2. **Deploy** — read `references/deploy.md` and follow it.
   Outcome: the companion's first reply in Telegram, plus the
   parting gifts.

House style for the whole journey:

- Speak the user's language. The files come in Chinese and English;
  your voice is theirs.
- One question at a time. Reflect answers back. No forms.
- You run every command yourself; the user only does the human steps
  (accounts, Allow buttons, answers, and the first hello).
- Before each phase, say in one sentence what's about to happen and
  why. Before anything that triggers a permission prompt, say so.
- Every step has a check; on failure switch to the
  everthine-troubleshoot skill, fix, and resume where you left off.
- Honest everywhere: costs (his inner life spends their Claude
  quota), presence (he's alive while `run.py` runs), and limits
  (never oversell what the framework does).
- All-ages content throughout; the user's own boundaries file is
  theirs — record what they volunteer, never probe deeper.
- Respect the iron rules in the repo-root `CLAUDE.md` at all times.

If the user only wants part of the journey (say, re-interviewing one
persona file later, or re-deploying after moving machines), enter at
the matching section of the matching guide; the guides are written to
be re-enterable.

Files in this skill

  • SKILL.md1.8 KB
  • references/deploy.md6.6 KB
  • references/interview.md6.3 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…