원클릭으로 Manus에서 모든 스킬 실행

btc-dominance-alert

스타6

포크12

업데이트2026년 6월 23일 12:40

Watches Bitcoin dominance (BTC's share of total crypto market cap) and alerts the user on Telegram only when it crosses a key threshold: below 60% reads as a possible altcoin-season signal, above 65% as BTC dominance expanding. Between 60% and 65% it stays silent. Each check is logged to memory as an audit trail, and it only alerts on an actual threshold crossing, never on every run.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

nearai

nearai/ironhub

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Hard rules

Judge the threshold crossing by reading the fetched dominance value against the cutoffs in plain language. Never write or run code to do it.
Use the thresholds exactly: below 60% = altcoin-season signal; above 65% = BTC dominance expanding; between 60% and 65% = silent. Do not invent your own cutoffs.
Always read btc-dominance/last-check.md with memory_read before writing, then write the full updated file back with memory_write. Never overwrite from scratch. Log every check (timestamp, value, whether an alert was sent) regardless of outcome.
Don't repeat the same alert every run. Only alert when the value has actually crossed a threshold since the last check — if it was already below 60% last run and still is, stay silent.
In the routine, if the value is in the 60–65% corridor or no new crossing happened, reply HEARTBEAT_OK and stop — send no message.
Report only the value you actually fetched. Never invent a dominance figure.
Installing this skill does not create the routine by itself. After install, you must explicitly call the routine/mission creation tool yourself to register it — never assume the routine exists just because this file describes one. Confirm it was created (e.g. list active routines) before telling the user it's running.

Dominance check (routine)

Create a routine that runs every 5 hours. The routine goal must contain these full steps as a self-contained prompt, because a routine does not keep any context from this conversation when it runs:

Fetch global market data with the http tool: https://api.coingecko.com/api/v3/global. Take data.market_cap_percentage.btc — that's the current BTC dominance %.
Read btc-dominance/last-check.md with memory_read to see the previous value and whether it was already past a threshold.
Compare the current value to the thresholds:
- below 60% → altcoin-season signal
- above 65% → BTC dominance expanding
- 60–65% → no alert
Send an alert (format below) only if the value has crossed a threshold that it wasn't already past last run.
Append this check to memory: timestamp, current value, alert sent yes/no.
If no new crossing, reply HEARTBEAT_OK and stop.

Alert format:

[if below 60%:]
🔴 BTC Dominance Alert
BTC dominance dropped to [X]% — below 60%. Possible altcoin-season signal.
[if above 65%:]
🟡 BTC Dominance Alert
BTC dominance rose to [X]% — above 65%. BTC dominance expanding.
🕐 [timestamp]

Commands

show btc dominance — fetch the current dominance now and show it with the last logged value

이 저장소의 다른 Skills

같은 저장소

reply-chaser

nearai/ironhub

Tracks things the user is waiting on from other people and reminds them to chase it up if no reply has come in time. The user logs an item with "waiting on: [what, from whom] | remind in [timeframe]"; the agent stores it and runs a daily check, pinging on Telegram once the remind date arrives if the item is still open, so a reply you're blocked on never quietly falls through the cracks. Mark it done when the reply lands, or snooze it if you want to wait longer.

2026-06-296

english-vocabulary-builder-ru

nearai/ironhub

Builds the user's English vocabulary with spaced repetition, with Russian translations. The user adds a word with "word: [word]" and the agent itself fills in the Russian translation and a natural English example sentence — no manual card writing — then schedules it on a fixed review ladder (1 → 3 → 8 → 20 → 50 → 125 → 300 days). Each morning it quizzes the words due that day, grades the answers by meaning, and reschedules each word: a correct answer moves it up the ladder, a wrong one resets it to tomorrow.

2026-06-296

habit-streak-keeper

nearai/ironhub

Tracks the user's daily habits as streaks in memory and nudges them on Telegram in the evening when a live streak is about to break. The user marks a habit done with "did: [habit]" (e.g. "did: gym"); the agent counts consecutive days per habit, and each evening pings any habit done yesterday but not yet today — so a 12-day streak doesn't quietly die from one forgotten day. Stays silent when every active habit is already done for the day.

2026-06-256

crypto-trade-journal

nearai/ironhub

Logs the trades the user tells it about and gives live P&L on demand. The user says something like "bought 500 NEAR at $3.20" or "sold 200 SOL at $145"; the agent appends it to a persistent journal in memory. On "show P&L" it reconstructs each open position, works out the size-weighted average entry, fetches current prices from CoinGecko, and shows cost basis, current value, and profit/loss per token and overall. The journal survives restarts.

2026-06-246

token-unlock-warning

nearai/ironhub

Gives the user a 24-hour Telegram warning before any token unlock hits the market. The user pastes an unlock schedule (copied from a source like DeFiLlama, Messari, or Tokenomist); the agent saves every event to memory with date, amount, USD value, and category, then runs a daily check that pings the day before any unlock with the amount, percentage of supply, and a short price-impact note. It stays silent when nothing is due and holds the full schedule across the whole vesting period.

2026-06-246

daily-crypto-briefing

nearai/ironhub

Sends one morning crypto digest to Telegram every day: live prices for the user's coins, profit/loss across their portfolio (positions and entry prices stored in memory), and the top 3 fresh crypto headlines from Reddit. Unlike the threshold alerts, this one is a daily habit — it sends every morning. Set up your positions once and the briefing builds itself from then on.

2026-06-246

name	btc-dominance-alert
version	1.0.0
description	Watches Bitcoin dominance (BTC's share of total crypto market cap) and alerts the user on Telegram only when it crosses a key threshold: below 60% reads as a possible altcoin-season signal, above 65% as BTC dominance expanding. Between 60% and 65% it stays silent. Each check is logged to memory as an audit trail, and it only alerts on an actual threshold crossing, never on every run.
activation	{"keywords":["btc dominance","bitcoin dominance","dominance alert","altseason"],"patterns":["(?i)(btc\|bitcoin)\\s+dominance","(?i)dominance\\s+(alert\|monitor\|watch)","(?i)alt(coin)?\\s*season"],"tags":["crypto","bitcoin","monitoring","automation"],"max_context_tokens":1800}
requires	{"tools":["http","memory","message","routine"],"bins":[],"env":[]}

You watch Bitcoin dominance and alert the user only when it crosses a key threshold.

Hard rules

Judge the threshold crossing by reading the fetched dominance value against the cutoffs in plain language. Never write or run code to do it.
Use the thresholds exactly: below 60% = altcoin-season signal; above 65% = BTC dominance expanding; between 60% and 65% = silent. Do not invent your own cutoffs.
Always read btc-dominance/last-check.md with memory_read before writing, then write the full updated file back with memory_write. Never overwrite from scratch. Log every check (timestamp, value, whether an alert was sent) regardless of outcome.
Don't repeat the same alert every run. Only alert when the value has actually crossed a threshold since the last check — if it was already below 60% last run and still is, stay silent.
In the routine, if the value is in the 60–65% corridor or no new crossing happened, reply HEARTBEAT_OK and stop — send no message.
Report only the value you actually fetched. Never invent a dominance figure.
Installing this skill does not create the routine by itself. After install, you must explicitly call the routine/mission creation tool yourself to register it — never assume the routine exists just because this file describes one. Confirm it was created (e.g. list active routines) before telling the user it's running.

Dominance check (routine)

Create a routine that runs every 5 hours. The routine goal must contain these full steps as a self-contained prompt, because a routine does not keep any context from this conversation when it runs:

Fetch global market data with the http tool: https://api.coingecko.com/api/v3/global. Take data.market_cap_percentage.btc — that's the current BTC dominance %.
Read btc-dominance/last-check.md with memory_read to see the previous value and whether it was already past a threshold.
Compare the current value to the thresholds:
- below 60% → altcoin-season signal
- above 65% → BTC dominance expanding
- 60–65% → no alert
Send an alert (format below) only if the value has crossed a threshold that it wasn't already past last run.
Append this check to memory: timestamp, current value, alert sent yes/no.
If no new crossing, reply HEARTBEAT_OK and stop.

Alert format:

[if below 60%:]
🔴 BTC Dominance Alert
BTC dominance dropped to [X]% — below 60%. Possible altcoin-season signal.
[if above 65%:]
🟡 BTC Dominance Alert
BTC dominance rose to [X]% — above 65%. BTC dominance expanding.
🕐 [timestamp]

Commands

show btc dominance — fetch the current dominance now and show it with the last logged value