Strategic Mentality

Apply battle-tested business mentality frameworks from Sun Tzu (Art of War), Alex Hormozi ($100M Leads), The 12 Week Year, and Dan Kennedy (No BS Direct Resp...

Security Scan

The skill's strategic guidance and templates are coherent, but its runtime instructions reference recurring Telegram pings, scraping/API integrations, and a specific 'Nex AI' deployment context without declaring any credentials or install needs — that mismatch is concerning and should be clarified before use.

Purpose & Capability

The skill claims to be a strategy/mentality framework (benign for advice). However, its instructions (HEARTBEAT.md and references) expect the agent to send scheduled Telegram messages, store trend data, run scrapers, query PageSpeed/social activity, and optionally use Resend/Calendly/Qwen Vision — none of which are declared in requires.env or install specs. Either the platform is expected to provide connectors (not documented), or the skill assumes access to external services that a user must authorize. This is an incoherence between purpose and the external capabilities the skill expects.

Instruction Scope

SKILL.md and HEARTBEAT.md explicitly instruct the agent to: (a) schedule weekly Telegram pings and monthly check-ins; (b) store weekly scores and trend history; (c) run reconnaissance (website checks, PageSpeed, social activity), and (d) optionally auto-load Nex AI-specific context which references internal endpoints and infrastructure. Those are operational actions beyond pure text advice and may cause network activity, data collection, or outbound messages. The instructions do not specify where credentials, chat IDs, or storage reside, and they grant broad discretion for scraping and automated outreach logic.

Install Mechanism

No install spec and no code files — the skill is instruction-only. That lowers disk/write risk: nothing will be downloaded or executed by an installer. The primary runtime surface is the agent following prose instructions.

Credentials

The skill requests no environment variables, yet references multiple services that normally require credentials (Telegram bots, Resend API, Calendly, Qwen Vision, Google/Maps scraping). The 'Nex AI Context' file contains private/internal endpoints and lists infrastructure (ports, domains, bots). Asking the agent to access those resources without declaring required env vars or explaining authorization is disproportionate and ambiguous — it could lead the agent to attempt to use platform-level credentials or hit internal endpoints unexpectedly.

Persistence & Privilege

HEARTBEAT.md configures recurring behavior (weekly Telegram pings, trend storage, execution alerts). 'always' is false and there's no install, so the platform would need to run a scheduler or the agent must be permitted to create persistent tasks. This persistent outbound communication capability is not inherently malicious but requires explicit user consent and clear configuration of where messages go and where data is stored.

What to consider before installing

This skill is mostly a set of well-structured business frameworks and templates, but it expects the agent to perform scheduled messaging, scraping, and use external services without declaring how it will obtain credentials or where it will store data. Before installing or enabling: - Confirm how Telegram pings are authorized: which bot/token and chat ID will be used, and that you explicitly consent to scheduled messages. - Ask where weekly scores and trend data will be stored (agent memory, platform DB, your account storage) and who can access them. - If you are not part of 'Nex AI', treat the Nex AI context as potentially environment-specific: it references internal endpoints, ports, and bots. Do not expose private network or credentials to this skill unless you control that environment. - If you want the automation (heartbeat, scrapers, email sequences), require the skill (or platform) to declare which environment variables or connectors it will use (Telegram_TOKEN, RESEND_API_KEY, etc.) and review those integrations separately. - If you only want advice/templates, restrict the skill from performing network actions or automated outreach until you've validated connectors and consent. Given the mismatch between instructions and declared requirements, proceed only after clarifying the above; otherwise treat the skill as text-only guidance and disable any automated outbound features.

Strategic Mentality System

Apply decision frameworks from four master sources to real business problems. No philosophy quotes, no motivational fluff. Actionable heuristics, concrete next actions, structured output.

Available Mentalities

Read the relevant reference file in references/ before applying any framework.

Mentality	File	Use When	Core Question
SUN_TZU	references/sun-tzu.md	Competition, positioning, market entry, timing, resource allocation	"How do I win without wasting resources?"
HORMOZI	references/hormozi.md	Lead generation, offers, pricing, advertising, scaling, outreach	"How do I get more strangers to want to buy my stuff?"
TWELVE_WEEK	references/twelve-week.md	Sprint planning, accountability, execution scoring, time blocking	"Am I executing on what matters this week?"
DAN_KENNEDY	references/dan-kennedy.md	Sales psychology, urgency, direct response, closing reluctant buyers	"How do I get them off the fence right now?"

Specialized Modules

Module	File	Use When
Lead Scoring	references/lead-scoring.md	Evaluate any lead with a 0-100 mentality-weighted score
Sales Call	references/sales-call.md	Handle objections during sales calls, especially with SME owners
Nex AI Context	references/nex-ai-context.md	Auto-load when running in Nex AI's OpenClaw instance for calibrated recommendations

Weekly Accountability

The HEARTBEAT.md file configures a scheduled Sunday evening ping via Telegram with a 12 Week Year scorecard prompt. The agent asks the user to fill in their weekly score, reviews the trend, and flags if execution is slipping below 65%.

How to Apply

Step 1: Map the Problem

Problem Type	Primary	Support
Should I pursue this lead/client?	HORMOZI	SUN_TZU
How do I beat competitor X?	SUN_TZU	HORMOZI
I'm not making progress	TWELVE_WEEK	SUN_TZU
What should I build/sell next?	HORMOZI	TWELVE_WEEK
How do I plan my next quarter?	TWELVE_WEEK	HORMOZI
Should I pivot or stay the course?	SUN_TZU	TWELVE_WEEK
How do I price this?	HORMOZI	SUN_TZU
I'm spread too thin	TWELVE_WEEK	SUN_TZU
How do I outreach effectively?	HORMOZI	DAN_KENNEDY
Score this lead	Lead Scoring module	All mentalities
Handle sales objection	Sales Call module	DAN_KENNEDY
Close this deal	DAN_KENNEDY	HORMOZI
Follow up strategy	DAN_KENNEDY	TWELVE_WEEK

Step 2: Load the Reference File

Read the matching references/*.md file. Each contains core principles, if-then heuristics, diagnostic questions, and an output template.

Step 3: Run Diagnostics

Ask the diagnostic questions from the loaded mentality to map the user's specific situation.

Step 4: Apply Heuristics and Output

Run the situation through the if-then heuristics. Output:

1. Situation Assessment - 2-3 sentences mapping problem to framework
2. Framework Verdict - what the mentality says to do
3. Concrete Actions - specific next steps with measurable targets
4. Risk - what could go wrong

Step 5: Combine When Needed

For complex decisions, apply the PRIMARY mentality first, then layer the SUPPORT mentality as a constraint or amplifier. Flag any contradictions explicitly.