In ArangoDB 2.6.9 we have fixed an AQL skiplist issue that occurs in a combination of sort and limit.
When using a Skiplist index on an attribute (say “a”) and then using sort and skip on this attribute caused the result to be empty e.g.:
require("internal").db._query("FOR x IN test SORT x.a LIMIT 10, 10");
Was always empty no matter how many documents are stored in test. This is now fixed.