Business Document Generator
ailabs-393/ai-labs-claude-skills
This skill should be used when the user requests to create professional business documents (proposals, business plans, or budgets) from templates.
AL project estimation for Business Central. An agent skill from javiarmesto/ALDC-AL-Development-Collection.
Install Skill Estimation
$ npx skills add javiarmesto/ALDC-AL-Development-Collection --skill skill-estimation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install javiarmesto/ALDC-AL-Development-Collection skill-estimation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/javiarmesto/ALDC-AL-Development-Collection.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skill-estimation .claude/skills/skill-estimation && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "skill-estimation" agent skill from https://github.com/javiarmesto/ALDC-AL-Development-Collection/tree/main/skills/skill-estimation into .claude/skills/skill-estimation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-estimation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/javiarmesto/ALDC-AL-Development-Collection/tree/main/skills/skill-estimationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add javiarmesto/ALDC-AL-Development-Collection --skill skill-estimation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install javiarmesto/ALDC-AL-Development-Collection skill-estimation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/javiarmesto/ALDC-AL-Development-Collection.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/skill-estimation .agents/skills/skill-estimation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "skill-estimation" agent skill from https://github.com/javiarmesto/ALDC-AL-Development-Collection/tree/main/skills/skill-estimation into .agents/skills/skill-estimation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-estimation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add javiarmesto/ALDC-AL-Development-Collection --skill skill-estimation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install javiarmesto/ALDC-AL-Development-Collection skill-estimation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/javiarmesto/ALDC-AL-Development-Collection.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/skill-estimation .cursor/skills/skill-estimation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "skill-estimation" agent skill from https://github.com/javiarmesto/ALDC-AL-Development-Collection/tree/main/skills/skill-estimation into .cursor/skills/skill-estimation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-estimation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/javiarmesto/ALDC-AL-Development-Collection.git --path skills/skill-estimation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add javiarmesto/ALDC-AL-Development-Collection --skill skill-estimation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install javiarmesto/ALDC-AL-Development-Collection skill-estimation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/javiarmesto/ALDC-AL-Development-Collection.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/skill-estimation .gemini/skills/skill-estimation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "skill-estimation" agent skill from https://github.com/javiarmesto/ALDC-AL-Development-Collection/tree/main/skills/skill-estimation into .gemini/skills/skill-estimation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-estimation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install javiarmesto/ALDC-AL-Development-Collection skill-estimationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add javiarmesto/ALDC-AL-Development-Collection --skill skill-estimation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/javiarmesto/ALDC-AL-Development-Collection.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/skill-estimation .github/skills/skill-estimation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "skill-estimation" agent skill from https://github.com/javiarmesto/ALDC-AL-Development-Collection/tree/main/skills/skill-estimation into .github/skills/skill-estimation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-estimation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add javiarmesto/ALDC-AL-Development-Collection --skill skill-estimation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install javiarmesto/ALDC-AL-Development-Collection skill-estimation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/javiarmesto/ALDC-AL-Development-Collection.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/skill-estimation .opencode/skills/skill-estimation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "skill-estimation" agent skill from https://github.com/javiarmesto/ALDC-AL-Development-Collection/tree/main/skills/skill-estimation into .opencode/skills/skill-estimation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-estimation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
skill-estimation- GitHub stars
- 109
- Token cost
- ~2.3k tokens
- SKILL.md length
- 526 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
AL project estimation for Business Central. An agent skill from javiarmesto/ALDC-AL-Development-Collection.
- Works in 5 steps: Intake → Analyze → Estimate → …
- Estimating development effort
- SKILL.md covers Purpose, When to Load, Core Patterns and Workflow, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Skill Estimation is an agent skill from javiarmesto/ALDC-AL-Development-Collection. AL project estimation for Business Central. Use when estimating development effort, creating cost models, SWOT analysis, or structuring project proposals.
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Business, Finance & HR, covering Startup and business strategy and Proposals and quotes. The repository describes itself as: AL development toolkit for Business Central with specialist agents, skills and review workflows for Copilot, Claude Code and Codex. The licence is MIT.
When your agent uses it
- Estimating development effort
- Creating cost models
- Structuring project proposals
Example prompts
- “/skill-estimation”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 4f99d7d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
learn.microsoft.comen.wikipedia.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Skill Estimation loads about 2.3k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 526 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from javiarmesto/ALDC-AL-Development-Collection at commit 4f99d7d, republished under its MIT licence (© javiarmesto). 526 words, ~2,320 tokens.
Download SKILL.mdSave it as
.claude/skills/skill-estimation/SKILL.md (or your agent's skills folder).- name
- skill-estimation
- description
- AL project estimation for Business Central. Use when estimating development effort, creating cost models, SWOT analysis, or structuring project proposals.
Skill: AL Project Estimation
Purpose
Estimate AL/Business Central projects: complexity scoring, PERT 3-point estimation, SWOT/DAFO risk analysis, cost breakdown by phase, resource allocation, and structured presales documentation.
When to Load
This skill should be loaded when:
- A new BC/AL project needs time and cost estimation
- A feasibility assessment or SWOT analysis is required before commitment
- A presales proposal or technical assessment document is being created
- Resource allocation and team composition need to be defined
- A project plan with milestones and payment schedule is needed
Core Patterns
Pattern 1: Intake Questions (Mandatory)
Before any estimation, gather these parameters:
## Project Intake — Required Information
### 1. Project Identity
- Project name (will be used for folder structure)
- Brief description: What problem does it solve?
### 2. Cost Parameters (MANDATORY)
- Hourly rate (e.g., €75/hour, $100/hour)
- Currency (EUR, USD, GBP)
- Contingency buffer: Yes/No (default 15-20%)
- Risk buffer: Low (10%), Medium (20%), High (30%)
### 3. Technical Context
- Target BC version: SaaS, On-Premise, or both?
- Target delivery date
- Existing codebase? (repository URL or workspace path)
- Reference repositories for similar functionality?
### 4. Team (optional)
- Available developers: Junior, Mid, Senior?
- BC experience level: New, Experienced, Expert?PAUSE — do NOT proceed without cost parameters. Estimation without rates is meaningless.
Pattern 2: Complexity Scoring
Score each dimension 1-10 to derive overall project complexity:
## Complexity Assessment
| Dimension | Score (1-10) | Criteria |
|---|---|---|
| Data Model | /10 | Tables, relations, migration needs |
| Business Logic | /10 | Codeunits, validations, calculations |
| UI Complexity | /10 | Pages, customizations, RoleCenter |
| Integrations | /10 | External APIs, events, webhooks |
| Reporting | /10 | Reports, queries, analytics |
| Security | /10 | Permissions, data sensitivity, audit |
| Testing | /10 | Test coverage needed, edge cases |
| Migration/Upgrade | /10 | Data migration, version compatibility |
**Overall Complexity**: (sum / 80) × 10 = X/10Object count estimation:
| Object Type | Low Complexity | Medium | High |
|---|---|---|---|
| Table | 2-4 hrs | 4-8 hrs | 8-16 hrs |
| Page (Card/List) | 2-4 hrs | 4-8 hrs | 8-16 hrs |
| Page (Document) | 4-8 hrs | 8-16 hrs | 16-32 hrs |
| Codeunit | 2-8 hrs | 8-16 hrs | 16-40 hrs |
| Report | 4-8 hrs | 8-16 hrs | 16-32 hrs |
| Integration | 8-16 hrs | 16-32 hrs | 32-80 hrs |
Pattern 3: PERT 3-Point Estimation
Use the Program Evaluation and Review Technique for each task:
## PERT Formula
E = (O + 4M + P) / 6
Where:
- O = Optimistic (best case, everything goes right)
- M = Most Likely (normal case, typical obstacles)
- P = Pessimistic (worst case, major obstacles)
- E = Expected durationApply per development phase:
## Phase Breakdown
### Phase 1: Analysis & Design
| Task | O (hrs) | M (hrs) | P (hrs) | E (hrs) |
|---|---|---|---|---|
| Requirements analysis | 8 | 16 | 24 | 16 |
| Technical design | 8 | 12 | 20 | 13 |
| Architecture review | 4 | 8 | 12 | 8 |
| **Subtotal** | **20** | **36** | **56** | **37** |
### Phase 2: Development
| Task | O (hrs) | M (hrs) | P (hrs) | E (hrs) |
|---|---|---|---|---|
| Tables & data model | X | X | X | X |
| Pages & UI | X | X | X | X |
| Business logic | X | X | X | X |
| Integrations | X | X | X | X |
| **Subtotal** | **X** | **X** | **X** | **X** |
### Phase 3: Testing & QA
| Task | O (hrs) | M (hrs) | P (hrs) | E (hrs) |
|---|---|---|---|---|
| Unit tests | X | X | X | X |
| Integration tests | X | X | X | X |
| UAT support | X | X | X | X |
| Bug fixes | X | X | X | X |
| **Subtotal** | **X** | **X** | **X** | **X** |
### Phase 4: Deployment & Documentation
| Task | O (hrs) | M (hrs) | P (hrs) | E (hrs) |
|---|---|---|---|---|
| Technical documentation | X | X | X | X |
| Training materials | X | X | X | X |
| Deployment | X | X | X | X |
| Post-go-live support | X | X | X | X |
| **Subtotal** | **X** | **X** | **X** | **X** |Pattern 4: SWOT/DAFO Analysis
Structured risk and opportunity assessment:
## SWOT Analysis
### Strengths (Internal Positive)
| ID | Strength | Impact |
|---|---|---|
| S1 | [e.g., Team has BC experience] | High/Medium/Low |
### Opportunities (External Positive)
| ID | Opportunity | Impact |
|---|---|---|
| O1 | [e.g., Standard BC API available] | High/Medium/Low |
### Weaknesses (Internal Negative)
| ID | Weakness | Impact | Mitigation |
|---|---|---|---|
| W1 | [e.g., No existing test suite] | High | Implement TDD from start |
### Threats (External Negative)
| ID | Threat | Probability | Impact | Mitigation |
|---|---|---|---|---|
| T1 | [e.g., BC version upgrade mid-project] | Medium | High | Pin BC version |
## Feasibility Score
| Criterion | Score (1-10) |
|---|---|
| Technical Feasibility | /10 |
| Resource Feasibility | /10 |
| Timeline Feasibility | /10 |
| Economic Feasibility | /10 |
| **Overall** | **/10** |
### Recommendation
- [ ] **GO** — Project viable, proceed
- [ ] **CAUTION** — Viable with conditions
- [ ] **NO-GO** — Not recommended currentlyPattern 5: Cost Summary and Payment Milestones
Consolidate estimation into a financial summary:
## Cost Summary
| Concept | Hours | Rate | Cost |
|---|---|---|---|
| Analysis & Design | X | [RATE] | [TOTAL] |
| Development | X | [RATE] | [TOTAL] |
| Testing & QA | X | [RATE] | [TOTAL] |
| Deployment & Docs | X | [RATE] | [TOTAL] |
| **Subtotal** | **X** | | **[TOTAL]** |
| Contingency ([%]%) | X | | [TOTAL] |
| Risk Buffer ([%]%) | X | | [TOTAL] |
| **TOTAL** | **X** | | **[CURRENCY] [TOTAL]** |
## Payment Milestones
| Milestone | % | Amount | Deliverable |
|---|---|---|---|
| Project Start | 20% | [X] | SOW signed, project plan |
| Design Approved | 20% | [X] | Architecture approved |
| Development Complete | 30% | [X] | Code delivered, tests pass |
| UAT Approved | 20% | [X] | User acceptance sign-off |
| Go-Live | 10% | [X] | Production deployment |Workflow
Step 1: Intake
- Ask mandatory intake questions (Pattern 1)
- Confirm cost parameters — do NOT skip this
- If reference repositories provided, analyze them for scope comparison
Step 2: Analyze
- Score complexity dimensions (Pattern 2)
- Count estimated objects (tables, pages, codeunits, reports)
- Identify integration points and external dependencies
- If existing codebase, use
al_search_objectsto measure current scope
Step 3: Estimate
- Apply PERT 3-point estimation per phase (Pattern 3)
- Use complexity-based hour ranges for object estimation
- Apply standard ratios:
- Testing = 30-40% of development
- Documentation = 10-15% of total
- Integration = typically underestimated by 50% — adjust accordingly
- Data migration = 15-20% of total (if applicable)
- BC version testing = 5-10% for compatibility
Show full SKILL.md (195 more words)Show less
Step 4: Risk Assessment
- Conduct SWOT analysis (Pattern 4)
- Calculate feasibility score
- Provide clear GO / CAUTION / NO-GO recommendation
Step 5: Deliver Proposal
- Create cost summary with payment milestones (Pattern 5)
- Define resource allocation (roles, FTE, duration)
- Compile all sections into presales documentation
- Store in
Technical_PreSales/{project-slug}/folder structure
PAUSE — present proposal for stakeholder review before commitment.
Estimation Guidelines
| Rule | Guideline |
|---|---|
| Testing effort | Always 30-40% of development hours |
| Documentation | Never skip — 10-15% of total hours |
| Integration complexity | Usually underestimated — add 50% buffer |
| Data migration | Add if mentioned — 15-20% of total |
| BC version testing | Add 5-10% for compatibility verification |
| Training | 8-16 hours per user group |
| Contingency | 15-20% standard, 25-30% for high uncertainty |
References
- PERT Estimation Technique
- BC Extension Development Guide
- AppSource Submission Requirements
- BC Licensing Model
Constraints
- This skill covers project estimation, risk analysis, and presales documentation
- Do NOT estimate without cost parameters (hourly rate, currency) — ask first
- Do NOT build, compile, or deploy code — estimation only
- Do NOT modify production source code — analysis and documentation only
- Do NOT skip the SWOT analysis for any project — risk awareness is mandatory
- Architecture design → al-architect agent | Technical specifications → al-spec.create workflow | Implementation → al-conductor agent
© javiarmesto, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/skill-estimation of javiarmesto/ALDC-AL-Development-Collection.
Open the folder on GitHubat commit 4f99d7d
Compare with similar skills
Skill Estimation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Skill Estimation this skilljaviarmesto/ALDC-AL-Development-Collection | 109 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Business Document Generatorailabs-393/ai-labs-claude-skills | 454 | — | ~2k | Automated safety check: Pass | MIT | |
| Anygen DocLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.3k | Automated safety check: Pass | MIT | |
| Startup Pressure TestKappaemme-git/codex-startup-pressure-test-skill | 991 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Zhang Yiming Perspectivealchaincyf/zhang-yiming-skill | 173 | 2 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Mmr Loop Skill9600dev/mmr | 131 | — | ~2.6k | Automated safety check: Pass | Custom licence |
Similar skills
Anygen Doc
LeoYeAI/openclaw-master-skills
Use this skill any time the user wants to create, draft, or generate a written document or report.
Startup Pressure Test
Kappaemme-git/codex-startup-pressure-test-skill
Pressure-tests a startup idea with blunt, compact analysis of problem reality, competition, first customers and MVP, ending in a strong, weak or pivot verdict.
Zhang Yiming Perspective
alchaincyf/zhang-yiming-skill
Answers product, organization, globalization, talent and growth questions in the voice of ByteDance founder Zhang Yiming, using a framework built from public material.
Mmr Loop Skill
9600dev/mmr
Autonomous trading loop for the MMR platform. An agent skill from 9600dev/mmr.
Mmr Skill
9600dev/mmr
Operate the MMR algorithmic trading platform on Interactive Brokers.
More from javiarmesto/ALDC-AL-Development-Collection
All 14 skills in this repoSkill Agent Instructions
javiarmesto/ALDC-AL-Development-Collection
Generate, review, and optimize natural language instructions for Business Central agents (Designer or SDK).
Skill API
javiarmesto/ALDC-AL-Development-Collection
AL API development patterns for Business Central. An agent skill from javiarmesto/ALDC-AL-Development-Collection.
Skill Copilot
javiarmesto/ALDC-AL-Development-Collection
AL Copilot capability development for Business Central. An agent skill from javiarmesto/ALDC-AL-Development-Collection.
Skill Migrate
javiarmesto/ALDC-AL-Development-Collection
AL version migration for Business Central. An agent skill from javiarmesto/ALDC-AL-Development-Collection.
Skill Agent Task Patterns
javiarmesto/ALDC-AL-Development-Collection
Agent SDK task integration patterns for Business Central. An agent skill from javiarmesto/ALDC-AL-Development-Collection.
Skill Agent Toolkit
javiarmesto/ALDC-AL-Development-Collection
Build, configure, and integrate Business Central agents using the AI Development Toolkit and Agent SDK.
Related
Questions about Skill Estimation
What does Skill Estimation do?
AL project estimation for Business Central. An agent skill from javiarmesto/ALDC-AL-Development-Collection. Skill Estimation is an agent skill from javiarmesto/ALDC-AL-Development-Collection. AL project estimation for Business Central.
When should I use Skill Estimation?
Skill Estimation fits situations like: estimating development effort; creating cost models; structuring project proposals.
How do I install Skill Estimation in Claude Code?
Run `npx skills add javiarmesto/ALDC-AL-Development-Collection --skill skill-estimation -a claude-code`. Or copy the skill folder (skills/skill-estimation in javiarmesto/ALDC-AL-Development-Collection) into .claude/skills/skill-estimation in your project. Claude Code loads it when a task matches its description.
How do I install Skill Estimation in Codex?
Run `npx skills add javiarmesto/ALDC-AL-Development-Collection --skill skill-estimation -a codex`. Or copy the skill folder (skills/skill-estimation in javiarmesto/ALDC-AL-Development-Collection) into .agents/skills/skill-estimation in your project. Codex loads it when a task matches its description.
Can I use Skill Estimation in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add javiarmesto/ALDC-AL-Development-Collection --skill skill-estimation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill-estimation, .gemini/skills/skill-estimation, .github/skills/skill-estimation and .opencode/skills/skill-estimation in your project.
What does Skill Estimation need to run?
SKILL.md names no scripts, command-line tools or credentials: Skill Estimation is instructions for the agent only.
Does Skill Estimation access the network?
SKILL.md names 2 domains. As links in the text: learn.microsoft.com and en.wikipedia.org. This is read from the text; nothing was executed.
Is Skill Estimation safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Skill Estimation use?
Skill Estimation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Skill Estimation use?
About 2.3k tokens (SKILL.md is roughly 9.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Skill Estimation?
Skills that share tags, products or a category with Skill Estimation: Business Document Generator (ailabs-393/ai-labs-claude-skills, 454 stars), Anygen Doc (LeoYeAI/openclaw-master-skills, 2.2k stars), Startup Pressure Test (Kappaemme-git/codex-startup-pressure-test-skill, 991 stars) and Zhang Yiming Perspective (alchaincyf/zhang-yiming-skill, 173 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Skill Estimation?
javiarmesto (a GitHub user) maintains it in javiarmesto/ALDC-AL-Development-Collection, which has 109 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 7, 2026.
Source: javiarmesto/ALDC-AL-Development-Collection on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.