docs: update README (#9)

Author: freeznet

README.md

@@ -2,7 +2,7 @@
 
 Agent skills that teach any skill-compatible AI agent how to manage StreamNative Cloud resources through StreamNative Cloud remote MCP tools or the `snctl` CLI. Distributed as the `streamnative-agent-skills` plugin. Built to the [agentskills](https://agentskills.io) spec; installable as a Claude Code plugin or as portable skill directories in Cursor, Gemini CLI, OpenCode, Goose, Codex, and more.
 
-**At a glance:** 8 domain skills · 55 guided workflows · 36 reference docs · 22 starter YAML manifests · 8 `snctl` smoke walkthroughs · 8 remote MCP smoke walkthroughs · 16 machine-readable smoke specs.
+**At a glance:** 7 domain skills · 48 guided workflows · 33 reference docs · 22 starter YAML manifests · 7 `snctl` smoke walkthroughs · 7 remote MCP smoke walkthroughs · 16 machine-readable smoke specs.
 
 ---
 
@@ -60,7 +60,7 @@ Remote MCP cannot cover every local credential flow yet; keep `snctl` available
 /plugin install streamnative-agent-skills
 ```
 
-Registers all eight skills at once. Plugin metadata: [.claude-plugin/plugin.json](./.claude-plugin/plugin.json).
+Registers all seven currently documented skills at once. Plugin metadata: [.claude-plugin/plugin.json](./.claude-plugin/plugin.json).
 
 ### Other skill-compatible agents
 
@@ -77,7 +77,7 @@ Copy a single `skills/<skill-name>/` directory into the agent's skills directory
 
 ---
 
-## What's inside (the 8 skills)
+## What's inside (the 7 skills)
 
 | Skill | Workflows | Covers | Activates on |
 |---|---:|---|---|
@@ -88,15 +88,14 @@ Copy a single `skills/<skill-name>/` directory into the agent's skills directory
 | [identity](./skills/identity/) | 7 | Users, service accounts, roles, API keys, secrets, OIDC, identity pools | "grant access", "API key", "role binding", "OIDC", "federated login" |
 | [pulsar-admin](./skills/pulsar-admin/) | 8 | Tenants, namespaces, topics, subscriptions, Pulsar Functions | "tenant", "namespace", "topic", "produce/consume", "Pulsar function" |
 | [kafka-admin](./skills/kafka-admin/) | 7 | Kafka topics, groups, partitions, Schema Registry, Kafka Connect | "Kafka topic", "consumer group", "schema registry", "Kafka Connect" |
-| [workspaces](./skills/workspaces/) | 7 | Agent Functions, Pulsar IO sinks/sources, package upload/download | "agent function", "sink", "source", "Pulsar IO", "upload package" |
 
 ---
 
 ## Features
 
 ### Execution bases
 
-- **Remote MCP:** first-class route when agent runtime exposes StreamNative Cloud remote MCP tools. Org-level control-plane uses domain tools such as `sncloud_byoc_read/write`, `sncloud_identity_read/write`, `sncloud_clusters_read/write`, `sncloud_workspaces_read/write`, plus `sncloud_resource_catalog` and `sncloud_resource_schema`. Data-plane admin uses feature-gated Pulsar/Kafka MCP tools after fixed cluster binding or `sncloud_context_use_cluster`; both require cluster-level MCP enabled for the target cluster in StreamNative Cloud UI.
+- **Remote MCP:** first-class route when agent runtime exposes StreamNative Cloud remote MCP tools. Org-level control-plane uses domain tools such as `sncloud_byoc_read/write`, `sncloud_identity_read/write`, `sncloud_clusters_read/write`, plus `sncloud_resource_catalog` and `sncloud_resource_schema`. Data-plane admin uses feature-gated Pulsar/Kafka MCP tools after fixed cluster binding or `sncloud_context_use_cluster`; both require cluster-level MCP enabled for the target cluster in StreamNative Cloud UI.
 - **`snctl`:** portable fallback route and baseline for local credential/config operations and workflows not exposed by remote MCP.
 
 Remote MCP write tools expect JSON-string manifests and a dry-run-first workflow. Do not use generic `sncloud_resources_*` names; current public contract is domain-scoped.
@@ -120,12 +119,6 @@ Every manageable control-plane resource kind is owned by exactly one skill:
 - **Pulsar:** tenants, namespaces, topics (persistent + non-persistent, partitioned + non-partitioned), subscriptions (all 4 types), permissions, Pulsar Functions, produce/consume.
 - **Kafka:** topics, consumer groups, partitions, Schema Registry (AVRO / JSON / Protobuf), produce/consume. Kafka Connect is available for PulsarCluster/KSN contexts; direct KafkaCluster contexts may not expose Connect.
 
-### Stream-processing compute
-
-- **Agent Functions** (`snctl agents`) — LLM-backed streaming compute with tool-calling and schema-aware output.
-- **Pulsar IO sinks and sources** (`snctl pulsar admin sinks` / `sources`) — connector-based data movement to/from external systems (JDBC, Snowflake, Elasticsearch, S3, Kafka, Debezium CDC, and more).
-- **Package management** (`snctl pulsar admin packages`) — upload/list/download/delete archives via `function://<tenant>/<namespace>/<name>@<version>` URLs, referenced by Pulsar Functions, Agent Functions, and connectors.
-
 ### Tooling bundled with this repo
 
 - `scripts/install-snctl.sh` — install a pinned `snctl` from the canonical GCS bucket.
@@ -201,7 +194,7 @@ See [CONTRIBUTING.md](./CONTRIBUTING.md).
 
 - **Plugin:** semver, bumped on any skill change (starts at `0.1.0`).
 - **Each skill:** its own `metadata.version` in frontmatter, bumped when that skill's content changes.
-- **snctl compatibility:** each skill pins `snctl-min-version` in frontmatter. The current floor is `1.5.0` — aligned with when `snctl context` and `snctl agents` stabilized.
+- **snctl compatibility:** each skill pins `snctl-min-version` in frontmatter. The current floor is `1.5.0` — aligned with when `snctl context` stabilized.
 
 ---