Build and publish a website. Use whenever the user asks to make, create, build, or publish a website, landing page, dashboard, status page, one-pager, or anything else a human will load in a browser. Covers both the publish recipe (no tunnels, no third-party hosts) and the design discipline that keeps the result from looking like generic AI slop.
Use for Clemson GC curriculum content questions — what a specific course teaches, what skills or projects it includes, what assignments are used, where a topic or learning outcome is covered, and how courses relate to each other pedagogically. This is about course *content*, not degree rules or credit requirements (use gc-advisor for those).
Use for ANY Clemson procurement or purchasing question — what's allowed or required, policy, rules, P-card, requisitions, purchase orders, suppliers, approvals, spending limits, bids/quotes. Use the procurement tools; never answer Clemson procurement from your own knowledge.
Use for Clemson class schedules and instructor scheduling — finding course sections, what an instructor is teaching, section details (time/seats/location), room availability, and academic terms. Use these tools, not your own knowledge.
Use for questions about Clemson Graphic Communications alumni outcomes — where graduates work now, first-job placement, career trajectories, AI exposure of GC occupations, industry/occupation distribution, grad-school rates, and outcome trends by graduation cohort. Data comes from the gc-alumni MCP server (read-only SQLite). For degree rules or course content use gc-advisor or clemson-curriculum instead.
Use for Clemson GC degree rules and academic requirements — degree audit (which requirements has a student met?), credit counts, gen-ed rules, specialty-area rules, prerequisite checking, course planning, and academic regulation lookups. This is about *rules and requirements*, not course content or pedagogy (use clemson-curriculum for what a course teaches, its skills/projects/assignments). Always pulls from the pinned catalog database — never from memory or the live website.
Install one or more host-side Telegram admin tools (/auth, /model, /provider) into the running NanoClaw instance. Trunk ships without them so the base codebase stays lean; operators opt in via this skill. Triggers on "add admin tools", "install admin commands", "add /model", "add /auth", "add /provider".
Read an image file's basic facts — format, dimensions, aspect ratio, orientation, file size, megapixels. Use when the user attaches an image and asks about its size, dimensions, resolution, or whether it fits a format (e.g. a square logo, a banner aspect ratio).