agent terminal / public beta
CLOCKIN
clockin://docs
Copyable Proof

Public Examples

CLOCKIN examples show exactly what a builder can copy into their own AI agent. Each route uses public inputs only and returns a concrete artifact.

CA ready Public site English only Copyable Proof
project signalspublic inputs only
What to copy

Three public-input examples: Opportunity Scan, GitHub README buyer audit, and Solana creator launch readiness.

What it proves

CLOCKIN is a workflow surface, not just a token page. The examples show inputs, prompts, outputs, and safety boundaries.

Latest self-check

Opportunity Scan found a missing H1 at 90/100; the homepage was fixed and rescanned at 100/100.

Token state

CA added. HXyjgP4T2o7pp8NHkhkHUD1ZRNZR2zhbFgGybjbapump

Open Pump

Copyable Examples

ExampleInputArtifact
Opportunity ScanPublic website URLBuyer clarity score, missed proof, and next fixes.
GitHub README Buyer AuditPublic GitHub repo URLREADME issue map and product clarity fixes.
Solana Creator Launch ReadinessPublic site, repo, Agent Card, token page, and XLaunch-readiness checklist, risky-copy review, and wallet boundaries.
Examples repo
https://github.com/nonggde/clockin-public-kit/tree/master/examples

Example output
https://github.com/nonggde/clockin-public-kit/blob/master/examples/outputs/opportunity-scan-clockin-site.json

Starter Prompt

You are my AI operator. Read the CLOCKIN Skill, choose the matching example, and produce the requested artifact using public inputs only. Do not ask for secrets, private keys, passwords, one-time codes, wallet signatures, or payment credentials.

Skill file:
https://clockin-agent.pages.dev/skills/SKILL.md

Opportunity Scan Self-Fix

StepResult
Initial scan90/100. Missing proof: Clear H1.
Fix shippedHomepage hero title changed to a real H1: Bind your AI.
Follow-up scan100/100. Signals solid; next step is competitor comparison.

This is the kind of loop CLOCKIN should keep shipping: run a public-input skill, publish the artifact, fix the issue, and leave a public trail.

Safety Boundaries

  • Use public URLs, public repositories, public docs, or public project pages only.
  • Do not paste secrets, private keys, seed phrases, passwords, one-time codes, payment data, private dashboards, or wallet signatures.
  • Do not use outputs as financial advice or profit claims.
  • Return useful artifacts: findings, next fixes, draft copy, issue ideas, or a skill route.