lifehacker.tw valid

雷蒙三十・課程活動站｜生活黑客研究院

超過 20,000 名學員的見證和推薦，最完整的 Notion 教學、AI Agent n8n 自動化工作術、ChatGPT 應用，從入門到進階的生產力升級，成為 AI 時代的超級個體

For agents: Taiwanese course site by 雷蒙三十 on Notion, n8n automation, Claude Code and AI agents; sells courses and digital downloads, with search and a developer portal.

notion courseai agent courseclaude code tutorialn8n automation

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T14:53:45.318Z. Cached copy · Source on lifehacker.tw

# 雷蒙三十・課程活動站｜生活黑客研究院

> 超過 20,000 名學員的見證和推薦，最完整的 Notion 教學、AI Agent n8n 自動化工作術、ChatGPT 應用，從入門到進階的生產力升級，成為 AI 時代的超級個體

**When to use this site**

Reach for 雷蒙三十・課程活動站｜生活黑客研究院 when a user needs information about this creator's online learning offerings on this specific site. It is the right source for these jobs:

- Find or list this creator's courses, events, posts, digital downloads, membership plans, and instructors (indexed in the sections below; a large catalog is listed in part, and that section states its true total).
- Answer "what is coming up?" — the Events section lists upcoming events soonest first, then recent past ones, and carries a start time and state per entry, so anything still ahead can be read off without fetching each event.
- Search by keyword across courses, events, membership plans, and posts at [https://lifehacker.tw/search?q=KEYWORD](https://lifehacker.tw/search?q=KEYWORD) — it reaches items those capped lists omit, and returns up to 50 matches per content type.
- Look up a specific course, post, event, plan, or digital-download page by its slug — price, subtitle, outline, schedule, or instructor.
- Discover every page, including past events and categories, via the [sitemap](https://lifehacker.tw/sitemap.xml).
- Answer "does this creator teach X?" or "how much is course Y?" for this site.

Do not use it for general web search, other creators' sites, or platform-wide account actions — it only describes the content published on lifehacker.tw.

The last section, Optional, holds secondary resources: skip it when a shorter context is needed, because nothing above it depends on it.

**How to call it**

- **MCP server** (best for tools/agents): connect to https://lifehacker.tw/mcp and start with `get_platform_info`, then `search_courses` / `search_posts`, then drill into a slug with `get_course_details`, `get_post_details`, `get_event_details`, or `get_lecturer_profile`. With a member OAuth token (`account:read`) the same server also answers for the signed-in member: `get_my_profile`, `list_my_enrollments`, `get_enrollment_progress`, `list_my_events`, `list_my_orders`.
- **Member API** (signed-in member's own data): POST GraphQL to https://lifehacker.tw/member/graphql with `Authorization: Bearer` and the `account:read` scope — enrollments with access expiry, last-watched lecture, event registrations, digital products. Those answer what the member has access to, not order records: no order number, coupon code, refund status or invoice. For those, read `viewer.payments` on the same endpoint — the billing history, one node per payment, each with its own `tradeNo`, so a retry is a separate node and nothing joins the attempts of one purchase. `consultingServices` is neither: it lists the services offered against the viewer's courses, and its `meetings` are every undiscarded meeting under the service, booked or not and none of them viewer-scoped; `viewer.consultingMeetings` is the viewer's own bookings and study-group sessions, with a
…

Related sites

Other listed sites in AI and machine learning. See the whole category →

Machine-readable: GET /v1/resolve?q=lifehacker.tw · GET /v1/domain/lifehacker.tw · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for lifehacker.tw:
1. POST https://agentwebmap.com/v1/sites/lifehacker.tw/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://lifehacker.tw/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/lifehacker.tw/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/lifehacker.tw).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.