@tianshu-ai/tianshu 0.3.0

package/plugins/web-search/package.json

@@ -0,0 +1,30 @@
+{
+  "name": "@tianshu-builtin/plugin-web-search",
+  "version": "0.1.0",
+  "private": true,
+  "description": "Web search tool for tianshu agents (Tavily / Brave Search providers).",
+  "type": "module",
+  "main": "./dist/server.js",
+  "types": "./dist/server.d.ts",
+  "exports": {
+    "./server": {
+      "types": "./dist/server.d.ts",
+      "default": "./dist/server.js"
+    },
+    "./manifest.json": "./manifest.json"
+  },
+  "files": ["dist", "src", "skills", "manifest.json"],
+  "scripts": {
+    "build": "tsc",
+    "dev": "tsc --watch --preserveWatchOutput",
+    "test": "vitest run --passWithNoTests"
+  },
+  "dependencies": {
+    "@tianshu/plugin-sdk": "*"
+  },
+  "devDependencies": {
+    "@types/node": "^25.9.1",
+    "typescript": "^5.9.3",
+    "vitest": "^3.2.4"
+  }
+}

package/plugins/web-search/skills/web-search-howto.md

@@ -0,0 +1,69 @@
+---
+name: web-search-howto
+description: How to use the `web_search` tool for tasks that need fresh information from the open web — current events, recent docs, prices, release notes, anything not in your training set or in the user's local files.
+scope: worker
+---
+
+# Web search
+
+`web_search` returns a JSON array of `{title, url, content,
+publishedDate}` objects from Tavily or Brave Search (whichever
+the host has an API key for; you don't have to pick).
+
+## Basic call
+
+```
+web_search({ query: "anthropic claude 4.7 release notes" })
+```
+
+Returns up to 5 results. Read titles + snippets first, only
+fetch the URL with `read_file`-style web fetchers when the
+snippet is insufficient.
+
+## Tuning
+
+- `count` (1-20, default 5): more results when you're sweeping
+  ("recent papers on retrieval-augmented generation"); fewer
+  when you know there's a canonical source ("python 3.13
+  release date").
+- `freshness`: `"day" | "week" | "month" | "year"`. Use this
+  for "what happened this week / this month" — without it,
+  search ranks by relevance over the whole web, which buries
+  recent news under older authoritative pages.
+- `language`: ISO 639-1 or locale, e.g. `"zh-CN"`, `"en"`.
+  Biases engines toward language-specific sources. Skip this
+  for technical English-language queries; technical content is
+  usually English regardless of locale.
+- `provider`: force `"tavily"` or `"brave"` if you want a
+  specific source. Default is "host's preferred provider with
+  fallback".
+
+## Anti-patterns
+
+- **Don't loop tiny searches.** Five searches with one keyword
+  each is worse than one search with the keywords combined.
+  `web_search({query: "claude 4.7 anthropic 2026 benchmark"})`
+  beats five separate searches.
+- **Don't ask `web_search` to summarise.** It doesn't. Read the
+  snippets, fetch the page if you need the full text, then
+  summarise yourself.
+- **Don't dump all results into the final answer.** Pick the
+  one or two most authoritative URLs, quote the relevant line,
+  cite. Agents who paste 10 result blocks turn answers into
+  noise.
+
+## When the snippet isn't enough
+
+`content` is 1-3 sentences. For the actual page body, fetch
+the URL through whatever HTTP fetcher you have available
+(`read_file` on a previously-saved page, the browser tools,
+etc.). `web_search` itself does not return page bodies; that's
+intentional — fetching only the URLs you actually need keeps
+the tool fast and cheap.
+
+## Citing sources
+
+When you use a result in a final answer, cite it with the
+title and URL. The agent who reads your output (the user, or
+the next worker in the chain) shouldn't have to retrieve it
+themselves to verify your claim.

package/plugins/workboard/agent-seeds/echo-demo/agent.json

@@ -0,0 +1,7 @@
+{
+  "kind": "echo",
+  "displayName": "Echo demo",
+  "description": "Sleeps, then echoes the task title. Ships with the workboard plugin.",
+  "enabled": true,
+  "source": "builtin"
+}

package/plugins/workboard/agent-seeds/llm-default/SOUL.md

@@ -0,0 +1,53 @@
+You are a workboard worker agent.
+
+You were started because the orchestrator dropped a task on the
+kanban for you. Each invocation handles ONE task end-to-end and
+then exits.
+
+## Your job
+
+- Read the task title and description carefully. The user (the
+  asking agent) wrote them; treat them as the spec.
+- Use whatever tools you need to do the work. The host's standard
+  tool set is available unless the orchestrator restricted you.
+- Write deliverables under the user's workspace (./projects/<slug>/
+  for finished output, ./tmp/ for scratch).
+
+## Exit contract (important)
+
+When you're done — or if the task is impossible and you've
+decided to give up — call the `task_complete` tool with a
+one-line `summary` of what you produced (or, on failure, why
+you couldn't). Optionally include `files` for paths you wrote.
+
+The orchestrator only sees the summary you pass to task_complete
+— prose alone won't reach it. If you finish without calling this
+tool, the pool counts the run as stalled and will retry.
+
+Do NOT ask the user clarifying questions: there's no human in
+your loop. If the spec is ambiguous, make a reasonable choice,
+proceed, and explain the choice in the task_complete summary.
+
+Reply concisely. Don't narrate every tool call — just do the
+work.
+
+## Reading skills before you act
+
+You have an `<available_skills>` block in your system prompt.
+Before starting any task, scan it. If a skill clearly applies,
+read its SKILL.md (use `tenant_config_read` for tenant skills
+or `read_file` for host/plugin skills) before doing anything
+else. Common triggers:
+
+- The task asks you to read ≥ 2 non-trivial files OR produce a
+  large output (long HTML / md / generated code) → you almost
+  certainly want to read **large-input-large-output** first.
+  The default failure mode is to batch-read all sources in one
+  turn and then try to emit the whole output in one
+  `write_file`; that runs you out of context or output budget
+  and the run aborts mid-call. The skill spells out the
+  read-then-summarise / skeleton-then-fill / batch-edit
+  patterns that avoid this.
+- The task involves running code → see `microsandbox-exec-howto`.
+
+One skill up front max. If none clearly applies, read none.

package/plugins/workboard/agent-seeds/llm-default/agent.json

@@ -0,0 +1,7 @@
+{
+  "kind": "llm",
+  "displayName": "Default LLM",
+  "description": "Default LLM worker. Picks up tasks tagged with worker_role=llm (or unrouted) and runs them to task_complete.",
+  "enabled": true,
+  "source": "builtin"
+}

package/plugins/workboard/dist/client.d.ts

@@ -0,0 +1,5 @@
+import { type AdminPageProps, type PanelProps, type PluginClientExports, type SidebarSectionProps } from "@tianshu/plugin-sdk/client";
+declare const clientExports: PluginClientExports;
+export declare const components: Record<string, import("react").ComponentType<PanelProps | AdminPageProps | SidebarSectionProps | import("@tianshu/plugin-sdk/client").ComposerActionProps | import("@tianshu/plugin-sdk/client").AttachmentRendererProps>>;
+export default clientExports;
+//# sourceMappingURL=client.d.ts.map

package/plugins/workboard/dist/client.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"client.d.ts","sourceRoot":"","sources":["../src/client.tsx"],"names":[],"mappings":"AAgDA,OAAO,EAEL,KAAK,cAAc,EACnB,KAAK,UAAU,EACf,KAAK,mBAAmB,EACxB,KAAK,mBAAmB,EACzB,MAAM,4BAA4B,CAAC;AA82EpC,QAAA,MAAM,aAAa,EAAE,mBAQpB,CAAC;AAEF,eAAO,MAAM,UAAU,4NAA2B,CAAC;AACnD,eAAe,aAAa,CAAC"}