Sources & analysis
Skene uses sources—GitHub repositories—to understand your product and propose onboarding milestones. This page covers connecting, choosing the right repos, and troubleshooting.
What is a source?
A source is a GitHub repository that Skene can read. For each source, Skene runs analysis to infer:
Features & flows
Major user-facing flows to complete
Setup steps
SDKs, APIs, auth configuration
Expansion
Advanced features for later
Connecting a repository
Navigate to sources
In your workspace, go to the area where sources or repositories are listed.
Select the target site
Choose which site this source should belong to (e.g., your main web app).
Connect repository
- Click Connect repository
- Paste the HTTPS URL of your GitHub repository
- For private repos: use the Skene GitHub App or a fine-grained personal access token with read-only Contents access
Start analysis
Click Start analysis. This usually takes 2-5 minutes.
If stuck: Open the source detail page and click Trigger analysis to refresh status.
Choosing the right repositories
The quality of milestones depends on which repositories you connect:
Good choices
- • User-facing flows (web apps, API servers, SDKs)
- • Documentation-heavy repos
- • Repos representing customer onboarding
Avoid
- • Internal admin tools
- • CI/CD configs
- • Infrastructure/ops scripts
You can connect multiple sources and build different widgets from each—e.g., one for core product, another for a separate SDK.
Re-running analysis
As you ship new features, re-run analysis to refresh suggested milestones. Skene preserves your approved milestones; you can merge in new suggestions.
- Open the source detail page
- Click Trigger analysis
- Review new suggestions and attach them to lifecycles
Troubleshooting analysis
- 1Permissions: Ensure GitHub App/token still has access and hasn't been revoked.
- 2Rate limits: Wait a few minutes and re-try if you hit GitHub API limits.
- 3Large repos: Very large monorepos may timeout. Consider a smaller, more focused repo.
For more issues, see Troubleshooting.
What's next?
Once analysis succeeds, Skene populates your source with draft milestones. Refine these into your onboarding journey.
- Continue with Milestones & lifecycles
- Then Widgets & embedding