Results for “on-page”

Builds a feature specification from scratch with plan-a-feature and publishes it to a user-specified Confluence location, posting the spec as a parent page and each companion artifact (decision log, team findings, technical notes) as a child page beneath it. Use when the user wants a new feature planned, designed, scoped, or specified AND posted to a Confluence space or page. Requires a configured Atlassian MCP server. Does not plan to local files only — use plan-a-feature. Does not publish an arbitrary existing markdown file — use markdown-to-confluence. Does not refine or stress-test an existing plan — use iterative-plan-review. Does not document already-built features to Confluence — use project-documentation-to-confluence.

Use when a human asks to connect to or enter Agent Internet or AI Internet, get their agent online, or open Agent Internet Browser, Bot Browser, a Bot page, a Bot homepage, a domain alias, a chain pin, a MetaApp, a MetaFile, or a map through the existing local Browser entrypoint, including opening a resource in a new Browser tab; also use when the human wants to find or discover on-chain MetaApps by topic, tag, publisher, or time range — such as "what on-chain mini-games exist", "apps published in the last 30 days", or "open the on-chain buzz app" — list the remixes of a known app, read what an app does, or remix and republish an existing MetaApp; also use when the human wants to find or discover on-chain users or Bots by name, personality, skill, or recency — such as "view Alice's bot page", "find cheerful users to chat with", or "find a bot that can translate" — or read an identity's full on-chain profile.

The "Commerce" MCP tiles — Documenso e-signatures is the one MCP-drivable tile; the rest (cashback quests, coupons, gift cards, fraud queue, merch) are admin-portal pages, with the QuestX rewards engine reachable via the game-ops `quests` MCP. Use for contracts and commerce-program admin.

Use when an AI agent needs to control a browser, automate web tasks, scrape pages, fill forms, or click buttons autonomously. Triggers on: 'browser automation', 'web agent', 'browser-use', 'AI browse', 'tự động duyệt web', 'điều khiển trình duyệt', 'scrape with AI', 'click button automatically', 'fill form automatically', 'web task automation'.

Publishes a local Markdown file to a user-specified Confluence location, creating a new page or updating an existing one through the Atlassian MCP server. Use when the user wants to post, publish, push, or sync a Markdown file to a Confluence space or page. Requires a configured Atlassian MCP server. Does not write or generate the Markdown itself — point it at an existing file, or use project-documentation-to-confluence for the document-then-publish flow, or plan-a-feature-to-confluence for the plan-then-publish flow. Does not publish to Jira — use work-items-to-jira.

Off-page playbook (Lesson 10, outreach). Turns a vetted link-prospect list into them-focused outreach drafts that earn links without spamming. Picks the RIGHT people (those who LINKED to or MENTIONED our topic — never "people who tweeted it"), gives each a real "excuse" (fresh-angle / new-proof / ego-bait), keeps to ≤1 follow-up, and never makes a pushy link ask. Drafts only — every outward send is operator-gated. Outreach is a tool, not a strategy.

Off-page playbook (Lesson 9, link building). Mines our competitors' backlink profiles via Ahrefs to produce a VETTED link-prospect list — their "superfans" (sites linking to several of a competitor's best-by-links pages), their "power-linkers" (sites linking to multiple competitors but NOT to us), and their fresh new links — filtered for relevance and de-duped against sites that already link to us. The Link Intersect method, encoded. Output is a prospect queue for /outreach; it does NOT send anything.

Post-draft pass that expands a drafted article to capture the FULL keyword family — keywords the page already or could rank for, plus the Ahrefs Content Gap (keywords competitors rank for but we don't) — by weaving the worthwhile ones in as natural added paragraphs/sections. NOT keyword stuffing. Triggered after /draft, before /quality-check.

Use when an agent needs to read the internet without paid API keys — Twitter/X, Reddit, YouTube, Bilibili, GitHub, TikTok, Xiaohongshu, RSS, web pages. Triggers on: 'agent-reach', 'agent đọc internet', 'đọc Twitter không API', 'đọc Reddit không API', 'agent xem YouTube', 'agent đọc Bilibili', 'agent đọc B站', 'agent đọc XHS', 'agent đọc Xiaohongshu', 'read social media free', 'agent internet eyes', 'no API key scraping', 'unified social reader'.

Use when an agent needs read-only MetaWeb data access (local Bot/MetaBot identity state, service, trace, or chain reads) and should prefer public metabot interfaces. Treat Bot, bot, and MetaBot wording as equivalent and case-insensitive for read-only identity/service queries; do not use this skill for writes like buzz post, service publish, file upload, or remote order submission; do not use this skill to look up, view, or open other users or Bots by name, personality, skill, or profile — people search, Bot pages, and identity profiles belong to metabot-browser, even when the request is phrased as a read-only "show me someone's info" query.

Execute a relaunch on a decayed-but-valuable article (Lesson 5 audit + Lesson 8 "don't abandon old winners"). Take a page the audit flagged as decaying or rank-slipping, refresh it against the LIVE SERP (freshen data, re-verify searcher intent, squeeze new keywords, refresh visuals), bump its published date, and re-promote it as if brand new. The "update ~half the calendar" half of the strategy. Triggered from the audit's Relaunch plan.

Build and maintain a persistent markdown wiki that an LLM updates on the user's behalf, usually inside an Obsidian vault or git-tracked notes repo. Use when raw sources such as web articles, papers, meeting notes, transcripts, screenshots, or past analyses need to be turned into an interlinked knowledge base with immutable source files, LLM-written wiki pages, `index.md`, `log.md`, schema rules in `AGENTS.md` or `CLAUDE.md`, source summaries, query notes, and recurring lint passes. Triggers on: llm-wiki, personal wiki, obsidian wiki, research vault, knowledge base, source ingest, persistent notes, wiki maintenance, source summaries, query filing.

Runs an evidence-based investigation of a bug, failure, or unexpected behavior with investigate and publishes the resulting investigation report to a user-specified Confluence location. Use when the user wants something debugged, diagnosed, or root-caused AND the findings posted to a Confluence space or page. Requires a configured Atlassian MCP server. Does not investigate to a local file only — use investigate. Does not publish an arbitrary existing markdown file — use markdown-to-confluence. Does not document an already-understood feature to Confluence — use project-documentation-to-confluence. Does not plan or specify a new feature to Confluence — use plan-a-feature-to-confluence. Does not publish to Jira — use work-items-to-jira.

Produces a progressive-disclosure overview of unfamiliar code or a pull request's changes with code-overview and publishes the resulting overview to a user-specified Confluence location. Use when the user wants code or a PR explained, oriented, or made sense of AND the overview posted to a Confluence space or page. Requires a configured Atlassian MCP server. Does not produce the overview to a local file only — use code-overview. Does not publish an arbitrary existing markdown file — use markdown-to-confluence. Does not document an already-understood feature to Confluence — use project-documentation-to-confluence. Does not root-cause a bug to Confluence — use investigate-to-confluence. Does not plan or specify a new feature to Confluence — use plan-a-feature-to-confluence. Does not publish to Jira — use work-items-to-jira.