featbit_skill
- C#
53
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill jinfanzheng/kode-sdk-csharp --skill featbit- README.md3.0 KB
- SKILL.md8.5 KB
Overview
This skill is the FeatBit official documentation real-time Q&A assistant. It activates when a user mentions "FeatBit", "feature flag", "feature toggle", or asks about FeatBit SDK integration, deployment, or configuration. The skill fetches documentation in real time so answers reflect the latest docs and SDK READMEs. It routes SDK questions to GitHub and other topics to docs.featbit.co for accurate, source-backed guidance.
How this skill works
On activation the skill loads routing rules and required reference maps to classify the question. If keywords indicate an SDK/integration question it fetches the SDK README from GitHub; otherwise it fetches pages from docs.featbit.co. The skill composes a direct operational answer, includes runnable code for SDK integration queries, and attaches source links to the relevant documentation pages.
When to use it
- Ask how to initialize or integrate a FeatBit SDK (e.g., .NET, JavaScript, React).
- Request deployment guidance for Docker, Kubernetes, or Helm setups.
- Configure feature flags, targeting rules, rollouts, or A/B tests in FeatBit.
- Clarify environment keys, SDK Key vs Environment Secret, or webhook setup.
- Check the latest docs for breaking SDK API changes or configuration updates.
Best practices
- Classify questions by keywords first: SDK-related → GitHub README; others → docs.featbit.co.
- Always fetch documentation in real time; avoid long-term caching for SDK docs.
- Provide a direct, action-oriented answer and include runnable code for SDK tasks.
- Attach one or more official source links at the end of every answer.
- If docs lack the requested info, explicitly state that and point to official resources or GitHub Issues.
Example use cases
- User asks: "How do I initialize the .NET SDK?" → returns code sample and GitHub README link.
- User asks: "How to deploy FeatBit with Kubernetes?" → returns step-by-step deployment guidance from docs.featbit.co.
- User asks: "Where is the SDK key located?" → returns precise navigation steps from the docs with link.
- User asks: "How to configure an A/B test targeting rule?" → returns operational steps and relevant doc pages.
- User asks: "Is there an example Docker Compose for FeatBit?" → returns official compose snippet or says not found and links docs.
FAQ
I will state that the official documentation does not contain the information and point you to the main docs site or the relevant GitHub Issues page.
How do you decide whether to fetch from GitHub or docs.featbit.co?
The skill uses keyword rules: SDK/integration/client/server keywords route to GitHub; deployment, feature management, and configuration route to docs.featbit.co.