The policy every author — human and AI-assisted — follows before anything ships on skene.ai. If we break a rule on this page, email us and we'll fix it.
Last reviewed: 2026-04-20
Everything published on skene.ai — blog posts, playbooks, glossary entries, docs, and alternatives pages — is produced by named humans on the Skene team or by external contributors credited on the byline.
We do not publish content under the generic "Skene" author name going forward. Historical posts attributed to "Skene" are being migrated to named authors; until that migration completes, treat "Skene" as "the Skene editorial team" and assume collective responsibility.
Claims about the Skene product reference the code, the public docs, or the changelog. If we cannot point a reader to a file, a UI, an API response, or a release note, we do not ship the claim.
Claims about third-party products (Pendo, Amplitude, Gainsight, Segment, Mixpanel, and the rest of the alternatives pages) are anchored to the vendor's own public documentation, pricing page, or a dated primary source. We link out so readers can verify independently.
Benchmarks and performance numbers cite methodology and sample size. If we cannot show the methodology, we label the number as a directional estimate.
We use large language models (Claude, GPT-4/5-class models) to draft outlines, tighten copy, and generate first-pass JSON-LD or code snippets. A named human author reviews, edits, and signs off on every piece before it publishes.
AI-generated code examples in our docs and blog are tested against the actual Skene CLI or runtime before publishing.
We do not generate fake quotes, fake case studies, or fake customer names. If a customer story is not on-the-record, we either omit it or present it anonymised with a disclosure.
If you spot a factual error — in a blog post, a comparison, a pricing claim, a benchmark, or a docs snippet — email support@skene.ai with the URL and the correction.
Material corrections are applied inline and disclosed with a dated note at the bottom of the affected page. Typos and non-material edits are applied silently.
We do not stealth-edit comparison pages to downplay competitor strengths. If a competitor ships a feature that invalidates a claim we made, we update the claim and note the change.
Skene does not accept paid placements, sponsored posts, or affiliate commissions on skene.ai. Every recommendation reflects what we actually use or have tested.
When we recommend a third-party tool (Supabase, Resend, Vercel, Stripe, an AI provider, and so on), we disclose any commercial relationship in the post. The default assumption is: no commercial relationship.
Skene is an open-source project and a commercial company at the same time. We link to our own product when it is genuinely the right answer for the reader — and we link to competitors when they are a better fit.
External links use descriptive anchor text and open in a new tab where appropriate. We do not cloak links, inject tracking into third-party URLs, or use redirect chains to obscure destinations.
We prefer primary sources (vendor docs, RFCs, changelogs, academic papers, official standards) over secondary aggregators.
Images have alt text. Code blocks have language labels. Headings use a consistent hierarchy so screen readers and LLMs can parse structure.
We write in plain English and avoid jargon that assumes the reader is already inside the PLG world. When a term is unavoidable, we link to our glossary.
Our robots.txt grants access to major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and others) for public content, and blocks them from authenticated workspace paths. We want LLMs to cite us accurately.
Quoting our content in AI answers or third-party publications is welcome — please link back to the canonical URL.
Send the URL and the correction to support@skene.ai. We'll fix and disclose.
